-
Notifications
You must be signed in to change notification settings - Fork 20
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
Headings, keyword, and word count fail to be scanned and scored when custom field is on a Product Category Page #14
Comments
Please inform the customer of conversation # 153070 when this conversation has been closed. |
I understand that the plugin does not yet support WYSIWYG editor in WordPress yet. However, this issue report may be helpful to point users too. |
@Pcosta88 I think this isn't an issue with this plugin but with the main Yoast SEO Plugin. The field that is not being analysed isn't coming from ACF but is the term description, right? So if that is true and it has nothing to do with ACF we can't do anything about it here. |
@kraftner If you add an ACF field to a Product Category, does the ACF Analysis plugin then pick it up? I ask as for some reason with my ACF plugin I am unable to add text fields to a product category |
Sorry, my fault, long day. I looked at the first screenshot and assumed you're talking about the default WYSIWYG of the term. Got it now. So I think this should be covered by the inclusion of the WYSIWYG (also see #2), but we should probably double check. Sorry for the confusion. |
@Pcosta88 Now that 2.0 is released, can you check if this is fixed? |
@kraftner I am not able to reproduce this issue. For some reason I am unable to get an ACF to display on a Product Category page. |
related? #59 |
What did you expect to happen?
Yoast ACF Analysis would count the Product Cat text section
What happened instead?
It did not
How can we reproduce this behavior?
1.Add text to the description area
2.Add text to Product Cat section
3.See that Yoast does not count it
Can you provide a link to a page which shows this issue? n/a
Technical info
The text was updated successfully, but these errors were encountered: