Bug

Problem:

The client was experiencing an issue where the accordion widget displayed incorrect characters on the translated page on their website. Initially, the problem was resolved in two languages after updating the translation, but it persisted in the Catalan language.

Solution:

We recommended the following steps to address the issue:
1) Navigate to WPML>>Settings>>Custom Fields Translation.
2) Click on the Show systems fields link.
3) Search for the

*_eael_widget_elements*

field.
4) Set it as Copy and save the changes.
5) Open the page for editing in the original language and make a minor change to refresh the translation settings and update it.
6) Update the translation.

Additionally, to address the issue with the Catalan translation specifically:
1) Visit Essentials Addons>>Tools and click on the Regenerate Assets button.
2) Update the page and then update the translation.

If these steps do not resolve your issue, or if the solution seems outdated or irrelevant to your case, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket at WPML support forum for further assistance.

Problem:
You are using the advanced translation editor in WPML and cannot save a translation due to an error stating that 'the original sentence includes formatting markers. However, not all markers are applied to the translation.' You need to know how to add formatting markers correctly to resolve this issue.
Solution:
We have identified that the issue arises because there must be an equal number of newline markers in both the original and translated content. For instance, if there are 7

wpml_linebreak

instances in the original text, you should ensure there are also 7 line breaks in the translation. It's important to note that one of these line breaks might be inside an HTML tag, so you should add one there as well. If you encounter difficulties in applying this solution, please provide us with the exact name of the page or post, and we can assist further.

Please be aware that this solution might be outdated or not applicable to your specific case. We highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the issue persists, please open a new support ticket at WPML support forum for further assistance.

Problem:
You are using the Better Search Replace plugin, which is compatible with WPML, to replace words across different language pages on your site. However, after using the plugin, the changes are visible on the English and Belgian pages, but the Classic Editor still shows the old content.
Solution:
The issue arises because the plugin modifies the database directly, which does not trigger the necessary WordPress hooks to update the Advanced Translation Editor (ATE). Unfortunately, WPML does not have a built-in tool to address this directly. However, we recommend updating your posts programmatically as a workaround. This method has not been fully tested by us and is not officially supported by WPML, so please ensure you have a full website backup before proceeding. For guidance on how to update posts programmatically, you can refer to this document: https://wordpress.stackexchange.com/questions/330746/how-can-i-mass-update-save-all-wordpress-posts-and-pages.

Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If this does not resolve your issue, please open a new support ticket at our support forum.

Problem:
Der Klient hat den Text 'Concentrate on the essentials' durch 'Focus on what truly matters' ersetzt und gespeichert, aber die Übersetzung wird nicht übernommen, trotz mehrfacher Anpassungen und Speicherungen.
Solution:
Wir empfehlen, sicherzustellen, dass alle ursprünglichen Tags in der Übersetzung vorhanden sind und in derselben Hierarchie bleiben. Dies kann im alten Übersetzungseditor durchgeführt werden. Es ist wichtig, dass das Tag, das entfernt wurde, an einer anderen Stelle hinzugefügt wird, um die Struktur beizubehalten. Außerdem könnte eine Überprüfung bewährter Praktiken bei der Vereinfachung Ihrer Übersetzungsprozesse helfen.

Falls diese Lösung für Sie nicht relevant ist, weil sie veraltet ist oder nicht auf Ihren Fall zutrifft, empfehlen wir Ihnen, ein neues Support-Ticket zu eröffnen. Wir empfehlen auch, die Seite mit bekannten Problemen zu überprüfen, die Version der dauerhaften Lösung zu verifizieren und zu bestätigen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben. Für weitere Unterstützung besuchen Sie bitte unser Support-Forum.

Problem:
Der Kunde berichtet, dass die Option 'Vorhandene Übersetzungen unverändert lassen' ausgegraut ist, wenn Änderungen an einer bereits übersetzten deutschen Seite vorgenommen werden und er die englische Seite anpassen möchte.
Solution:
Wenn Sie Änderungen an einer bereits übersetzten Original-Seite vornehmen, können Sie die Übersetzungen entweder durch Klicken auf das Symbol 'Pfeile im Kreis' aktualisieren oder die Seite über WPML > Translation Management erneut zur Übersetzung senden. Die Option 'Vorhandene Übersetzung unverändert lassen' ist nur verfügbar, wenn eine Übersetzung zu 100% abgeschlossen ist. Wenn die Seite nur teilweise übersetzt ist, übersetzt WPML nur die bearbeiteten oder neuen Inhalte innerhalb der Seite. Inhalte, die bereits übersetzt wurden, werden nicht doppelt berechnet.

Falls diese Lösung für Ihr Problem irrelevant erscheint, weil sie veraltet ist oder nicht auf Ihren Fall zutrifft, empfehlen wir Ihnen, ein neues Support-Ticket zu öffnen. Wir empfehlen Ihnen auch, die bekannten Probleme zu überprüfen, die Version der dauerhaften Lösung zu verifizieren und zu bestätigen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben.

Problem:
You are trying to translate your BetterDocs documentation from Danish to English, but you're facing an issue where headers such as H2, H3, and below are not visible on most translation pages, although they appear on some.
Solution:
We recommend two approaches to resolve this issue:
1) Modify the string format by removing the dot after the numeral in your headers. For example, change from (2.1. Økonomi) to (2.1 Økonomi). This adjustment should make the headers visible in the translation editor.
2) Utilize the search field in the translation editor to locate and translate these headers.

If this solution does not apply to your case, or if it seems outdated, we encourage you to open a new support ticket. We also highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum at WPML Support Forum.

Problem:
The

WPMLSuperGlobalsServer::getServerName

function relies on the

$_SERVER

superglobal for HTTP host information, which is not available in the CLI environment. Consequently, the

WPML_URL_Converter_Domain_Strategy::convertRestUrlToCurrentDomain

function fails to retrieve the correct host name, rendering REST URLs generated in the CLI environment invalid.
Solution:
We tested the scenario using WPML version 4.5.15 with no other plugins active. We used the following code to simulate the environment and did not encounter the issue:

if (defined('WP_CLI') && WP_CLI) {<br />    class ExampleCommand extends \WP_CLI_Command {<br />        /**<br />         * @subcommand wpml-rest-api<br />         */<br />        public function wpmlRestApi() {<br />            echo get_rest_url(path: 'wp/v2') . "\n";<br />        }<br />    }<br /><br />    WP_CLI::add_command('example', ExampleCommand::class);<br />}

We recommend you provide more details or a screen recording of the issue to help us better understand and address the problem.

If this solution does not apply to your case, or if it seems outdated, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If the issue persists, we highly recommend opening a new support ticket at WPML support forum.

Problem:
After updating Elementor Pro, both website languages were down. Disabling the WPML Multilingual CMS plugin allowed the base language (NL) to work, but the alternate language (EN) remained non-functional. Even after updating WPML to version 4.6.15, the plugin could not be activated due to a PHP Fatal error related to Elementor and WPML.
Solution:
To resolve this issue, follow these steps:
1. Ensure you have a full backup of your website.
2. Go to Plugins and deactivate all plugins.
3. Navigate to Plugins > Add New > Commercial, install and activate the WPML String Translation. If installation fails, download it manually from https://wpml.org and install it.
4. Reactivate the WPML Multilingual CMS plugin.
5. Reactivate all other previously active plugins.

This should resolve the issue as the missing WPML String Translation plugin was likely causing the problem.

If this solution does not apply to your case, or if it seems outdated, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If issues persist, please open a new support ticket at WPML support forum for further assistance.