identifier_exists bug

  • Resolved visumgroup

    (@visumgroup)


    6 years, 11 months ago

    there appears to be a bug in the field mapping : g:identifier_exists.

    in my setup it always defaults to yes if i allow the plugin to determine, and it should be no.

    so, i changed this to static value and entered “no”. the trouble is that this is then creating an empty field that has no field name just a value of no, and the identifier has no value

    not sure that makes sense, but it creates a name/value pair that is
    identifier_exists: (blank)
    blank : no

    so google cannot process the feed as the names and values do not line up

    i have tried many times, same result always.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter visumgroup

    (@visumgroup)

    so in trying to fix this i moved identifier field to end and did static of no, this sort of seemed to work, but, now the field that was in that place (4th one from bottom) is now brand and value set to pa_brand (and this was working) and was picking up “snurk” but since moving identified to bottom the brand only ever returns a value of “yes” (which is what the identifier value always returned ??

    it seems its not mapping things properly

    Thread Starter visumgroup

    (@visumgroup)

    also, i am having to use txt feed as google reported error in xml feed saying not formatted properly

    Thread Starter visumgroup

    (@visumgroup)

    i could also find no way of selecting products in a categoryid ? so for testing i just had to use a product id

    Hi Darren,

    I replied to your support question by e-mail. Let’s follow up by email.

    Best,
    Joris

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘identifier_exists bug’ is closed to new replies.