Problem: You are trying to translate links for your custom post types (CPTs) and have set the slugs to be translatable in WPML settings. Despite translating the slugs, saving permalinks, and clearing all caches, the translated links are not appearing in the mega menu under various language paths such as /fr/, /es/, /de/, /nl/, and /it/. Only non-CPT blocks have translated links. Solution: We have identified that this is a broader issue with WPML concerning CPTs and not just specific to your site. Currently, the recommended workaround is to manually adjust the links in the translations. We understand this is not the ideal solution, but it is a temporary fix that can be implemented immediately. We are actively investigating this issue internally and will keep you updated on any developments.
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking the related 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.
Problem: The client was experiencing issues with WPML on their website using Bricks Builder. Specifically, translated ALT text attributes were not displaying correctly, showing the original Polish ALT text instead of the translated versions. Additionally, there were problems with the Bricks Builder translation workflow on the homepage, requiring multiple resends for translation before the layout displayed correctly.
Solution: For the translated ALT text issue, we recommended the following steps: 1. Check the WordPress memory limit in WPML → Support and increase it if necessary by adding
define('WP_MEMORY_LIMIT', '256M');
in the wp-config.php file. 2. Ensure that the WPML Media Translation add-on is active and that the ALT texts for images are translated in WPML → Media Translation. 3. Re-translate specific ALT text strings by deleting the existing translations in WPML → String Translation, re-registering the string by visiting the page, and then re-translating the string.
For the Bricks Builder translation workflow issue: 1. Confirm that both Bricks Builder and all WPML plugins are updated to the latest versions. 2. Use specific WPML Troubleshooting tools in WPML → Support → Troubleshooting to synchronize content and language information. 3. After troubleshooting, re-save and resend the homepage for translation in Bricks Builder to check if the layout displays correctly.
Workaround:
Open the ...\wp-content\themes\bricks\includes\elements\image.php file
If these steps do not resolve the issues or if the solution becomes outdated, we 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 problems persist, please open a new support ticket at WPML support forum.
Problem: After deleting and re-adding a user, the client found that translations were visible, but upon opening the first form to translate, it did not function correctly. Solution: We recommend following these steps to resolve the issue: 1. Open your database administration tool (such as PhpMyAdmin). 2. Execute the following SQL commands:
UPDATE `{wpdbPrefix}_icl_translation_status` SET `status` = 1 WHERE `status` = 2
UPDATE `{wpdbPrefix}_icl_translation_status` SET `status` = 10 WHERE `status` = 1;
UPDATE `{wpdbPrefix}_icl_translation_status` SET `status` = 10 WHERE `status` = 9;
Make sure to replace '{wpdbPrefix}' with your actual table prefix.
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 experiencing issues with the 'Validate on Save' feature when adding a secondary domain for a new language. Despite having an SSL certificate, the domain does not validate on save. Additionally, the domain sometimes times out on initial load but loads correctly after a few seconds. Solution: We recommend ensuring that the secondary domain is correctly set up as per our documentation on using WPML with different domains per language, which can be found here: https://wpml.org/documentation/getting-started-guide/language-setup/language-url-options/how-to-use-wpml-with-different-domains-per-language/. If everything is set up correctly, you should deactivate the 'Validate on Save' checkbox and add the domain normally. After this adjustment, verify if the domain functions correctly. If it does, the issue is resolved.
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 WPML support forum.
Problem: The client is experiencing issues with translating the menu navigation sidebar, Professional Service sidebar, Timing sidebar, and the appointment form at the bottom of each page, which appears in English on some pages and in Arabic on others. Solution: If you're facing similar issues with sidebar translations or inconsistent language displays in forms, we recommend the following steps: 1. Navigate to WPML > Settings and set the ElementsKit items post type to be translatable. 2. Go to WPML > Translation Dashboard and locate the widget to translate, as indicated in our provided screenshot.
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.
Problem: The client needs to configure different domains for each language version of their website, such as brokercheck.de for Germany and brokercheck.fr for France. Solution: We recommend setting up separate domains externally from WPML. You can find detailed instructions on how to do this by visiting how to use WPML with different domains per language. After configuring the domains with your domain provider, you should update the settings in WPML > Languages on your site. Please note that it is not possible to use different domains and language directories simultaneously. For more details, refer to the FAQ section in the provided documentation.
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking the related 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.
Problem: The client added thirty languages to their website and wanted to automatically translate the entire website into these languages. They were concerned about the low number of translation credits available in their account and inquired about the need to purchase more credits. Solution: We checked the client's account and found that they have 10,000 credits available but none assigned to their website. We advised the client to confirm their credit balance and assign credits to their website by visiting https://wpml.org/account/manage-credits/. To view how credits were spent, they should check the Translation Tools tab under WPML > Translation Dashboard. For an estimate of the credits needed to translate the website, the client should filter for untranslated items in the WPML > Translation Dashboard, select them to get a word count and credits needed estimate. A visual guide can be found here: https://www.loom.com/share/d800748fe6fd4dcc86e44809e08ccc71.
If this solution does not resolve your issue or seems outdated, we 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.
Problema: O cliente está tentando adicionar e traduzir novos blocos em uma página, mas as traduções não estão aparecendo. Solução: 1. Verifique se as traduções estão atualizadas. Para páginas específicas, vá à lista de páginas e clique nos ícones de tradução para atualizar. 2. Se estiver usando botões não padrão do Elementor, como os do plugin Essential Addons, substitua-os por botões padrão do Elementor, que são compatíveis com o WPML. 3. Após fazer alterações, limpe o cache do WP Super Cache antes de traduzir para garantir que as traduções sejam atualizadas corretamente. Siga estes passos: - Abra a página com o Elementor e substitua o "Botão Criativo" pelo "Botão" padrão do Elementor. - Salve as mudanças. - No painel, clique em "Excluir Cache". - Atualize as traduções. - Exclua o Cache novamente.
Se a solução fornecida não resolver o problema ou parecer desatualizada, recomendamos abrir um novo ticket de suporte. Também é aconselhável verificar os problemas conhecidos e confirmar que você instalou as versões mais recentes dos temas e plugins.
