Jeff Alvarez
Forum Replies Created
-
Hi @jpoyntz ,
It’s likely that they are using these following features for GMC:
https://support.google.com/merchants/answer/13837705?hl=en &
https://support.google.com/merchants/answer/7050148
https://support.google.com/merchants/answer/13838102
or: https://support.google.com/merchants/answer/14768922?hl=en&sjid=18036471924573912640-NC- This reply was modified 8 months, 2 weeks ago by Jeff Alvarez.
Hi @indigo5andvinecom ,
woosea_gtin, mappable field is only available on our Elite plugin or premium plugin. You mentioned you have a field called _woosea_gtin is this a custom field?
So if you select this then it’ll likely not work as intended:
If it is a custom field go to Product Feed > Settings Clear Attribute Cache and then see if there’s another mappable field
Hi @iqcalex ,
On the latest update we have a data migration for the rules and filter that happens automatically when updating our plugin: https://ibb.co/7tGsfz6D
Can you please send in a screenshot on how your rules and filters are set? Also, on what version are you currently on prior to the update?
Here’s the hotfix zip: https://drive.google.com/file/d/1v5egsK6aoqC5aOzL8WR9O_pf3enl3QPs/view?usp=sharing feel free to install/update the plugin on your end.
Ensure that you have a backup ready before proceeding. Alternatively, you can remain on the downgraded or working version and wait for the official update.
There’s currently no ETAs when it’ll be publicly available.
Hi All,
I confirm this is a bug, it only seems to happen when the value is only numbers. I’ll raise it up with our developers to get this resolved.
Hi @jkont ,
It might be due to something else on your server that’s causing the issue because we aren’t able to replicate it and have no other users reporting this behavior.
Though, we’ll note it as a potential bug and keep track of things.
Hi @s1lviu ,
Try using this snippet, it’ll force them to use a certain price format but do note that this will affect all the feeds. It’s not currently possible to make it only apply to certain feeds: https://ibb.co/hFygw947
function modify_product_feed_product_id($product_data) {
if (isset($product_data['id'])) {
$product_data['price'] = '123.55'; // Set to a test value
}
return $product_data;
}
add_filter('adt_get_product_data', 'modify_product_feed_product_id', 10, 1);Alternatively you could use the rules and filter:
https://ibb.co/LDxF80L9
https://ibb.co/DD1XX1wf- This reply was modified 8 months, 3 weeks ago by Jeff Alvarez.
Hi @iqcalex , @gerhardst17
Yes it does output the value: https://www.loom.com/share/8eb4e14604ad4745b37f906ae513f9bc
I have the latest version installed, try re-installing the plugin or create a new feed and see if the output shows.
Also, check that you are viewing the xml file via incognito as you may be viewing a cached copy of the page. You can try clearing your server/plugin cache and see if that helps.
Please send in your setup via images/screenrecording or your debug log and I’ll try to replicate the issue:https://adtribes.io/knowledge-base/send-your-debug-log-to-support/Hi @jkont ,
You can downgrade to the previous working condition of our plugin, as previously mentioned we’ve released an update for this. We aren’t able to replicate the behavior or having other users reporting such errors so it’s hard to say if it’s a bug.
Downgrade options here: https://wordpress.org/plugins/woo-product-feed-pro/advanced/
Also, do a basic debug to confirm that the issue isn’t due to 3rd party plugins or themes. Also, create a new feed and see if that helps.
If you have caching/server caching try disabling them and see if that works. Also, go to Woocommerce > Status > Scheduled Actions >>> Failed Actions and look for any failed feed refresh and see if it gives any details.
Hi @antonellov10 ,
For the sale price, at the moment the default sale price is only supported if you are using 3rd party plugins then it’s likely due to that.
As for the price mapping, try just the Price Mappable Field. By Default, it’ll always add Tax: https://ibb.co/v4YNQ6ZD
Also, please run a basic debug to confirm that the issue isn’t due to a plugin or theme conflict. Do this by disabling all the plugins except Woocommrce and product feed, also use the storefront theme.
If you still face issues you can downgrade to the previous working versions: https://wordpress.org/plugins/woo-product-feed-pro/advanced/
For the missing products, try removing all your rules and filters to test.
- This reply was modified 8 months, 3 weeks ago by Jeff Alvarez.
Hi @s1lviu ,
For the price mappable fields you will need to use any of our price mappable fields because most sites require it to follow a specific format.
Also, static fields for the price in general will be empty (even whole numbers). And you can downgrade to the previous working version to get it up and running.
Is there a reason you are using static fields for the price?
Hi @iqcalex,
Can you please confirm if you are using a Google Feed/Shopping template? I’m able to view the g:store_code mappable field.
Could you also please send a recording of the error or how you replicate it? The video may give us some clues on how you are facing this issue
Hi @antonellov10 ,
– 22% VAT
Try using the regular Price and sale price mappable field these options by default include tax. I’ve also just tested and it’s working as intended:https://ibb.co/20Tpg1FW
https://ibb.co/MD4wJxx0
https://ibb.co/dJByD30P
https://ibb.co/MDWVMpYW-Preview don’t work
Looks like you have the category equal to, this means the product must have X category and be out of stock to be excluded. Try removing the filter/rule, refresh the feed and see if that works.-New Feed everyday
Yes, this is a known bug please go to Product Feed > Settings > and run the Fix Duplicated FeedsHi @kikiluksic,
Thanks for that information but I’m still unable to replicate the error. I’ll consult our developers about this but I’m still unable to replicate the error: https://www.loom.com/share/de005a8cd64444baae721a79c89e912e
Is there a specific step you did to replicate the error and have you tried creating a new feed and see if that still causes the error?
I’ll consult with our developers regarding this as a potential bug but without an accurate way to replicate the behavior it’s hard for us to quickly apply a fix.