Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support shahzeen(woo-hc)

    (@shahzeenfarooq)

    Hi there!

    I have investigated the error message and found that there is a thread on GitHub related to this issue: https://github.com/woocommerce/woocommerce/issues/34682.

    Our developers are already aware of this and are working to resolve the issue as soon as possible. You can monitor the progress via our public GitHub repository here: https://github.com/woocommerce/woocommerce/issues/34851.

    Additionally, a?post on the google forum?indicates that it’s a known issue. But I cannot confirm that information comes from anyone on the google team.

    Thank you

    Thread Starter mklusak

    (@mklusak)

    Well, those are two years old links and issues. The relevant one is https://github.com/woocommerce/woocommerce/pull/52871 … this change made it to the core three weeks ago. And after updating my website, this very problem occured, instead of being resolved. And it didn’t even exist before.

    Changelog:

    = 9.5.0 2024-12-16
    Fix – Fix “missing ‘price’ property in ‘offers'” error in Google Search Console

    Plugin Support shahzeen(woo-hc)

    (@shahzeenfarooq)

    Hi there!

    Apologies for the confusion. I accidentally included the wrong link in my previous reply (the second one, which is already closed). I actually found the following link related to this bug, which was opened two years ago here: https://github.com/woocommerce/woocommerce/issues/34682 and have not closed yet which caused the mix-up.

    However, Please disregard my previous response. I can see that you have already been in touch with our developers in this thread: https://github.com/woocommerce/woocommerce/pull/52871. They have suggested running a conflict test by deactivating all plugins and custom code to see if the issue persists.

    Additionally, I noticed you replied to the developer in the closed thread. As they’ve already suggested, please create a new ticket for further discussion. Share the details there and tag the developer so they can investigate further.

    If you’ve already run the conflict test, I would suggest adding that information in the new GitHub thread as well.

    Thank you!

    Thread Starter mklusak

    (@mklusak)

    Well, Github “new issue” hint suggested to write here first, so I did.

    But – the conflict test really sorted it out (). Both affected sites have FOX currency switcher installed, and when deactivated, the issue is gone and structured data are valid.

    So, I reported it there and will be waiting for response.

    Thank you!

    Plugin Support Moses M. (woo-hc)

    (@mosesmedh)

    Hi @mklusak,

    Thank you for sharing the results of your conflict test. Based on your explanation, it appears the issue isn’t with WooCommerce but rather caused by the plugin ‘Fox Currency Switcher.’

    You can continue addressing this in the plugin’s support forum. If you encounter any other issues related to WooCommerce, feel free to create a new thread for assistance.

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.