Problem: If you're experiencing issues where changes made to a translated page in German (DE) are not being saved and instead revert to English (EN), and this behavior persists even after editing, it might be due to the settings or a specific bug in the WPML plugin. Solution: We recommend backing up your production site and updating the WPML plugin to the latest version, which as of now is 4.7.6. You can download the update from https://wpml.org/account/downloads/. This update addresses an edge case where the original post designed using a page builder would override a translation edited natively, as noted in the changelog here. If updating does not resolve the issue, please contact us for further assistance. We may need to escalate this to our 2nd Tier Support team for direct investigation.
Please note that this solution might be irrelevant if it's outdated or not applicable 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, do not hesitate to open a new support ticket here.
Problem: The client is working on a site under development and is trying to use translation hints in their code. However, they do not see the hint in the translation dialog when using the following PHP code:
printf(esc_html(// translators: %s is a year __( 'Active since %s', 'cnmd' ),), esc_html( $year ));
Solution: The solution in this case would be using the _x() Function which will allow you to add a context to a sting. WPML String Translation does have a column to display this context.
Source: https://developer.wordpress.org/reference/functions/_x/
We further explained that the comment
/* translators: %s: %s is a year */
is intended to provide context to translators who are translating the theme or plugin into different languages. It helps in understanding what the string represents, especially when creating .po language files that accompany the theme or plugin. However, PHP comments, whether single-line (//) or multi-line (/* */), are ignored by the PHP interpreter during script execution. They are meant only for documentation and do not appear on the website or affect the program's execution. For more details on PHP comments, you can visit https://www.w3schools.com/php/php_comments.asp.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable 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. Should you need further assistance, please open a new support ticket with us.
Problem: The client reported that strings on their WPML-powered site, which have been translated correctly, occasionally and randomly revert to the untranslated version. This issue occurs without any specific action taken within WPML. Adjusting the memory usage did not resolve the issue. Solution: Take note, that if the language files of a plugin or theme are added to WordPress or those files are being altered while working on the site, you will need to run a dialog which will appear on top of the page WPML > Theme & Plugin Localization. This dialog indicates that WPML found a new theme or plugins and needs to generate the custom language needed by WPML to translate the site. Those files will be saved at /wp-content/languages/wpml.< br/>< br/> We also identified some issues with GetText Calls inside the theme, like for example that the 'Learn More' link on the homepage was not using the correct GetText call. We recommended using esc_html__ for cases, in which the string is part of an HTML element which is detailed here: https://developer.wordpress.org/reference/functions/esc_html__ Additionally, we noticed multiple text domains being used within the theme, which could also lead to translation inconsistencies. We advised standardizing the text domain to 'rainforest-alliance' across all theme strings, as it is the one declared in styles.css. The text domain should always match the name of the theme or plugin's folder. More information on text domains can be found here: https://wpml.org/faq/what-are-text-domains/
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable 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 further assistance is needed, please open a new support ticket at WPML support forum.
