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.
Tagged: Compatibility
This topic contains 7 replies, has 2 voices.
Last updated by Pieter 1 year, 9 months ago.
Assisted by: Lauren.
Author | Posts |
---|---|
May 16, 2023 at 5:30 pm #13658845 | |
Pieter |
WPML SEO with Yoast and auto translating strings of admin_texts_wpseo_titles |
May 16, 2023 at 6:04 pm #13659019 | |
Pieter |
> In the meantime, as a workaround, you can edit the string translations to add the correct title and sitename terms in the translation. Yes, I understand that I can do that, thank you. That was not the point of my ticket. It was to report a bug. |
May 18, 2023 at 7:12 pm #13674689 | |
Lauren Supporter
Languages: English (English ) Timezone: America/New_York (GMT-05:00) |
After further testing, I was not able to reproduce this issue. Please tell me, did you send this string from string translation to Automatic Translation? Was it included in a group string? Also, after using the workaround to resolve the translation of the SEO title, please delete the string from your string translation table. Then reload the front end of your site. Is the string automatically registered and automatically translated? |
May 19, 2023 at 9:45 am #13677583 | |
Pieter |
Hello Lauren, In String Translations I selected the admin_texts_wpseo_titles text-domain. I then clicked the "Display all results" link which showed all 33 strings. Next step was to select all the strings and click the Translate button. The way I solved the issue was to "translate" them all manually. |
May 19, 2023 at 2:43 pm #13680287 | |
Lauren Supporter
Languages: English (English ) Timezone: America/New_York (GMT-05:00) |
Okay, I was originally thinking this string was automatically translated somehow without being sent to translation. This makes more sense, because machine translation (automatic translation) only knows to translate what is sent to it. In your case, this string should not have been sent to translation, because there was no need to translate it. Once you did send it to translation, then the correct way to fix it was to manually change the translation back to what it should be. I hope this makes sense. |
May 19, 2023 at 2:46 pm #13680293 | |
Pieter |
okay thank you, but what I don't understand is that if translation of these strings is not necessary, then why are they added to the string translations table in the first place? |
May 19, 2023 at 3:27 pm #13680415 | |
Lauren Supporter
Languages: English (English ) Timezone: America/New_York (GMT-05:00) |
In your case the strings were not needed to be translated, but other cases sometimes clients wnat to use a different structure or would like to change the translation. So they are added as the option in case someone would want to translate them. |
May 19, 2023 at 3:48 pm #13680503 | |
Pieter |
Okay, thank you. |