Problem: You are experiencing missing translations on local pages after making changes in the default language, and you are also facing issues with opening WPML and the WPML Translation Editor. Solution: To determine if a page’s content was initially created using the Classic Translation Editor or the Advanced Translation Editor, first check if the content appears in the Advanced Translation Editor. If it does, the translations were done using the Advanced Translation Editor. If the frontend shows content but the Advanced Translation Editor is empty, check the Classic Translation Editor. If the content appears there, it means the page was translated using the Classic Translation Editor. If the frontend shows content but both the Advanced Translation Editor and the Classic Translation Editor are empty, then further troubleshooting is necessary as this situation is usually not possible.
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 issue persists, please open a new support ticket at WPML support forum for further assistance.
If you're experiencing a 504 Gateway Timeout error when trying to add a new item to a translated menu using WPML, it might be due to a temporary glitch, cache conflicts, a stuck translation process, or a problem with the menu structure.
Solution:
We recommend the following steps to troubleshoot and potentially resolve the issue:
1. Disable all other plugins except WPML to check if there is a compatibility issue with another plugin. 2. Enable the debug log to capture any errors or notices that occur during the process. You can learn how to do this by following our guide on debugging WPML. 3. Check if the issue occurs with every menu or only specific ones.
If these steps do not resolve the issue, it might have been a temporary glitch. Deactivating and reactivating plugins can act as a soft reset, which might help clear any blocks in the process.
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 WPML known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If needed, do not hesitate to open a new support ticket with us for further assistance.
Problem: The client added the Arabic language to their site using WPML and expected the content to display in RTL (right-to-left) format. However, the Arabic content was displaying in left-to-right format due to the use of a custom language code (ar-eg), which WPML did not recognize as RTL. Solution: We advised the client that the issue is controlled by the theme rather than WPML itself. For immediate testing, the client could switch to a theme that supports RTL or set Arabic as the WordPress language without WPML to confirm if the issue persists. To address the specific issue with the custom language code, we provided a code snippet to force RTL direction:
/**
* Force RTL direction for the custom Arabic‑Egypt (ar‑eg) language.
* Adjust the body/html tag direction when WPML's current language is ar-eg.
*/
add_filter( 'language_attributes', function ( $output ) {
// Get WPML's current language code
$current_lang = apply_filters( 'wpml_current_language', null );
// If we're on ar-eg and dir="rtl" is not already in the attributes, add it
if ( 'ar-eg' === $current_lang && false === stripos( $output, 'dir=' ) ) {
// Remove any existing dir attribute just in case, then append rtl
$output = preg_replace( '/\sdir=("|\")(rtl|ltr)\1/i', '', $output );
$output .= ' dir="rtl"';
}
return $output;
}, 20 );
We recommended that the client ensure they have a backup before implementing this snippet as it was not tested directly.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is unsure about the impact and differences between using the WordPress Editor and the WPML Translation Editor for translating pages, specifically regarding the accuracy or functionality of translated pages. Additionally, the client seeks guidance on translating schema markup content like FAQ schema. Solution: We recommend using the WordPress Editor for cases where script or code translation is involved, as the WPML Translation Editor cannot handle these elements. Using the WordPress Editor allows you to manually add and adjust translated content similarly to how you manage content in the default language. This method does not affect the accuracy or functionality of your page. However, if you switch back to the WPML Translation Editor in the future, any changes made manually will be overwritten. If you have not already created an Italian page, you can start with a blank page or use our duplication method, which copies content from the default language for manual adjustments. For more details, please visit: Using Different Translation Editors for Different Pages.
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 further assistance is needed, please open a new support ticket at WPML Support Forum.
Problem: The client is trying to add FAQ schema in JSON-LD format to their web pages using an HTML block and wants to translate the 'name' (Question) and 'text' (Answer) values using WPML's Advanced Translation Editor (ATE). However, the content injected via an HTML block doesn't appear as translatable fields in ATE by default. Solution: We explained that the Advanced Translation Editor is not designed for handling script tags, which are excluded and copied over to the translation unchanged. This can lead to issues when trying to translate content within script tags directly in ATE. As an alternative, we suggested switching to the Classic Translation Editor, which allows the translation of HTML, CSS, and JavaScript, if the client does not require features like automatic translation or glossary provided by ATE. For more detailed guidance, we recommended checking out the documentation on choosing your translation editor at https://wpml.org/documentation/translating-your-contents/using-the-translation-editor/#choosing-your-translation-editor and using different translation editors for different pages at https://wpml.org/documentation/translating-your-contents/using-different-translation-editors-for-different-pages/.
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. Should you need further assistance, please do not hesitate to open a new support ticket at https://wpml.org/forums/forum/english-support/.
