leoneagle
Forum Replies Created
-
Hi, yes, I can confirm.
WordPress: Version 5.6.1
Yoast SEO for WordPress: Version 15.7
Yoast SEO Multilingual: Version 1.2.4
Easy Digital Downloads Multilingual: Version 1.3.4
WPML Multilingual CMS: Version 4.4.9
WPML String Translation: Version 3.1.7
WPML Translation Management: Version 2.10.5I’ve already followed the instructions on the link you sent me. It shows how to manually translate all the pages, including seo attributes. It could works for ecommerce with few items. We don’t need this approach. We want translate in automatic way all the “content types” and “taxonomy” filed of Yoast Seo, in search appearance.
And, as I explained before, all works perfectly: in the source code of the page you can see that the fields are translated correctly.
What doesn’t work is this:
Let’s take our beats as an example. We use a modified version of EDD, so our beats, are basically EDD items, which are usually called “downloads”.1. On Yoast Seo / Search Appearance / Content Types, I write the default Seo description and the default title.
2. On WPML string translations, in the admin_text_wpseo_titles section I’m going to enter the relevant translations.
3. At this point in the source code of the pages the translations are created correctly.
However, if I check a random beat from the backend (an EDD item),in the Yoast SEO section, the italian translations do not appear, it keeps showing the English versions.
So, to sum up, it’s a problem of Yoast SEO visualization, because in the source code of the pages the translations are correctly created.
I hope I was able to explain the problem. Anyway, it is not a big problem. Just that at the beginning, not seeing the translation in the yoast seo section of the beats, we thought that this was not happening correctly.
Then, following this support ticket,
we discovered that in the source code of the individual beats pages in Italian, meta-description and seo title were translated correctly.Yes,
from here you can see the WPML String Translation page. As you can see, the string is translated. https://www.dropbox.com/s/01996m59d8wv6bw/WPML%20-%20String%20Translate.png?dl=0Here, instead, you can see the Yoast Seo section of the page: https://www.dropbox.com/s/ewd3pb663oj28ip/Yoast%20SEO%20-%20not%20translated.png?dl=0
As you can see, the string appears not translated.
However, here you can see the relative page source code: https://www.dropbox.com/s/ekw1170p4vbi51y/Source%20Code.png?dl=0
As you can see, the string is translated correctly and in the meta-description it appears exactly what it should appear.
So the problem is related only to what the Yoast Seo section shows in the metadecription filed and in the google preview field.
I hope I was able to explain the problem.
Best regards
GiovanniHi Md Mazedul,
first of all thanks for your kind reply.
I hadn’t thought to do this check because I didn’t know what and where to look but actually, looking at the source code, I could see that the variables appear correctly.For example in this
view-source:https://shine-library.com/downloads/nuovo-rock-leggero/There was also another problem, but that too has been resolved. Anyway, I want to share it with you in case you want to solve it.
We use WPML string translation to translate the default strings. I translate the default seo titles and meta descriptions with string translation, but in the Yoast preview you see the untranslated content. However in the source code of the page, the content is translated correctly.Thanks a lot for your help.
Giovanni- This reply was modified 5 years, 4 months ago by Steven Stern (sterndata).
- This reply was modified 5 years, 4 months ago by Steven Stern (sterndata).
Hi, I discovered that the incompatibility is with the “Google Captcha (reCAPTCHA) by BestWebSoft”. I need that plugin for protect the wp-admin page. Do you have any suggestions?
Ok perfect! now it works again! Thanks a lot!
Ok, if I uninstall the plugin and after I install the 1.6,
should I see again the slider or I’ve to create it again?Hi again,
I’m using the 2.17 version, so JQuery problems should be solved.
Now, I downloaded the previous version of your plugin. I thought of a solution.
If I unistall the actual version (2.0.3) and install the old working version, there’s a way to restore the carousel?It’s very strange. Yesterday the plugin was working perfectly. Why with the update it stopped working?
I updated to 2.0.1 but unfortunately the problem is still there: the carousel is not present. The only visible thing is a grey line… tested on chrome, safari and firefox, for mac and mobile.