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:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
/**
* 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.
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/.
Problem: You are trying to display all posts in all languages on a US page using WPML, but the default WPML settings do not support this functionality. Solution: We recommend adjusting your query to bypass WPML's default language filtering. Here's how you can modify your WP_Query:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
// Perform your WP_Query with suppress_filters set to true
$query= newWP_Query( array(
'post_type'=> 'post', // Or your custom post type
'posts_per_page'=> -1, // Show all posts
'suppress_filters'=> true, // Disable WPML language filtering
) );
// Apply the 'the_posts' filter manually to get posts in all languages
// Now $all_posts will contain all posts from all languages
$query->posts = $all_posts;
}
// Loop through and display the posts
if( $query->have_posts() ) {
while( $query->have_posts() ) {
$query->the_post();
// Your loop code (e.g., the_title(), the_content(), etc.)
}
}
// Don't forget to reset post data after the loop
wp_reset_postdata();
Please note that this solution is a custom workaround and was not extensively tested. If this solution does not work or seems outdated, or if it does not apply 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client needed guidance on managing the WPML license for a new testing environment that will eventually become the production site. Solution: We recommend registering the new instance with a new key as a development site. Once development is complete and you are ready to transition this to a production environment, you can update the site key to a production site key from the WPML accounts section. For more details, please visit How to remove the 'This site is registered on WPML.org as a development site' notice.
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.
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.
