[Resolved] Teaser Box from Total theme -> url not translated
This thread is resolved. Here is a description of the problem and solution.
Problem:
Client is unable to translate the links in the "Teaser Box" from the "Total Theme" using WPML. The links in the teaser boxes are not pointing to the translated FR pages but instead to the original EN language pages.
Solution:
First, we registered the
vcex_teaser
shortcode in WPML by adding custom XML configuration. Here is the XML code to add:
After adding this code, the URLs for the teaser box in the default language became available for translation in the Advanced Translation Editor (ATE) and String Translation (ST). To translate URLs in ATE, you can search for "https" and replace it with the translated version of the URL.
Additionally, to ensure the module is registered for translation, follow these steps:
1. Open the original page with the module on the front-end to trigger module registration.
2. Update the original page with a minor change and save it. This will update the translation and add the new module to the Translation Management.
After these steps, you should be able to search for URLs in ATE and translate them accordingly.
I am trying to: Translate links of "Teaser Box" from "Total Theme"
Link to a page where the issue can be seen: hidden link
The problem:
Teaser Box from Total Theme is supposed to be 100% compatible with WPML, but the links of the 4 boxes at the beginning of the page should link to the FR pages, but they keep linking to the original language which is EN.
I made a test page with only a teaser box, to see if the problem was coming from the page, but the result was the same: -> link was not translated
This is a common case among page builders, since they keep evolving and new stuff being added. This shortcode needed to be recognized by WPML (as mentioned above).
Since your "Translated document options" in WPML -> Settings are set to "Translate (this will include the slug in the translation and not create it automatically from the title)", you'll need to translate the slugs manually as mentioned above.
I see that it works on the staging and I followed your advises on the prod. website, but for a reason I ignore, the 4 http links don't appear in the ATE.
Here is what I did:
1- Copied you code in WPML settings -> Custom XML configuration
2- I scanned to adjust links in WPML setting
3- Cleared WPML cache
4- re-saved permalinks just in case
5- Purge SG Cache and Browser cache
But with all that, when I type "http" in the ATE, no url appear to be translated.
Before you can see your module in the Translation Editor you need to do the following:
1. Open the original page with the module on the front-end. This will trigger the module registration.
2. Update your original page. You can do a small change like adding a period and deleting it. Just be sure that once you click the Update button the translation has the round icon and not the pencil one. If you still see the pencil icon it means that the translation was not updated and the new module was not added to the Translation Management.
So at this point all you need to edit your page, having this module or widget, make some change in the content, save and update the translation. And in ATE search for the URLs.