Skip Navigation

This thread is resolved. Here is a description of the problem and solution.

Problem: How to translation additional focus keywords in Yoast SEO Premium

Solution: It is happening because Yoast using *_yoast_wpseo_focuskeywords* meta key to store the focus keywords 2 to 5. Only first focus keyword is stored in *_yoast_wpseo_focuskw* meta key. And 2 to 5 keywords are storing in JSON formats. As a workaround please try the following steps.

1) Visit *wp-content/plugins/wordpress-seo-premium* folder
2) Open *wpml-config.xml* file for edit
3) Add the following code after line 7

<custom-field action="translate">_yoast_wpseo_focuskeywords</custom-field>

4) Save the changes
5) Visit the backend. Then update the Page and open the Page for translation
6) You can see the rest of *Focus Keywords* in JSON format for translation

Relevant Documentation:

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

This topic contains 8 replies, has 2 voices.

Last updated by reneA-5 4 years, 5 months ago.

Assigned support staff: Bigul.

Author Posts
June 23, 2017 at 6:57 pm #1304710

reneA-5

I am trying to: translate additional focus keywords for Yoast SEO Premium

URL of (my) website where problem appears: hidden link

I expected to see: strings to be translated, however it seems these are not offered.

Instead, I got: I have mostly set 4-5 additional focus keywords in the German pages, however in the English translation I find only one translation (additional focus keywords are not yet translated). How to go about it? Add them manually
Steps to duplicate the issue: See screen-cast here: hidden link

June 26, 2017 at 10:23 am #1305503

Bigul
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Hi ,

Thank you for contacting the WPML support. We are happy to help you.

Please check the following tutorial. Try the exact steps with a new Page or Post and translate it to a secondary language. Then make sure you are still having the issue.

https://wpml.org/documentation/plugins-compatibility/using-wordpress-seo-with-wpml/

It would be nice if you can provide me the WordPress debug.log (not WPML debug information). Please check this page for instructions https://wpml.org/documentation/support/debugging-wpml/

To enable it, open your wp-config.php file and look for define(‘WP_DEBUG’, false);. Change it to:

// Enable WP_DEBUG mode
define( 'WP_DEBUG', true );
 
// Enable Debug logging to the /wp-content/debug.log file
define( 'WP_DEBUG_LOG', true );
 
// Disable display of errors and warnings 
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );

In this case, the errors will be saved to a debug.log log file inside the */wp-content/* directory. Please do the steps to reproduce the bug and check you are getting any errors or warning related to WPML in the log file.

If you can paste your debug.log to http://pastebin.com/index.php and provide me that link it would be great! (This is the cleanest way because sometimes the logs are long and create a complete mess in discussion).

I have a request. Please do the following steps after a site backup for the expected performance of your site.

1) Please upgrade your MySQL version to 5.6(if you are not using MariaDB), the minimum required MySQL version for WPML. Check this article for more details -- https://wpml.org/home/minimum-requirements/

2) Increase *WP Memory Limit* to *128*(the minimum required memory limit for WPML) or more. Please check the following link for more details

https://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP

--
With Regards

Bigul

June 27, 2017 at 7:36 am #1306225

reneA-5

Good morning to you again, Bigul. Further to my second issue, please be informed that I have arranged for WP debug mode. Here is a copy of the debug.log: https://pastebin.com/Kek1UjXV
Thanks in advance, Cheerio, René

June 27, 2017 at 5:23 pm #1306874

Bigul
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Hi ,

Thank you for the updates. I would like to access admin area of your site for further checking. Please fill the private details fields after a full site backup. Check the following links for more details about private information sharing.

hidden link

https://wpml.org/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/

Please allow me to make a duplicator copy of your site using Duplicator plugin(https://wordpress.org/plugins/duplicator/) for debugging the issue locally.

--
With Regards

Bigul

June 28, 2017 at 8:13 am #1307247

Bigul
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Hi,

Thank you for the login information. I made a duplicator copy of your site now. Will debug it locally and get back to you as soon as possible. Please wait.

--
With Regards

Bigul

June 29, 2017 at 8:09 am #1308189

Bigul
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Hi,

For your kind information, I can reproduce the issue with your duplicator package and the bug is existing after the initial debugging procedures. Therefore I have forwarded the details to our second tier team and waiting for their feedback. Please wait.

--
With Regards

Bigul

June 29, 2017 at 9:44 am #1308326

reneA-5

Good day to you, Bigul, and many thanks for your further investigations on this issue!
Cheerio, René

June 29, 2017 at 12:50 pm #1308561

Bigul
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Hi ,

For your kind updates, it was happening because of a compatibility issue between Yoast Premium and WPML. I have forwarded the details to our compatibility team for further debugging. As a workaround please try the following steps and let me know your feedback.

1) Visit *wp-content/plugins/wordpress-seo-premium* folder
2) Open *wpml-config.xml* file for edit
3) Add the following code after line 7

<custom-field action="translate">_yoast_wpseo_focuskeywords</custom-field>

4) Save the changes
5) Visit the backend. Then update the Page and open the Page for translation
6) You can see the rest of *Focus Keywords* in JSON format for translation

Please consider it as temporay workaround. Will get back to you when I have a feedback from our developers. It is happening becuase Yoast using *_yoast_wpseo_focuskeywords* meta key to store the focus keywords 2 to 5. Only first focus keyword is stored in *_yoast_wpseo_focuskw* meta key. And 2 to 5 keywords are storing in JSON formats. Please check the attached images for more details.

--
With Regards

Bigul

2017-06-29_1557.png
2017-06-29_1556.png
June 29, 2017 at 6:05 pm #1308915

reneA-5

Good evening to you, Bigul, and thank you so much for all your help. Problem solved with the work-around as suggested by you. Hopefully, this will be correncted soon in the orderly plugin as well. Once more, many thanks for your help!