Problem: The client's translated pages are not being indexed by Google, and the Google Search Console indicates a 'Page with redirect' error. This issue is likely due to WPML's language redirect settings. Solution: 1. Navigate to WordPress → WPML → Languages → Language URL format. Check if it is set to 'Different domains' or if there is a redirect causing a loop, such as from anantamassage.com/fr to anantamassage.com/fr/. 2. Go to WPML → Languages → Browser language redirect. If this setting is ON, turn it OFF. This setting might cause redirects based on the browser language, which Google interprets as a redirect, leading to the indexing issue.
If these steps do not resolve the issue, or if the information seems outdated or irrelevant to your case, we recommend opening a new support ticket. Additionally, 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. For further assistance, please visit our support forum at WPML Support Forum.
Problem: After activating WPML, the cart always shows a quantity of '1' on the client's site, which does not replicate on a test page. Disabling WPML resolves the issue, suggesting a potential compatibility problem with the Fly Cart plugin. Solution: We currently do not have a compatibility cooperation with the Fly Cart plugin, which might be causing the issue. To address this, we need to replicate the problem on a clean installation to better understand the compatibility issues. Here are the steps we recommend: 1. Access the clean WordPress installation we set up for you at this link. 2. Install the Fly Cart plugin on this installation. 3. Try to replicate the issue and inform us where to check to see the problem. This process will help us report the issue to our compatibility team and potentially expedite a resolution.
Please note that this solution might become outdated or may not apply to your specific case. If the issue persists, we highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If needed, do not hesitate to open a new support ticket at our support forum.
Problem: The client needed editors to access more WPML features, specifically the glossary function, without elevating them to Translation Managers. Despite being registered as translators, editors were unable to access or modify the glossary. Solution: We clarified that by default, editors do not have access to all WPML features. To allow editors to translate content, they must be added as translators via WPML->Translation Dashboard->Manage Translators & Services, which the client had already done. This setup enables editors to translate assigned content or initiate translations directly from pages or posts. However, for editors to access and manage the glossary, they must be assigned as Translation Managers. This role will allow them to update, add, or remove glossary items. The glossary itself automatically applies during translations in the Advanced Translation Editor, providing accuracy and context without direct editor intervention. For more details on managing glossary entries, visit How to Create and Manage Glossary Entries.
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.
