Important Notice from AspDotNetStorefront
It is with dismay that we report that we have been forced, through the action of hackers, to shut off write-access to this forum. We are keen to leave the wealth of material available to you for research. We have opened a new forum from which our community of users can seek help, support and advice from us and from each other. To post a new question to our community, please visit: http://forums.vortx.com
Results 1 to 4 of 4

Thread: Tracking down errors in google feed?

  1. #1
    bundleshop is offline Junior Member
    Join Date
    Sep 2009
    Posts
    10

    Default Tracking down errors in google feed?

    After uploading our product feed to google, it returns a few "invalid encoding" errors scattered at (seemingly) random spots throughout our product feed. It returns an item number and line number it finds problematic, but when I open my xml file in a text editor the lines numbers don't even remotely match the line numbers reported as problematic, and there seems to be no way to track down item numbers other than trying to wade through lots of xml. Any solutions?

  2. #2
    ASPAlfred is offline Senior Member
    Join Date
    Nov 2007
    Posts
    2,244

    Default

    Could you paste in here a couple of those lines containing an "invalid encoding" errors to check?

  3. #3
    bundleshop is offline Junior Member
    Join Date
    Sep 2009
    Posts
    10

    Default

    what I meant to say is that I can't even figure out which ones were tagged invalid because the line and item numbers google returned don't match line numbers in my xml file and I can't see a way to find item numbers in the xml file

  4. #4
    VibeCommerce is offline Member
    Join Date
    Dec 2006
    Location
    Grandville, MI
    Posts
    63

    Default

    In general this can be an enormous headache. One way to "help" is to open up your feed (like googlebase.xml) in IE and it will show you generally where it errors out - I've found this helpful in tracking down pesky characters. Not a silver bullet, but perhaps, a little more help than Google's vague errors.