Giải pháp có sẵn

Problem:
The client was experiencing an issue where the translation of a page containing a shortcode was getting stuck. The specific page in question was 'My Wishlist' which was not translating and was showing a 504 error after some time.
Solution:
We recommended the following steps to resolve the issue:
1. Edit the 'My Wishlist' page and make a small change in the content, then save the changes.
2. Navigate to WPML -> Translation Management.
3. Select the 'My Wishlist' page and assign it to your user for translation.
4. Check if you can now translate the page or cancel the translation job.
Additionally, for translating specific strings, go to WPML -> String Translation or WPML -> Translation Management -> Strings section at the bottom.

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.

Problem:
You are experiencing an issue where WPML is missing some records in the languages tables, which prevents it from fully working. Despite following the suggested troubleshooting steps like clearing language information and repopulating languages, removing ghost entries, fixing terms and taxonomy relationships, setting language information, assigning translation status to duplicated content, and fixing post type assignment for translations, the problem persists.

Solution:
If you're facing this issue, we recommend you try the following steps after taking a database backup:
1- Open your database manager, for example, PhpMyAdmin.
2- Navigate to the "wp_options" table (note: 'wp_' is a standard prefix, yours might be different but the table name will be similar to xx_options).
3- Execute the following SQL query to search for the 'icl_admin_messages' key:

SELECT *
FROM `wp_options`
WHERE `option_name` LIKE '%icl_admin_messages%'
LIMIT 50;

4- Delete this key from your database.
5- Clear your cache, refresh your dashboard, and check if the message has disappeared.

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 issue persists, please open a new support ticket at WPML support forum for further assistance.

Problem:
The client was experiencing an issue where the translation editor was only displaying the headline of a page, and other textboxes were not visible when using BeTheme/BeBuilder with WPML.
Solution:
We identified that this issue is a known problem with BeTheme and BeBuilder, as detailed in our errata page (https://wpml.org/errata/betheme-bebuilder-content-not-available-in-translation-editor/). We recommended the client to try the workaround suggested on that page. Additionally, for fields appearing in the translation editor that should not be translated, such as shortcodes or CSS, we provided three options:
1. Contact BeBuilder to modify the code to prevent these elements from registering in the Translation Editor.
2. Follow the guide to register the element for translation correctly (https://wpml.org/documentation/support/language-configuration-files/register-page-builder-content-for-translation/).
3. Use the Automatic Translation's Glossary feature to prevent certain terms from being translated (https://wpml.org/documentation/translating-your-contents/advanced-translation-editor/how-to-create-and-manage-glossary-entries/).

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 (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 in our forum (https://wpml.org/forums/forum/english-support/).

Problem:
After migrating from Polylang to WPML, menus disappeared in the backend. The client was concerned about resetting WPML due to the large number of pages migrated.
Solution:
We recommended the following steps:
1. Ensure a full site backup or at least a database backup.
2. Navigate to WPML -> Support -> Troubleshooting link. Follow the steps outlined in the WPML Troubleshooting guide.
3. If menus still do not appear, create a new test menu and translate it following the instructions in this guide on translating menus. If the new menu works but old ones do not, it indicates a database issue with the old menus, which should be recreated.

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

Problem:
The client is experiencing an issue where a specific paragraph ('Dimensions - height x width x depth (cm): 80 x 65 x 75') is missing in the German and Czech translations of a page, resulting in English text appearing in these translations. The paragraph is present in the Hungarian translation.
Solution:
We recommend installing the Yoast Duplicate Post plugin and cloning the problematic page. Then, follow these steps:
1. Go to your Dashboard > Pages.
2. Open the edit screen of the original page and look for a pencil/circle/gear icon under the "Languages" section in the sidebar.
3. Make a minor change, such as adding an extra blank space at the end of a sentence or paragraph.
4. Save the changes. A circular arrow should appear beside the links for the second languages, indicating that an update is required.
5. Edit the translation again and ensure it is saved up to 100% translated.
If this does not resolve the issue, please provide us with the login information for the copied website so we can further investigate.

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 the problem persists, do not hesitate to open a new support ticket at WPML support forum.