Open josevarghese opened 1 year ago
Please inform the customer of conversation # 959895 when this conversation has been closed.
Please inform the customer of conversation # 980564 when this conversation has been closed.
Please inform the customer of conversation # 981715 when this conversation has been closed.
Please inform the customer of conversation # 1000584 when this conversation has been closed.
Please inform the customer of conversation # 1004973 when this conversation has been closed.
Any progress on this?
Please inform the customer of conversation # 1019547 when this conversation has been closed.
Hey! can I get a status update on this task? Thanks!
Hi @alexanderArsenault
Thanks for getting back to us and sorry for the delay in responding.
Our product team will assess the severity of the report in relation to other open bug reports and new features. Based on their assessment, the bug report will be given a priority level. Our developers work on the highest priority issues first. Unfortunately, this means we cannot give you an estimate of when they'll start working on your report.
As soon as our development team has a clear indication of which release this problem will be solved, we'll send you an update on this issue.
Please inform the customer of conversation # 1112785 when this conversation has been closed.
Issue moved from Jira: https://yoast.atlassian.net/browse/IM-2083 Reporter: @jeroenrotty
Related issue: https://github.com/Yoast/yoast-acf-analysis/issues/170
Please give us a description of what happened.
A customer reached out that Yoast SEO is not scanning custom fields tied to WooCommerce Products. While troubleshooting, we noted that on our local sites this isn’t happening either.
How can we reproduce this behavior?
Expected Results Yoast SEO is able to scan the fields.
Actual Results Yoast SEO is not pickup up the content in the ACF fields.
Impact Yoast SEO and ACF users running a WooCommerce webshop and having custom fields set on products.