Bug: Custom fields sometimes gets picked up, sometimes not
-
Hi!
I am configuring this plugin and initially thought this is the one but as I wanted to fine tune it a bit more I found erroneus behaviour regarding custom fields.
I have a custom field attached to products called “appsolute_product_condition” and I mapped this field to condition. The field can get a value “new”, “used” or “refurbished”. When I save a product the value “new” gets appiled by default.
In the feed sometimes it shows up in a few products but most of them not. I even made a rule that if the “Appsolute product condition” is empty it should replace it in the feed with the value of “new”.
(I don’t know for sure but I suspect that this condition maybe first looks for a custom field and if that exists it then evaluates if it is empty. However it should work if the custom field doesn’t exist it should also evaulate as empty. I hope you understand the difference.)
This is not only the problem, but in some products even if the custom field is present, the value is missing from the exported file. Could there be a caching issue of product data?
I am trying and debugging and digging into the code in the last 4 hours but I don’t find consistent behaviour.
The topic ‘Bug: Custom fields sometimes gets picked up, sometimes not’ is closed to new replies.