Problem: You are experiencing a 504 ERROR when trying to use the WPML menu sync feature, indicating that CloudFront could not establish a connection with the origin. Solution: We recommend checking your server's log files to determine why the timeout occurred. It's possible that a port is blocked, preventing traffic from passing through CloudFront.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please visit our known issues page and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket for further assistance. You can do so at our support forum.
Problem: You are experiencing an issue where the translated pages in Mongolian are not following the layout set in the default language on your site. This affects all Mongolian pages, with the layout and template settings not syncing correctly, resulting in a broken homepage in Mongolian compared to the default language version. Solution: We recommend deactivating the Elementor plugin and then reactivating it. This action has resolved similar issues in the past and might fix the layout synchronization problem for the Mongolian translations on your site.
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. Additionally, please feel free to open a new support ticket with us for further assistance at WPML support forum.
Problem: You have set up your site using TheGem Theme and configured category-based templates for single posts. Although you have set TheGem Templates to be non-translatable in WPML settings to use a single global template ID across all languages, this setup works only for the default English version. Translated posts in other languages do not adopt the correct layout despite having the correct global template ID assigned in the backend. Solution: To resolve this issue, it is necessary to create separate TheGem templates for each language, as WPML loads translations for posts, pages, or any other custom post types (CPT) in this manner. You should keep the translation of the Templates CPT active and translate it as described here: Translating Templates Documentation. Enforcing a single template ID across all language versions of posts in the same category is not supported by default and might require custom coding, which is beyond our standard support scope.
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: You are trying to match posts with multiple languages by uploading CSV files for each language. After importing the English posts as the default language and then importing other languages, the language connections are lost after running WPML > Import and Export > Run Imports. The first import after the default language import is successful, but subsequent imports cause the issue.
Solution: To ensure that the posts remain linked across different languages after import, follow these steps: 1. Import all your languages first before running the WPML Import tool. This prevents the tool from cleaning up 'import-related' data which includes unique IDs and translation groups. 2. If you need to import languages at different times, re-run your previous imports using WP All Import to update the posts and reassign the unique ID before importing a new language. 3. Alternatively, you can add the following code to your functions.php to prevent the removal of import-related metadata:
After all languages are imported, you can remove this filter.
If this solution does not resolve your issue or 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 the problem persists, please open a new support ticket.
Problem: When using the Broadcast plugin to copy menus from one site to another, the copied menu is not visible on the child site, likely because the menu and its items do not have an assigned language. Solution: Currently, there is no available hook in WPML to programmatically set the language for menus and menu items copied using the Broadcast plugin. We recommend contacting the developers of the Broadcast plugin to discuss making their plugin compatible with WPML. They can also join our Go Global program where we assist developers in making their plugins compatible with WPML.
If this solution does not apply to your case, or if it seems outdated, please open 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.
Problem: The client is a Game Platform Operator building a WordPress site and needs to manage content across three domains using WPML. They require content synchronization, multilingual support, and selective synchronization for localized content such as footers and Terms & Conditions pages.
Solution: We recommend the following steps: 1. Use WPML Automatic Translation to create and manage multilingual content and ensure timely updates across domains. WPML Automatic Translation Documentation. 2. Set up WordPress Multisite integrated with WPML to manage your domains from a single installation, with WPML handling the multilingual content. WPML Different Domains Per Language. 3. Utilize WPML Geo-targeting and Automatic Redirection for language-specific user navigation. WPML Geo-targeting, WPML Automatic Redirect. 4. Customize the WPML Languages Table for specific language URL configurations, adding custom languages, or adjusting language codes. Editing WPML's Languages Table. 5. Enable display of untranslated content on pages in secondary languages with WPML. Displaying Untranslated Content.
Please note that the solution might be irrelevant due to being outdated or not applicable to your specific case. If this is the case, 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 you still need assistance, please open a new support ticket. Contact WPML Support.
Problem: The client needs advice on setting up a multilingual website with different content for different IP countries, using subdomains and separate domains, and whether to use WordPress Multisite and the Broadcast plugin.
Solution: 1. Configure WPML for different domains or subdomains per language as per the WPML guide on using different domains per language. 2. Use WPML's Translation Management and Duplicate Post or Fallback feature to duplicate content across languages and make specific adjustments for each region. Refer to the documentation on displaying untranslated content. 3. For content that differs by region, such as License Logos, T&C, and Footers, use WPML's String Translation module or Custom Fields Translation options. 4. Integrate GeoTargetingWP to direct users to the correct regional or language version based on their IP address. 5. Ensure your server is configured to handle the domains and subdomains, and use WPML to assign languages to them. More information can be found in the WPML documentation. 6. WordPress Multisite is not necessary unless there are requirements beyond WPML’s capabilities. 7. The Broadcast plugin might not be required as WPML's content duplication functionality should suffice. 8. Use GeoTargetingWP to redirect users from non-specified regions to a restriction notice page.
If this solution does not apply to your situation, or if it seems outdated, we recommend opening a new support ticket. We also highly recommend checking related 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.
