@kambro The %%wc_price%%
and %%wc_shortdesc%%
variables are only available if the Yoast WooCommerce SEO add-on plugin is installed on the site.
Unfortunately, per the forum guidelines, we cannot answer questions about our premium products. For questions about WooCommerce SEO or any other of our premium plugins please contact our support team directly by emailing support@yoast.com.
Thank you for your understanding.
Thread Starter
kambro
(@kambro)
Thank you for your answer. I understand you are not able to help for premium plugin. I’ve not yet the Yoast WooCommerce SEO add-on. But I dont now why the %%ct_book_author%% variable dont have result.
Here is the url of the dashboard book author page : /wp-admin/edit-tags.php?taxonomy=book_author&post_type=product
Thanks in advance.
Hey @kambro,
Thank you for your reply.
I understand that you want to see the book_author field show up correctly in our preview while you are optimizing your content. Please know that while the preview might not show the actual correct content/text, can you double-check if the output in the source code is actually showing the author’s name?
We’re looking forward to your reply.
Thread Starter
kambro
(@kambro)
Thank you for your help.
What do you mean by “double-check if the output in the source code is actually showing the author’s name”
Where and how can I check it?
Best regards.
Hey @kambro,
If you’d save the post or page you showed in your screenshot before and visited the front-end side of that content. Then check if the source code has the author details in it. If you are not so familiar, we have a help article on this: https://yoast.com/help/view-page-source-site/
Thread Starter
kambro
(@kambro)
Thank you very much ; indeed, the book author is present in the page source.
Hey @kambro,
Thank you for letting us know. Happy to hear that is only a visual bug in the preview but does work on the front end of the site.
We’ll be marking this topic as resolved for now. We do have an open report for improving how we can handle custom fields in the preview – hopefully, we’ll be able to fix this in the future.
Thread Starter
kambro
(@kambro)
Thank you for your service.