Problem:
After translating the content, the Elementor page is now aligned to the right and lacks balance (as I mentioned earlier). Is there something I need to activate to resolve this issue? Solution:
The client reported how he solved the issue:
I’ve identified and resolved the alignment issue with the Arabic page. The problem was that the page designed with Elementor, when translated to Arabic, doesn’t automatically apply the same settings as the English page by default. I manually adjusted the settings for the Arabic page, and the issue was resolved. Here are the changes I made:
In the English page, the sidebar was set to "none," but the Arabic page had a sidebar enabled. When I removed the sidebar from the Arabic page, the alignment issue was fixed.
Additionally, the header in the Arabic page was not set correctly. I selected the custom header from the main page (English version), and that resolved the header issue as well.
Problem: You are trying to translate two search forms using WPML, but they remain stuck in the 'waiting for translator' status even after attempting to publish them without review. Additionally, the 'jobs' tab shows no pending tasks. Solution: First, ensure that these forms do not require translation. If they don't, you should exclude them from WPML's translation management. Here's how you can do it: 1. Create a backup of your website. 2. Navigate to WPML > Settings and set the Post Type for your forms to 'not translatable' under Post Types Translations. 3. If you need to translate placeholder text within the forms, use the WPML > String Translation module. You can find more details on string translation here: String Translation documentation.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also advise 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.
If you're unable to find and translate the Product Tabs title string [xts-woodmart-options]additional_tab_title using WPML, and it appears as 'Registered and locked' in the Admin Texts Translation page, this might be due to corrupt entries in your database.
Solution:
We recommend logging into your site’s database using tools like PHPMyAdmin after taking a full site backup. Run the following query to correct the issue:
1
UPDATE wp_icl_strings SET string_package_id = NULL WHERE string_package_id = 0 AND context LIKE 'admin_texts_xts-woodmart-options'
After applying this fix, verify that everything is working as expected. If similar issues occur with other string domains, you can use the following query as a workaround, but only after ensuring you have backed up your site:
1
UPDATE wp_icl_strings SET string_package_id = NULL WHERE string_package_id = 0
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 problems persist, please open a new support ticket.
Problem: You are managing translations for tags using the WPML 'taxonomy translation' tool and have encountered an issue where the Ukrainian translation of a tag separated from its Russian version. This separation resulted in a 301 redirect, and the Russian version created a duplicate Ukrainian translation with the same name. Solution: The issue arises from a mismatch in the database collation settings. Your database's wp_terms table uses the utf8mb3_general_ci collation, which does not fully support non-Latin characters like Cyrillic, while your WordPress configuration is set to use utf8mb4. To resolve this, we recommend updating the collation of your core database tables, particularly wp_terms, to utf8mb4. This update will support a broader range of characters and should prevent similar issues in the future.
If this solution does not apply to your case, or if it seems outdated, 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 for further assistance.
Problem: The client is unable to delete a database and is seeking clarification on whether a specific error is preventing the deletion. Solution: Firstly, it appears there was a misunderstanding regarding the deletion of a database as our previous supporter did not suggest this. If the client intends to delete a language rather than a database, we recommend following these steps: 1. Visit https://wpml.org/faq/how-to-completely-remove-a-language-from-your-site/ for guidance on removing a language. 2. If the above link does not resolve the issue, ensure to back up the website fully. Then, proceed with these steps: - Activate the language intended for deletion. - Manually delete all content associated with that language by navigating to the respective content tabs (pages, posts, templates), switching the language via the top-bar flag, and deleting all content. - Clear all deleted content from the trash. After completing these steps, the language can be removed from the site.
If this solution does not apply or is outdated, or if further issues arise, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that the latest versions of themes and plugins are installed. Should the problem persist, please do not hesitate to open a new support ticket at WPML support forum.
Problem: O cliente está tentando ativar o WPML - The WordPress Multilingual Plugin e encontra um erro ao inserir a chave fornecida, com a mensagem: 'Unable to register: Site key not matching'. Solution: Se você está enfrentando esse problema, recomendamos que registre o site novamente seguindo estes passos: 1. Acesse https://wpml.org/account/sites e remova o site da lista; 2. Adicione o site novamente e copie a nova chave que for gerada; 3. No painel administrativo do seu site, vá em Plugins > Adicionar Novo > Aba Comercial e clique em "Remover registro do WPML neste site"; 4. Registre o site novamente, utilizando a chave copiada no passo 2.
Essa solução pode ser irrelevante se estiver desatualizada ou não se aplicar ao seu caso. Recomendamos verificar os problemas conhecidos, confirmar a versão da correção permanente e certificar-se de que você instalou as versões mais recentes dos temas e plugins. Se o problema persistir, por favor, abra um novo ticket de suporte em fórum de suporte WPML.
Problem: If you're experiencing issues where pages are redirected to article categories when WPML is enabled, it might be due to a slug conflict between a page and a post category in different languages. Solution: We recommend checking if the slug of the post category in another language is the same as the slug of your page. If they are the same, change the slug of the post category. For example, if both the page and the category are named 'canyoning' in different languages, you could rename the category to 'canyoning-it' for Italian. This change should resolve the redirection issue.
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 problem persists, please open a new support ticket at WPML support forum.
Problem: Le client a rencontré une erreur de base de données WordPress lors de l'utilisation du plugin WPML avec plusieurs autres plugins et le thème JupiterX Child. L'erreur indiquait l'impossibilité d'effectuer la requête car elle contenait des données invalides, empêchant l'édition des conditions d'affichage des modèles de page d'Elementor. Solution: Nous avons identifié que le problème pourrait être lié à l'utilisation d'Emojis ou d'autres symboles incompatibles. Pour résoudre cela, nous recommandons de vérifier la base de données pour identifier et supprimer la chaîne invalide. Voici un exemple de données à rechercher :
De plus, il est important de s'assurer que WPML est correctement enregistré. Si ce n'est pas le cas, suivez ces étapes pour le réenregistrer : 1. Visitez la page de votre compte sur https://wpml.org/account/sites/ 2. Supprimez la clé du site. 3. Allez dans plugins -> Ajouter un nouveau -> Onglet commercial. 4. Cliquez sur « Désenregistrer WPML de ce site ». 5. Cliquez sur « Enregistrer WPML ». 6. Cliquez sur « Get a key for this site ». 7. Enregistrez le site et entrez la nouvelle clé.
Si cette solution ne résout pas votre problème ou semble obsolète, 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.
