posted on September 24, 2001 09:06:59 AM
I've seen the WBN do this before but just realized why it does it sometimes and not other times and wondered if this glitch will be fixed or if I need to change the words in my auction titles.
Here is what happens. When a title has a ' in it (like for Collector's) it inserts a ' for the ' so that Collector's becomes Collector's and looks very unprofessional. My bidders probably think I've been hitting the bottle while doing end of auction correspondence
Is this a glitch that is gonna be fixed?
Thanks,
Antelope67
posted on September 24, 2001 11:01:34 AM
Hi Antelope67,
We are aware of a glitch in the system that sometimes causes the problem you have described, however, it would be helpful for us in isolating the source of the problem if you could let us know if these characters are appearing in the subject line or in the body of the WBN.
posted on September 24, 2001 01:38:56 PM
It is happening in the subject line and the the body of the WBN.
Also, I didn't know if you were aware that ebay made changes to the categories again. I posted to another thread about it. I noticed the one change but there are likely others as well.
posted on September 25, 2001 02:06:59 PM
I have some more info concerning the strange characters in the WBN's that might help you to pinpoint the problem and fix it. This morning I edited all items in inventory that had an apostrophe in the title and all went well. But then I was gonna relist some auctions from the auctions ended section this afternoon and realized that most of them also had an apostrophe in the title. But after ya tell the system to relaunch it gives the option to edit each auction first. So I did. When I got to the edit for each auction I was surprised to see that in the title there was no apostrophe but had the ' instead! It looked fine from other menus and in inventory but in edit mode from the relaunch menu it had the strange string of characters. Hope this helps.
Antelope67
Engineering is aware of this issue and actively working to correct it. We should have a fix in place sometime in the next few weeks, sorry I do not have an exact ETA.
As soon as I do have an update on this issue, we will post back to this thread.
