Problem: The client is using JetEngine custom post queries on a multilingual site. The queries work for German, Spanish, and Russian, but not for French or Italian translations.
Solution: We recommend going to the Listing in either French or Italian and re-saving it. This action was confirmed by Crocoblock as a solution and worked for the client, resolving the issue for both languages. After re-saving the listings and Smart filters, all items displayed correctly across the site.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please check the related known issues 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 with us for further assistance at WPML support forum.
Problem: You are working on a site under development and encountering issues with WPML. Specifically, you face an error when trying to translate link targets ('Error! Reload the page and try again'), and custom post URLs are not being translated. Solution: For the issue with translating link targets, we recommend enabling WordPress Debug by following this guide. After enabling, use the Link Target feature again and check the WordPress Debug log for any errors. Share these errors with us for further assistance.
Regarding the custom post URLs not being translated, ensure that the CPT slug has been registered correctly. For guidance on adding multilingual support for CPT slugs, refer to this documentation. If the problem persists, please provide the link to the page/post where the slug is not showing correctly.
Additionally, a '504' server error was identified, which suggests issues with the server or the Content Delivery Network (CDN). Contact your server support for this matter. As a temporary measure, deactivating all plugins except for WPML might help, as it did complete the process successfully in our test.
If these steps do not resolve your issues 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 needed, do not hesitate to open a new support ticket for further assistance.
Problem: The client is unable to review translations on their site when Elementor Pro is activated, encountering a PHP fatal error due to a missing format specifier in a translated string. Solution: If you're experiencing this issue, we recommend making a full backup of your website first. Then, ensure that the dynamic part of the problematic string matches the original. For example, a correct translation in German should look like this:
Sie sind eingeloggt als %1$s (%2$sLogout%3$s)
You can locate and correct this translation in WPML > String Translation by searching for "You are logged".
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.
