-
Notifications
You must be signed in to change notification settings - Fork 798
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WooCommerce Analytics: better fallback when conflicting with plugins changing product data #11301
Comments
#10216325-hc |
This issue has been marked as stale. This happened because:
No further action is needed. But it's worth checking if this ticket has clear reproduction steps and it is still reproducible. Feel free to close this issue if you think it's not valid anymore — if you do, please add a brief explanation. |
This was also brought up in #20743, and is apparently caused by Elementor Pro:
|
We ran into this today on a T51 partner site that is not running Elementor. Single product pages load for logged in users, but return the fatal when logged out. Toggling the Jetpack woocommerce-analytics module off resolved. Active plugins:
Edit: This appears to be caused by the WooCommerce Single Product block accessing |
Fixes #11301 Some plugins make changes to Products and Orders, overwriting methods that we call in Jetpack. Let's check for such methods before we use them on our end, to avoid issues.
Steps to reproduce the issue
wc_get_product
.We should aim to have a better fallback than this fatal in
get_product_details
.The text was updated successfully, but these errors were encountered: