• Resolved blueg2017

    (@blueg2017)


    When field mapping a Google Local Products Inventory I did the following:

    For the google local proudcts attributes I selected store code and mapped it to a static value which was my Google Business store code that I just created. I tried just having the code, or like in some of the topics here, tried placing a pipe right after it. Both techniques generate this error:
    <store code>GBOOC1</store code>
    —————–^
    Any ideas of why this is happening?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Hi,

    Thanks for using our plugin and reaching out to us.

    Our plugin only supports TXT format for Google Local Product Inventory feeds and not XML (XML can’t even be selected during configuration so I don’t know how you did that). So please make sure you select TXT format instead of XML.

    https://www.dropbox.com/s/vmzvcha9ekw8lc6/Screenshot%202021-11-15%20at%2008.20.41.png?dl=0

    Thread Starter blueg2017

    (@blueg2017)

    The way I was able to select XML was by going back into the general settings for the feed after it had been created. For some reason it will give you the option of selecting XML which was not an option during the initial setup.

    Switching it back to TXT produces a feed that only contains:
    id,quantity,price,store code

    Shouldn’t it have actual product info?

    Hi,

    That is probably because you forgot to add a pipe behind the store code.
    Please see: https://adtribes.io/how-to-add-multiple-store-codes-to-your-google-local-products-inventory-feed/

    Thread Starter blueg2017

    (@blueg2017)

    I tried that after reading researching through the topics here. I have the store id mapped to a static field with the following content:
    GBOOC1|

    I have hit refresh on the feed and it still generates a txt file with just the text:
    id,quantity,price,store code.

    SOLUTION: Rebuild feed from scratch. Since earlier I was able to switch it to XML and then back to TXT I figured maybe a setting was corrupted. That fixed the whole problem. Hope this helps for any future debugging. Thank you for your assistance.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘XML Parsing Error: not well-formed’ is closed to new replies.