Problem: The client updated internal links and content in posts, resulting in up to 50% of segments showing an orange bar and being untranslated or needing re-approval. This issue did not occur previously and was suspected to be related to recent server issues. Solution: The issue was due to the site not being properly registered and migrated between different environments (WPML test site, staging site, and production site). The site was moved, creating a new entry instead of copying the existing translation memory. We resolved this by manually merging the translation memory of all site organizations into the current one. The client should now cancel any affected 'In Progress' jobs at WPML > Translation Dashboard > Jobs, and create new jobs for the affected contents at WPML > Translation Dashboard. Assign the translations to yourself and access them at WPML > Translations. We have already applied this solution to the 'Best of Nightlife and Bars in La Spezia' and confirmed a 100% completed translation on ATE. Please verify if the issue is resolved by creating new translation jobs, as changes might not be visible on jobs currently in progress.
If this solution does not apply to your case, or if it 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 issues persist, please open a new support ticket at WPML support forum.
Problem: After moving the site from staging to live, the client is unable to access the Advanced Translation Editor (ATE). They encounter error messages indicating an inability to retrieve job details and a message about the website being under heavy load, despite server statistics showing otherwise. Solution: We have identified a temporary issue on our servers affecting the ATE access. Our technical team is actively working to resolve this. We recommend checking back in a few hours as the issue is expected to be resolved soon.
Please note that this solution might be outdated or not applicable to your case. If the issue persists, 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 needed, please open a new support ticket at WPML support forum for further assistance.
Problem: The client added custom XML configuration to the WPML settings and noticed that while the primary category translates correctly on the front end, the permalink in the backend does not update to the French version when switching languages in the Post Editor. The client is concerned about potential SEO issues and duplicate content. Solution: We confirmed that the primary category shown in the URL is indeed taken from the selected primary category for that language. We also verified that there are no duplicate content issues as the discrepancy only appears in the backend. Therefore, it is safe to ignore this backend behavior as it does not affect the front-end display or SEO.
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 the problem persists, please open a new support ticket.
Problem: After switching from Yoast to SEOPress, the primary category was not correctly assigned in languages other than English. The primary category field was missing in the Advanced Translation Editor (ATE) and was not translatable. Additionally, there was a looping issue in the WPML settings page, making it difficult to update settings. Solution: We identified the issue as a compatibility problem between WPML and SEOPress. To resolve this, we recommended inserting a custom XML configuration into WPML > Settings > Custom XML Configuration. This configuration ensures that the primary category is correctly used on translated posts, although it may still display as 'none' in the backend. The necessary XML is:
If this solution does not resolve your issue or seems outdated, please check the related known issues, verify the version of the permanent fix, 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 here.
Problem: If you're experiencing issues where segments become untranslated after saving them in the Advanced Translation Editor (ATE), even though you've translated every segment and saved the translation, this might be similar to the issue we recently addressed. Solution: We recommend checking if any translations are flagged for "save later". This can sometimes occur without immediate notice. If you find such flags, you should complete these translations and save again. If the problem persists, translating additional pages might help identify if the issue is recurring or isolated.
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 continues, please do not hesitate to open a new support ticket at WPML support forum.
Problem: If you're experiencing a looping issue even after deactivating all plugins except WPML, and it seems to loop faster, the problem might be related to your .htaccess file. Solution: We recommend generating the default WordPress .htaccess file and replacing the current one with it. This change might resolve the looping issue. If the default .htaccess file resolves the issue, you should then update or modify the needed mod_headers rules accordingly.
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 for further assistance.
Problem: The client encountered a WPML message in their WordPress dashboard asking if their main site laspeziaguide.com is a duplicate of a non-existent domain wpml.wpml.laspeziaguide.com. This message was confusing as the domain mentioned does not exist and the client had not recently created a staging site with that URL. Solution: We determined that the message was not generated by WPML but possibly by other plugins (Admin Site Enhancements or Unlimited Elements for Elementor) that check for a license. The client should verify which plugin generated the notice by following any available links in the message for more information. If the issue persists, the client should contact the support for those plugins. Additionally, we resolved the issue from our side by adjusting the organization IDs and merging them in our system, ensuring the client can continue using the Pay as you go system for translations. To prevent future issues, follow the steps outlined in the WPML documentation on handling site copies: Using Advanced Translation Editor when you move or use a copy of your site.
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 issues persist, please open a new support ticket.
Problem: You are experiencing issues with symbols being incorrectly inserted in Italian translations using WPML, such as unnecessary spaces and quotation marks instead of apostrophes. This problem is attributed to the translation engines, particularly Deepl, which interprets these insertions as correct grammar. Solution: We recommend using Microsoft or WPML AI for translations as these engines do not frequently exhibit this issue. We are actively working to improve our systems to gain more control over translation outputs. In the meantime, if possible, manually correct the errors in the translated content. Additionally, we have added 3000 credits to your site for testing purposes. If the problem persists, please provide temporary access (wp-admin and FTP) to your site for further investigation. Ensure to back up your site files and database before providing access, and verify that you are using the private fields for submitting sensitive information. For more details on privacy and security, please visit: Privacy and Security Policy.
If this solution does not resolve your issue or 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 necessary, please open a new support ticket for further assistance.
Problem: If you're experiencing issues with the primary category not being correctly represented in the Language Switcher for Spanish URLs, leading to incorrect URL structures on page load, particularly after updating to version 4.7.4, this might be due to a compatibility issue with the Only Top Category option of the Grid Post widget from the Unlimited Elements for Elementor (Premium) plugin.
Solution: First, we recommend replicating the issue on a clean installation to confirm it's a compatibility issue. Here are the steps: 1. Install Unlimited Elements for Elementor (Premium) on a clean WordPress installation with Elementor, Yoast, WPML, and all necessary WPML add-ons. 2. Create the same situation and try to replicate the issue.
Additionally, there is a workaround provided by our compatibility team: 1. Open the file
function on line 574. 3. Replace the existing code with the new code provided, which includes a WPML filter to ensure the primary category ID is correctly translated. 4. Clear Elementor's cache by going to "Elementor > Tools > Clear Files & Data" and ensure the translation is 100% complete.
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. If the problem persists, please open a new support ticket at WPML support forum for further assistance.
