David, can you upload the error file you receive to your file manager? I'll take a look at the errors and let you know what I find out.

John,

I deleted it, but I can generate it again and let you know when I do.

In addition I've come across multiple other problems, and this is starting to drive me crazy! No offense to you.

The images on about half of my items don't show up in Google Base because the URLs are relative. I went to change them to absolute, but realized that the absolute image paths in thumbnails were causing IE to display an alert about non-secure and secure items being displayed on secure pages. I had changed these to relative to solve that problem. However, now that I look at my products about half my URLs are relative and half are absolute!

Please advise if we should be using absolute URLs in the Large Image paths in order for Google Base to display them, but relative in the Thumbnail Image paths so our customers don't get the security alert in IE.

David

I'll have to take a look at the image links in the feeds and see if I can figure out why some of yours are not absolute. I'll get back to you shortly.

After reviewing your feed and image paths, the error appears to be spaces in your image names. It appears that all the the relative paths contain a space in the image name, while the ones that generate the correct absolute urls have no spaces. There appear to be about 44 products that use images that contain spaces in the name that will need to be corrected.

Thanks John! I'm not sure why I thought there were so many more initially.

So does the feed automatically make the URLs absolute? And, should our image URLs be relative for the purpose of not receiving the alert in IE? I just looked in IE at a product I have with an absolute URL for the thumbnail path, but it appears NetSol is stripping the absolute portion. Is that correct? Thanks again,

David

Yes, the feed should be generating all absolute urls from your relative paths unless there is an issue. Also, image paths are stored as relative, so you shouldn't need to use absolute paths.

Thanks for the help John.

Eddie:

I have always used the long description when using the export feature to create the G Base feed. I would also like at least the opition of having this description.

Another problem I've noticed as a result of looking into this feed is that many of my "LargeImagePath"s are to my detailed images, rather than the main product image. So the Google Base image for a Christmas tree is a close up of a needle. Is there any way that this can be corrected in bulk? My images got supremely messed up during the migration. Clicking on a "more images" button on my site usually brings up the same image, and then the second is the detailed image.

I used the new Google base feed and was happy to see it however I recevied this message this morning from GoogleBase showing my feed was removed and making another case for using the long description instead of the short description.

"- Incorrect descriptions: Some of your items include incorrect
descriptions. The descriptions in your data feed should match the
descriptions appearing on your website, contain all the text describing
each item, and shouldn't simply repeat the title of your item. By
including the full item descriptions from your website, we'll be better
able to match your items to users' queries."

I do repeat the title for the short description since I really don't have a "short" description. I believe I read on this forum that some people do not even use the short description. It is usually redundant of the title.

We really need to be able to specify what information we want to pass over in our google feed. I love that I can generate it on the fly and schedule it in Google to upload. I will probably have to start manually creating my own feed again but would really like this feature to be fixed.