Problem: The client is experiencing issues with the slugs of custom post types not being applied correctly when displaying an archive page in another language. Despite setting the slugs correctly and translating them, the links in the language switcher do not reflect the translated slugs, leading to 404 errors or incorrect pages being displayed. Solution: 1. Verify that the slugs for the translated custom post types (CPTs) are set correctly in WPML. This can be checked under the WPML Translation Editor where the slugs should be translated for all jobs. 2. Check if there is a conflict between the page slugs and CPT slugs. This issue might arise if the same slug is used for different types of content, such as a page and a CPT. This can be identified by using tools like the 'Debug Bar' plugin to analyze the request and query strings. 3. If the problem persists even after ensuring no slug conflicts and correct settings in WPML, it might be due to a theme or plugin conflict. Specifically, the Porto Theme and its related functionality plugin could be causing the issue as they handle the post types. In this case, reaching out to the Porto Support Team for further assistance is recommended.
Please note that the solution provided 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 with us for further assistance.
Problem: You are trying to translate posts using the 'Classical Translation Editor' (CTE) that were created with the Classical Editor and do not use Elementor functions. However, you can no longer access the Wysiwig translation editor, only the 'code' view. WPML displays a message advising to switch to the Advanced Translation Editor (ATE) to translate content without risking breaking your HTML code. Solution: The WPML support team has investigated and found that ATE has specific handling for HTML content, whereas CTE does not, and there are no plans to add new features to CTE at this time. WordPress itself does not allow adding script tags through the Visual tab in the Classic Editor; they must be added in the Text tab to function correctly. Therefore, for translating content that includes HTML, it is recommended to switch to ATE, which is better equipped for handling such scenarios. If you need to manage different editors for different pages, you can follow this guide on Using Different Translation Editors for Different Pages. Alternatively, replacing HTML with shortcodes is another viable option.
Please note that this solution might be irrelevant if it's 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.
Problem:
Vous utilisez ACF via des plugins avec des champs déclarés dans des fichiers PHP, et les traductions sont gérées via un textdomain. Depuis la dernière mise à jour d'ACFML, les traductions ne se chargent pas correctement dans la zone d'administration de vos sites multilingues, alors qu'elles fonctionnent sur un site monolingue.
Solution: Le client a résolu le problème de la manière suivante:
Le problème de chargement du textdomain était lié au hook utilisé, init au lieu de plugin_loaded. Les deux exemples sont donnés dans le codex.
En utilisant init, manifestement, le domaine se chargeait avant de pouvoir être pris totalement en compte par ACFML
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 you still need assistance, please open a new support ticket at https://wpml.org/forums/forum/french-support/.
Problem: The client reported two issues on their multilingual website. First, the Recent Comments widget was displaying English comments on a French page, when it should only show French comments. Second, there was a link to an English version of the page that was still in draft and therefore led to a 404 error.
Solution: We recommended the following steps to address the issues: 1. Navigate to WPML > Languages. 2. Enable the "Auto user Sign in and out for all domains" option under "A different domain per language" and save the change. 3. Resave the permalink structure by going to Settings > Permalinks. 4. Log out from the site. 5. From the login page, switch to the secondary language and log back into the site. 6. From the Widget section, remove the Recent Comment widget and add it again. 7. Save the changes.
These steps resolved both issues for the client.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the problem persists, 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 you still need assistance, please open a new support ticket at our support forum.
