Skip to content
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

ACF custom fields on WooCommerce Products are not being scanned #336

Open
2 tasks done
josevarghese opened this issue Apr 25, 2023 · 10 comments
Open
2 tasks done

ACF custom fields on WooCommerce Products are not being scanned #336

josevarghese opened this issue Apr 25, 2023 · 10 comments
Labels

Comments

@josevarghese
Copy link

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

Related issue: #170

  • I've read and understood the contribution guidelines.
  • 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
Copy link
Author

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

@josevarghese
Copy link
Author

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

@josevarghese
Copy link
Author

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

@josevarghese
Copy link
Author

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

@josevarghese
Copy link
Author

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

@joedawson
Copy link

Any progress on this?

@josevarghese
Copy link
Author

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

@jeroenrotty jeroenrotty added the IM label May 30, 2023
@alexanderArsenault
Copy link

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

@josevarghese
Copy link
Author

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.

@shabnam611
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants