Problem: You are experiencing an issue when switching from English to French on your website, receiving an error message indicating that the translation loading for the health-check domain was triggered too early. This suggests that some code in a plugin or theme is running prematurely. Solution: We recommend ensuring that all your plugins, especially the one mentioned in the error message, are updated to their latest versions. You can check for updates in the 'Plugins → Add New Plugin → Commercial' tab by clicking the 'Check for updates' button. Additionally, updating the WPML plugin to the latest version, which is 4.7.1, might help as it includes the latest bug fixes and improvements. For detailed instructions on updating WPML, please visit http://wpml.org/faq/install-wpml/. For more information on this specific error, you can visit https://wpml.org/errata/php-error-wp-6-7-notice-function-_load_textdomain_just_in_time-was-called/.
If this solution does not resolve your issue or seems irrelevant due to being 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue where the 'Stores' section on their profile page does not load in the Serbian version and shows a spinning loader, while the English version loads correctly. The problem is associated with the Classified Listing Store plugin, and the slug is set to 'store'. Solution: We recommended applying a workaround from our errata page. You can find the detailed steps and explanation here: WPML String Translation error fix.
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client reported that the English version of their website was displaying mixed content in English and French, including forms and property details. This issue seemed related to the translation settings in the theme's backend, where languages were mixed without any recent changes made by the client.
Solution: We advised the client to ensure they are using the latest versions of the WPML plugins by checking for updates in the Plugins > Add New > Commercial section. We also suggested re-adding strings in the default language and re-translating them to check if the issue persists. Additionally, we recommended not translating labels from the theme options but using the WPML String Translation instead. If the problem continues, we suggested creating a staging site for further debugging to avoid issues on the live site.
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 for personalized assistance.
Problem: The client experienced a significant increase in the size of the icl_translation table after switching from Elementor to Gutenberg/GeneratePress, causing delays in staging software due to the large database size. The client also inquired about the creation and loading of .mo files for translations. Solution: We can offer installing a special plugin to manage and delete unnecessary jobs that may be enlarging the database. Our developers are aware of this issue and are working on a solution in a future version of WPML.
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 issues persist, please open a new support ticket.
Problem: You are unable to add a different URL in a Custom Post Type field for the English version of your website, as the URL field is blocked. Solution: We recommend checking the workaround provided on the Advanced Custom Fields - Inability to Translate External Links in Same Fields Across Languages page. This should help you unlock the URL field and allow you to add different URLs in your Custom Post Types.
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.
Problème: Après avoir traduit les templates "Header" et "Footer" via Translation Management, une erreur 500 apparaît lors de l'accès aux pages traduites. Le client a reçu un message d'erreur indiquant un "Crash du site web". Solution: 1. Nous avons recommandé d'activer le journal de débogage de WordPress pour identifier les erreurs potentielles. Pour cela, modifiez le fichier wp-config.php comme suit:
2. Après avoir activé le débogage, une erreur liée au plugin jet-compare-wishlist a été identifiée. Nous avons conseillé de désactiver ce plugin pour résoudre le problème. Si cette solution ne résout pas votre problème ou semble dépassée, nous vous recommandons de consulter les problèmes connus, de vérifier la version du correctif permanent et de confirmer que vous avez installé les dernières versions des thèmes et plugins. Si le problème persiste, n'hésitez pas à ouvrir un nouveau ticket de support.
Problem: You are using WPML and encountered an error: Uncaught Error: WPMLStringTranslationInfrastructureStringGettextRepositoryFrontendQueueJsonRepository::get(): Return value must be of type array, null returned. Solution: We are currently investigating a similar issue. In the meantime, we recommend following this workaround to help resolve the issue. Please ensure that you back up your database before making any changes. For detailed instructions, visit WPML Errata.
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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: You are experiencing a critical error when trying to access the WPML admin panel, resulting in a fatal error message instead of the expected admin panel. Solution: We are currently investigating a similar issue. In the meantime, we recommend following the workaround provided here: WPML String Translation error fix. Please ensure that you back up your database before making any changes.
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: You are experiencing issues with badly encoded characters when importing a glossary CSV file into WPML. Solution: 1. Initially, we identified an issue with special characters being badly encoded during the import process. We documented this problem in our errata, which you can check here. 2. We have resolved this issue, and the fix has been released to production. Please verify by importing your CSV file again to see if the problem with character encoding has been resolved.
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 here, 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.
Usamos cookies para otimizar nosso site e nossos serviços. Seu consentimento nos permite processar dados como o comportamento de navegação. O não consentimento pode afetar alguns recursos.
Funcional
Sempre ativo
Necessário para que nosso site funcione e se comunique corretamente.
Preferências
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Estatísticas
Nós os usamos para analisar as estatísticas do nosso site. As informações coletadas são totalmente anônimas. O armazenamento ou acesso técnico que é utilizado exclusivamente para fins estatísticos anônimos. Sem uma intimação, o cumprimento voluntário por parte do seu Provedor de Serviços de Internet, ou outros registros de terceiros, as informações armazenadas ou recuperadas para este propósito geralmente não podem ser usadas para identificá-lo.
Marketing
Esses cookies rastreiam sua navegação para fornecer anúncios relevantes para você.