29-03-2025 02:43 PM - edited 29-03-2025 02:45 PM
A couple of weeks ago, I noticed eBay had removed some of the embedded images from my listings. While a massive inconvenience and extremely time consuming, it wasn't difficult to revise each listing and replace the images.
Then in the evening of Thursday 27th March, a new issue arose.
Every item I revise ends up being bar-$tar-dized by eBay once the revision is submitted. I end up with random font sizes, styles, colours, bold text, line spacings, text spacings, etc.. Basically, they randomly target anything at all that can possibly be screwed up. Nothing is safe. I really don't want bold, italic hot pink font - or lime green Times New Roman (8) randomly tossed in with grape purple Arial (14), and alternating black and red bullet points.
After spending countless hours trying to fix the stuff up, using 3 different browsers, classic site, mobile site and app, I've discovered that it only happens to listings with bold font in the description - as much as 1 single character activates the issue. If I remove all bold font, the problem doesn't arise.
Remembering that eBay advise using bold font for sub-headings - which is exactly what I am trying to do - this now poses a whole new issue.
During the listing creation for a DVD, when the UPC number is added to the item specifics, the draft is automatically updated with quite a lot of pre-filled information and refreshed. This step activates the aforementioned unwanted changes.
Apart from removing all bold font from every listing, does anyone have any suggestions on how to fix this issue?
on 30-03-2025 07:28 PM
I use bold for all my descriptions and nothing seems to have changed
on 03-04-2025 05:28 PM
something's going on...
from the US boards:
Current known technical issues - updated as of 3/3... - The eBay Community
on 04-04-2025 01:35 AM
Thanks for that.
This was doing my head in.
After hours and hours of trial and error, I made a couple of changes 2 days ago and the problem seems to have been rectified.... or at least for the time being.
I'm pretty sure (99.9%) that it has something to do with a certain 3rd
party account integration. Once disconnected, the problem disappeared. Coinkydink? Maybe... but methinks not.