I can see in the "yoast_indexable" table post_status as publish in the secondary languages After auto-translation with the new settings.
Product URL : hidden link
First, Still we have an issue, with this new settings we are not able to see "open_graph_image", "open_graph_image_id", "twitter_image_source", "twitter_image_id" and "twitter_image" etc data in the "yoast_indexable" but we are able to see with old setting after auto translation.
Video Recording : hidden link
Second, Yoast SEO breadcrumb does not work on translation page.
Find the screenshot : hidden link
Note : Try creating a new product and test it. don't test with old product.
Here is the new ticket. Can you please help me replicate the issue on a clean installation of WordPress? You can access the admin area directly with this link hidden link
I've tried to replicate the issue there but still see the "open_graph_image", "open_graph_image_id" ... data in the "yoast_indexable" table.
I'm not able to replicate the issue in your admin, but we found out what an issue. let me explain you.
Steps of the product auto-translation :
-----------------------------------------
First vendor creates a product, then admin publishes the product from store-manager, after that admin will process auto translation. after this process we are not able to see "open_graph_image", "open_graph_image_id" etc data in the "yoast_indexable" table.
See the screenshot of the store-manager product edit page : hidden link
Product listing URL (backend) of the store-manager : hidden link
Found out:
----------------
If we publish product from the WooCommerce product edit page then we are able to see "open_graph_image", "open_graph_image_id" etc data in the "yoast_indexable" table.
See the screenshot of the WooCommerce product edit page : hidden link
Product listing URL (backend) of the WooCommerce : hidden link
You can test below products publish from woocommerce and store-manger.
From woocommerce :
-----------------------
This is the product published from the woocommerce by admin (After auto translation you can see "open_graph_image", "open_graph_image_id" etc data in the "yoast_indexable" table.) :
Product URL : hidden link
From Store Manager:
------------------------
This is the product published from the store-manager by admin (After auto translation you not able to see "open_graph_image", "open_graph_image_id" etc data in the "yoast_indexable" table.) :
Product URL : hidden link
Note : Vendor doesn't have capability to publish product from their login.
So issue is that if admin publish product from the store-manager then we are not able to see "open_graph_image", "open_graph_image_id" etc data in the "yoast_indexable" table.
So I understand the issue is related to the plugin WooCommerce Multivendor (WCFM) and its addon Frontend Manager: Store manager page in the frontend.
I suggest you use the automatic translation option "Let me review it before it gets published" and go to WPML > Translations to approve translation to see if it helps.
If not, can you please help me replicate the issue on the sandbox site with those plugins? It could be a compatibility with 4 plugins, not just WPML itself.
I suggest you use the automatic translation option "Let me review it before it gets published" and go to WPML > Translations to approve translation to see if it helps.
*Reply* : This setting is not useful for us. we already discussed with this setting - if we use this setting then after auto translation in the "yoast_indexable" table showing as draft products.
See this ticket URL : https://wpml.org/forums/topic/after-auto-translating-in-the-yoast_indexable-table-showing-as-draft-products/
And also this setting "Let me review it before it gets published" is slowing down our translation work a lot because we have so many languages, and I would therefore very much like to change that setting to “Publish right away without reviewing”.
If not, can you please help me replicate the issue on the sandbox site with those plugins?
*Reply* : We have replicated the issue on the sandbox site, you can create a new product from the frontend manager then try to auto translation and see the data in the "yoast_indexable" table.
URL of the frontend manager : hidden link
I can see the issue on the sandbox site after creating the product in the frontend with the WCFM Frontend feature. I'm discussing this issue with our 2nd tier support and update you here when I have something to share.
The issue has been escalated to our compatibility team and currently, I don't have more information about this. I will let you know once I have any information.
I got some new information from our compatibility team while investigating the issue: The SEO data is only generated in the translation product if the original product has the "_yoast_wpseo_primary_product_cat" custom field, and this field is missing in products created using the front-end editor WCFM.
There is a workaround to fix the issue:
1. In the WP dashboard (wp-admin), edit the product in the original language.
2. Click on "Update" (this will generate the _yoast_wpseo_primary_product_cat field)
3. Click on "Update" again (this will generate the SEO data for the translations)
or you can update products in bulk on the Products page.
It is a compatibility issue between Yoast and WCFM, if it works on your end, please also report this issue to the Yoast and WCFM plugin author.
The SEO data is only generated in the translation product if the original product has the "_yoast_wpseo_primary_product_cat" custom field, and this field is missing in products created using the front-end editor WCFM.
Reply : If is this correct then why we are getting SEO data in the secondary languages after auto translation if we're using this setting "WPML -> settings -> Automatic translation -> Let me review it before it gets published" ?
FYI : with this setting "WPML -> settings -> Automatic translation -> Let me review it before it gets published" the product status showing as draft but we are getting all SEO data in the secondary languages.
Let me discuss that case with the compatibility team. I think that the option "Let me review it before it gets published" will trigger the Update function like steps 2 and 3 in the workaround above.
Our compatibility team sees that: When we select "Let me review it before it gets published", it means that we will need to review it, and then publish it. And when we do that, it does not fail in the YOAST conditions, so the field is created.
Have you reported this issue to Yoast and WCFM author? Meanwhile, you can use the workaround above to update products in bulk to generate the SEO data for the translation products.
Have you reported this issue to Yoast and WCFM author?
* Reply: * Not yet, because I was waiting for your reply. Are you sure this is a bug of Yoast or WCFM?
Yes, our compatibility developer has investigated the issue and found that the issue is related to the Yoast custom field "_yoast_wpseo_primary_product_cat" when creating the product in the WCFM frontend.
Please share this ticket and feedback from our compatibility developer with those plugin authors then let me know their feedback.
Thanks for your co-operation.
The topic ‘[Closed] We are not able to see "open_graph_image", "open_graph_image_id" data in the "yoast_indexable"’ is closed to new replies.
