Problem: The client is trying to translate HTML code inside the Divi Code Module using the WPML Advanced Translation Editor (ATE), but the HTML code block does not appear in the ATE. The client wishes to translate either the entire HTML block or just the attribute values within the HTML tags.
Solution: 1. We recommend adding a
1
<p>
tag to the HTML code within the Divi Code Module. This should make the content appear correctly in the ATE for translation. 2. If you need to translate specific attribute values, you can use the WPML String Translation. This allows you to translate individual strings that might not be available in the ATE.
Please note that the solution provided might be irrelevant due to being outdated or not applicable to your case. If the issue persists, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. Should you need further assistance, please do not hesitate to open a new support ticket in the WPML support forum.
Problem: The client was experiencing an issue where the Europe (EU) homepage could not be found after deleting and re-translating the EU version of the homepage. An error message indicated that the homepage did not exist or its translation was not published in the EU language.
Solution: First, we recommended that the client ensure the site's default language is set to English and then set the homepage in the English language. The client should also edit the homepage in English and double-check if the EU translation is published.
If the issue persisted, we suggested that it might be related to caching or a temporary problem. We recommended the following steps: 1. Deactivate all non-WPML plugins. 2. Switch to the main theme, such as Divi. 3. Re-select the homepage in the Reading settings page for the EU language.
After following these steps, the homepage should work properly. If the problem continues, we advise the client to check for related known issues, verify the version of the permanent fix, and confirm that the latest versions of themes and plugins are installed.
If the solution provided here is outdated or not applicable to your case, please open a new support ticket with us.
Problem: The client is experiencing an issue where the Advanced Translation Editor (ATE) displays links with the staging environment path ("/wpml/") after promoting the staging environment to production. Solution: We recommend making a minor change to the default language page and then resending the page for translation through WPML > Translation Management. This should update the content and display the correct URLs in the ATE, matching those on the frontend.
If this solution does not seem relevant to your situation, please open a new support ticket with us.
Problem: The client is unable to translate the Module Link URL of a Divi Blurb using the Advanced Translation Editor (ATE). The issue arises when using Divi's Dynamic URL feature, as the URL does not appear in the ATE. The client has tried adding custom XML configuration for the Divi Blurb shortcode and has made changes to the blurb to trigger WPML's translation detection, but without success.
Solution: We have identified that dynamic URLs are encrypted and therefore not recognized by ATE as translatable URLs. To work around this issue, the client should use either absolute or relative URLs for the Module Link URL field. Here are the steps to configure the translation:
For absolute paths, add the
1
<et_pb_blurb>
shortcode tag with the
1
link_option_url
attribute AND
1
link
type.
For relative paths, add the
1
<et_pb_blurb>
shortcode tag with the
1
link_option_url
attribute and WITHOUT the
1
link
type.
This approach allows the URLs to be recognized and translated within the ATE. If you are experiencing this issue and the solution provided does not seem relevant, please open a new support ticket with us.
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.
