yoast-acf-analysis icon indicating copy to clipboard operation
yoast-acf-analysis copied to clipboard

Published 20 hours ago • verified publisher icon Yoast

ACF custom fields on WooCommerce Products are not being scanned

Open josevarghese opened this issue 2 years ago • 10 comments

Issue moved from Jira: https://yoast.atlassian.net/browse/IM-2083 Reporter: @jeroenrotty

Related issue: https://github.com/Yoast/yoast-acf-analysis/issues/170

  • [x] I've read and understood the contribution guidelines.
  • [x] I've searched for any related issues and avoided creating a duplicate issue.

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?

  1. Install Yoast SEO, WooCommerce, ACF ,and ACF Content Analysis for Yoast SEO
  2. Create an ACF field (i.e. Text, Text Area or Wysiwyg Editor, or even image field) and tie the field group to the product post type
  3. Create a new product
  4. Add some text/image to the ACF field
  5. Note that the Yoast analysis doesn't detect any content

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.

josevarghese avatar Apr 25 '23 08:04 josevarghese

Please inform the customer of conversation # 959895 when this conversation has been closed.

josevarghese avatar Apr 25 '23 08:04 josevarghese

Please inform the customer of conversation # 980564 when this conversation has been closed.

josevarghese avatar Apr 25 '23 08:04 josevarghese

Please inform the customer of conversation # 981715 when this conversation has been closed.

josevarghese avatar Apr 25 '23 08:04 josevarghese

Please inform the customer of conversation # 1000584 when this conversation has been closed.

josevarghese avatar Apr 25 '23 08:04 josevarghese

Please inform the customer of conversation # 1004973 when this conversation has been closed.

josevarghese avatar Apr 25 '23 08:04 josevarghese

Any progress on this?

joedawson avatar May 20 '23 13:05 joedawson

Please inform the customer of conversation # 1019547 when this conversation has been closed.

josevarghese avatar May 22 '23 12:05 josevarghese

Hey! can I get a status update on this task? Thanks!

alexanderArsenault avatar Oct 23 '23 20:10 alexanderArsenault

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.

josevarghese avatar Dec 26 '23 06:12 josevarghese

Please inform the customer of conversation # 1112785 when this conversation has been closed.

shabnam611 avatar Mar 08 '24 10:03 shabnam611