There is a bug in Google Base that is causing file format errors to be generated for all images uploaded in the single-item editor. Our development team is aware of the problem, and they're working to get it resolved as soon as possible. Unfortunately, we cannot provide an ETA for a fix but we will post updates in this thread as they become available.
We have a fix ready for this problem that will be included in our next build release, currently scheduled for the end of this week. We apologize for any inconvenience caused. Should you have any further questions or concerns, please feel free to reply to this thread.
Thanks for fixing the problem. I can now upload with Camino (so I assume Firefox would work as well). However, Safari (417.9.2) still cannot. I'm running OS X 10.4.6.
The image upload problem in Safari has been verified - thank you for bringing this to our attention. Our development team is investigating the issue now. We'll post an update as soon as the problem is resolved.
friday 5/12, all images i uploaded were showing only x-boxes. attempted again today (5/15) and still having the same problem. using microsoft explorer, by the way
We're working on a fix for the problem causing broken images to appear in item pages now. This issue is not related to the problem we experienced with image uploads in April.
We'll post a follow up message as soon as this matter is resolved.
The problem with images not displaying in item pages has been resolved. If you still experience problems with your images, please let us know by submitting a ticket to Google Base Support.
Google Base Guide wrote: > The problem with images not displaying in item pages has been resolved. > If you still experience problems with your images, please let us know > by submitting a ticket to Google Base Support.
Attempting to upload a GIF (Safari 417.9.3, OSX 10.4.6) for a single item results in an "invalid image type" popup error message. The file extension and image data are correct, however.
I'll submit to GB Support ... just wanted to make sure readers of the thread would see that the issue is apparently not quite resolved just yet.