Problem: After installing WPML and adding two additional languages, the client's website became unsearchable on Google, except when selecting 'show English results'. The client was concerned about the site not appearing in Google search results and inquired about the necessary configurations in WPML to ensure proper indexing. Solution: We recommended the client to install a dedicated SEO plugin, such as Yoast SEO or Rankmath SEO, to manage multilingual SEO effectively. This setup allows the translation of meta information for each page, post, or archive, which is crucial for SEO in multiple languages. We provided documentation on how to integrate WPML with these SEO plugins for optimal results. You can read more about this integration here: WPML SEO documentation.
Please note that the solution provided 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.
Problem: The client was experiencing an 'Invalid post type' error when WPML was active, which disappeared upon deactivating WPML. The issue was suspected to be related to a conflict with another plugin. Solution: We recommended the client to test their site in a minimum environment by deactivating all plugins except for WPML and its add-ons. This would help identify if the issue was indeed due to a plugin conflict. The client was advised to reactivate the plugins one by one to pinpoint which one caused the issue. It was important to make a full site backup before proceeding with these steps. If the site was live, we suggested performing these procedures in a staging environment or a snapshot on a local or another server.
If you're experiencing similar issues, we recommend trying these steps to see if it resolves the problem. However, 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.
Problem: The client needed a solution where they could upload a category image using a Metabox custom field on the default language, and have that image automatically duplicated across other languages without the need to upload the same image for each language. Solution: 1. We advised the client to ensure that at least one image is added to a category in the default language to see the field in the settings page. 2. Once an image is added to a category, the field should appear correctly in the settings. 3. We asked the client to look for a specific message indicating that the settings have been updated, as shown in the screenshot we provided. 4. After seeing the message, the client should update the settings one more time to ensure the changes take effect.
Please note that this solution might not be relevant to your situation due to it being outdated or not applicable to your case. If this is the case, 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 you still need assistance, please do not hesitate to open a new support ticket in the WPML support forum.
Problem: The client experienced an issue where after recreating a custom taxonomy term, posts got multiplied within it. Additionally, the client wanted a solution to allow uploading a category image (created by a Metabox custom field) only in the default language, and have that image automatically duplicated across other languages. Solution: To address the issue of multiplied posts in the custom taxonomy term, we recommended the following steps: 1. Navigate to WPML -> Support -> Troubleshooting. 2. Execute the functions listed one by one as shown in this screenshot: https://prnt.sc/hQAyoQylDG6w 3. Clear the site's cache and check if the issue is resolved.
Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, 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 you still need assistance, please do not hesitate to open a new support ticket with us.
Problem: The client encountered a 'Commands out of sync; you can't run this command now' error in the WordPress database, which was found in the error.log file.
Solution: We recommend checking the database and server configuration, as this error often occurs when the database tables are not configured correctly. There may be other causes, and we suggest reviewing the following threads for detailed information:
We also advise discussing the issue with your hosting or service provider and sharing your findings with them.
Please note that the solution provided might be outdated or not applicable to your specific case. If the issue persists, we highly recommend checking related known issues, verifying the version of the permanent fix, and ensuring that you have installed the latest versions of themes and plugins. If you still need assistance, please open a new support ticket with us.
Problem:
The client tried to translate some pages created with Bricks builder but only the page title was available in the advanced translation editor.
Solution:
The string translation plugin was disabled and it's required to translate the content created with the Bricks theme.
Nous utilisons des cookies pour optimiser notre site web et nos services. Votre consentement nous permet de traiter des données telles que le comportement de navigation. L'absence de consentement peut affecter certaines fonctionnalités.
Fonctionnel
Toujours activé
Nécessaire au bon fonctionnement et à la communication de notre site web.
Préférences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistiques
Nous les utilisons pour analyser les statistiques de notre site. Les informations collectées sont totalement anonymes. Le stockage ou l'accès technique qui est utilisé exclusivement à des fins statistiques anonymes. Sans citation à comparaître, la conformité volontaire de la part de votre fournisseur d'accès Internet ou d'autres dossiers d'un tiers, les informations stockées ou récupérées à cette fin ne peuvent généralement pas être utilisées pour vous identifier.
Marketing
Ces cookies suivent votre navigation pour vous proposer des publicités pertinentes pour vous.
