Problem: Der Kunde versucht, den Home-Link im Logo zu übersetzen, sodass er auf die entsprechende Sprache umleitet. Das Logo wurde in Bricks Builder eingefügt und führt derzeit auf eine spezifische URL. Die Header-Datei enthält jedoch keine übersetzbaren Links. Solution: Beachtet dazu bitte, dass man dieses Problem auf einer neuen Test-Site nicht bestätigen konnte. Man konnte dort die Link URL des Images (Logo) wie erwartet im WPML Übersetzungseditor übersetzen. Anlternative: 1) Gehe zu Bricks > Templates. 2) Öffne das "Header" Template im WordPress Editor. 3) Stelle in der rechten Seitenleiste unter "Translations" die Übersetzungsmethode auf "WordPress Editor". 4) Übersetze den Header mit dem WordPress-Editor und setze die Logo-Links manuell in jeder Sprache. Für detaillierte Anweisungen zur Verwendung verschiedener Übersetzungsmethoden besuche bitte https://wpml.org/documentation/translating-your-contents/using-different-translation-editors-for-different-pages/.
Sollte das Problem weiterhin bestehen oder auf anderen Seiten oder Templates auftreten, empfehlen wir, einen neuen Support-Ticket zu öffnen. Wir empfehlen auch, die Seite mit bekannten Problemen (https://wpml.org/known-issues/) zu überprüfen, die Version der dauerhaften Lösung zu verifizieren und zu bestätigen, dass die neuesten Versionen von Themes und Plugins installiert sind.
Problem: The client is experiencing an issue where updating a block of text in the French version of their website causes the styling (fonts, alignment, spacing) to be lost on the frontend. Additionally, after editing, the page appears in the Translation Queue with the status 'In progress', and even when marked as complete, the styling does not always return correctly. Solution: We recommend resaving the translated page without making any changes to see if the issue resolves itself, as it did with the homepage in this case. It's possible that a specific module on the page is interfering with the proper saving of edits. If you're experiencing this issue on other pages, try the same approach of resaving without alterations. If the problem persists, it might be due to outdated themes or plugins, or a known issue.
Please check the related known issues and ensure you have the latest versions of your themes and plugins installed. If this solution does not apply or is outdated, we highly recommend opening a new support ticket for further assistance. You can do so at WPML support forum.
Problema: Você está enfrentando um erro de redirecionamento ao testar suas páginas no Google PageSpeed, onde 161 de 950 páginas estão sendo redirecionadas para a versão em inglês. Solução: Se você está enfrentando esse problema, recomendamos verificar se a opção de 'redirecionamento com base no idioma do navegador' está ativada no WPML. Esta configuração pode fazer com que o site redirecione automaticamente para a versão em inglês quando detecta que o idioma do navegador do visitante é inglês. Como o Google PageSpeed Insights utiliza servidores com navegador configurado em inglês, isso resulta no redirecionamento mencionado. Para resolver, você pode desativar essa opção de redirecionamento. Para mais detalhes, consulte a documentação do WPML sobre redirecionamento automático baseado no idioma do navegador.
Caso essa solução não se aplique ou já esteja desatualizada, recomendamos abrir um novo ticket de suporte. Também é aconselhável verificar os problemas conhecidos relacionados, verificar a versão da correção permanente e confirmar que você instalou as versões mais recentes de temas e plugins.
Problem: The client redesigned a page and attempted to translate it into Dutch, Spanish, and Catalan using WPML. However, the translation process was getting stuck in a loop or only partially translating the content. Additionally, the Dutch version displayed old content instead of the redesigned version.
Solution: We discovered that the issue might have been due to a mismatching record update possibly from a previous site migration. We corrected this, and the Dutch translation now reflects the redesigned content. You can add other translations by clicking the '+' sign next to a language and completing the translation. For issues related to formatting, such as colorful markers, please consult our guide on how to apply formatting markers.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, 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: After updating WPML from version 4.6.11 to 4.7.6, the list of translators is no longer visible in the WordPress admin panel under WPML -> Translation Management -> Translators. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Back up your database to ensure data safety. 2. Open your database and navigate to the
wp_options
table. 3. Locate and remove the
wpml-cache-translators-translate
option. 4. Return to your site and re-add the translators. WPML will automatically rebuild the cache.
Please note that this solution might be irrelevant if it's outdated or not applicable 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 the issue persists, please open a new support ticket at WPML support forum.
Problem: The client was experiencing issues with WPML on their website, where only the titles were being translated automatically. Additionally, there was a warning about a problem with the String Translation table, which could potentially become a critical issue. Solution: We recommended the client to provide debug information from their site by navigating to WPML → Support and copying the debug information. For the string translation table issue, we suggested following the steps provided in a specific support forum thread (https://wpml.org/forums/topic/there-is-a-problem-with-the-string-translation-table-in-your-site-23/). After further investigation and with the client's authorization, our second-tier specialists resolved the issue by adding a missing column in the database table using the following SQL commands:
ALTER TABLE `wpstg0_icl_strings` ADD `wrap_tag` varchar(16) COLLATE 'utf8mb4_unicode_520_ci' NOT NULL AFTER `location`;
ALTER TABLE `wp_icl_strings` ADD `wrap_tag` varchar(16) COLLATE 'utf8mb4_unicode_520_ci' NOT NULL AFTER `location`;
We also advised the client to make minor edits to the content in the original language and update the translations accordingly.
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 the problem persists, please do not hesitate to open a new support ticket at our support forum.
Problem: The client is experiencing an issue with WPML's Advanced Translation Editor not being activated due to an API authentication error related to an inactive access key. The client did not receive any email to confirm the access key and there have been no recent changes to the website. Solution: We recommend the following steps to resolve the issue: 1. Disable all other plugins to ensure they are not interfering with WPML's functionality. 2. Navigate to WPML → Translation Management to check for any prompts. 3. Unregister and re-register your site's key: - Go to Plugins → Add New, click the Commercial tab, and select Unregister WPML from this site. - After the page loads, click on Register WPML. Follow the prompts to get a new key for your site from your WPML account, setting it as a Production site. - Copy the new key and paste it in the Commercial tab. Delete the old site key in your WPML account. 4. If the error persists, please provide a screenshot of the WPML → Support → Advanced Translation Editor Error page. 5. If WPML was deactivated/reactivated, rest assured that translations and settings are preserved in the database, but ensure to back up your site beforehand. Additionally, if a translation job seems stuck, make a minor edit to the original page and save it to update the translation status, then reattempt the translation in the WPML Translation Editor.
If these steps do not resolve your issue, 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. Please feel free to open a new support ticket for further assistance at WPML support forum.
Problem: If you're experiencing issues where the translated content of your custom post types is displayed using the default single post template instead of your custom template, this might be due to the templates not being translated. Solution: We recommend translating your Site Templates and Template Parts to ensure they apply correctly in different languages. First, check if these templates are available for translation at WPML > Translation Management > Dashboard. If they are not translated, create a translation job for each template or template part. You can then access and complete these translations to 100% using the WPML Translation Editor or automatic translation at WPML > Translations. Additionally, be aware of potential display condition issues when editing templates in a second language within the Site Editor. A workaround for this issue can be found at https://wpml.org/errata/template-is-not-applied-to-translated-page/.
Please note that this solution might be irrelevant if it's outdated or not applicable 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 the issue persists, please open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue where the 'Other texts (Strings)' section in WPML > Translation Management does not load strings and continuously displays 'Loading items...'. This is due to PHP Warnings being returned instead of valid JSON from the endpoint. The warnings are caused by undefined array keys in the PHP code handling the data. Solution: We discovered that switching the theme resolved the issue, indicating that the problem was related to the custom theme used. Additionally, deleting the strings in WPML > String Translation that were waiting for a translator resolved the issue. We recommend checking if any custom theme or plugin might be overriding PHP error settings and causing warnings to display. If the problem persists, consider deleting strings waiting for translation in WPML > String Translation.
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.
