Not WPML issue

Problem:

After migrating from a staging site to a test site, most of the text displays incorrectly, showing special characters and question marks. Additionally, the media section shows blank images, though the images exist.

Solution:

If you're experiencing issues with special characters and question marks after migration, it's likely due to the database collation setting. We recommend changing your database collation to either utf8mb4_unicode_ci or utf8mb4_unicode_520_ci to support non-Latin characters properly. Before making changes, ensure you back up your site fully. You can run the following SQL query for each table:

ALTER TABLE your_table_name CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci;

For example:

ALTER TABLE wp_posts CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci;

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.

Problema:
Il cliente ha un multisite con WPML attivo solo in due siti. Vuole cambiare la chiave di licenza solo per uno di questi siti, ma non trova l'opzione per farlo dalla pagina 'Add new plugin'.
Soluzione:
Se stai riscontrando lo stesso problema, ti informiamo che la chiave di licenza in un ambiente multisite è gestita a livello di network e non è possibile associare un singolo sottosito a un account WPML diverso. Pertanto, non è possibile cambiare la chiave di licenza solo per uno dei siti in un network multisite.

Se questa soluzione non risolve il tuo problema o se ritieni che le informazioni siano obsolete, ti invitiamo a verificare i problemi noti e a confermare che hai installato le versioni più recenti dei temi e dei plugin. Se necessario, apri un nuovo ticket di supporto sul forum di supporto WPML.

Problem:
If you're experiencing issues with duplicated content in Elementor after using the 'duplicate content' mode in WPML and wish to switch to using the Advanced Translation Editor (ATE) for translations, follow these steps.
Solution:
1. Optionally, navigate to your content list (e.g., Pages), filter by the secondary language, send the duplicated content to the Trash, and permanently delete it.
2. Go to WPML -> Settings -> 'How to translate the content' section -> Select 'Advanced Translation Editor' -> Save the changes.
3. Edit the content you want to translate, ensure the 'Translation Editor' option is selected in the Languages block on the right column, and click the plus (+) icon to add the translation.
4. Alternatively, you can use WPML -> Translation Management to search for content to translate, select it, and send it for translation using the options at the bottom of the table.

If this solution does not apply to your case, or if it seems outdated, 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 open a new support ticket.

Problem:
The client encountered a PHP deprecation warning in the WPML Multilingual CMS plugin, specifically with the

strtotime()

function, indicating 'Passing null to parameter #1 ($datetime) of type string is deprecated'. This occurred while using WordPress Version 6.7, PHP Version 8.2, Plugin Version 4.6.14, and WooCommerce Version 9.4.2.
Solution:
We explained that the deprecation notice is not a fatal error and will not affect the PHP's ability to complete tasks on the site. This type of warning typically indicates that the way a function is used will be removed in future PHP versions. We assured the client that in future versions of WPML, this warning will be resolved.

If this solution does not apply to your case, or if it seems outdated, we recommend opening 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 client was experiencing 404 errors on their multilingual website when accessing translated pages and taxonomies for the first time. The issue persisted even after disabling various caching solutions and plugins. The WPML String Translation plugin was identified as part of the problem, particularly when switching between languages on posts.
Solution:
We recommended the following steps to address the issue:
1. Navigate to WPML > String Translation.
2. Search for

wc/file/transient

and

wc-api

under the WP Endpoints domain.
3. If these strings are translated (indicated by a pencil icon below the language flag), select both and delete them from String Translation.
4. Go to "Settings > Permalinks" and resave the permalink structure.
5. Clear the caches from the site and browser, then check the page again.
Additionally, we suggested checking the guide on handling .htaccess issues with WPML at https://wpml.org/faq/why-is-htaccess-getting-overwritten-with-the-language-folder-on-my-wpml-website/.

If this solution does not resolve the 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 problems persist, please open a new support ticket at https://wpml.org/forums/forum/english-support/.

Problem:
The client was experiencing a blank white page when trying to use the Advanced Translation Editor (ATE) on their website. Additionally, after attempting a solution, they encountered a 'Critical Error' message.
Solution:
1. We suggested making a minor edit to the primary language page to refresh the ATE and then retranslate the page.
2. When a 'Critical Error' occurred, we advised the client to perform a full backup of their website/server.
3. We identified that the server lacked the 'Multibyte String Extension', which was necessary for the ATE to function properly. We recommended checking if this extension was available and activating it on their hosting.

If this solution does not resolve your issue, or if it 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 problems persist, please open a new support ticket.