Problem: If you're experiencing an issue where a bar at the bottom of your site is still visible after switching from development to production, this can be frustrating. Solution: We recommend checking the following documentation on how to remove the 'This site is registered on WPML.org as a development site' notice. If the notice persists even after following these steps, it might be due to caching or settings that need to be updated. Please visit How to Remove the Development Site Notice.
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 the issue persists, please do not hesitate to open a new support ticket with us for further assistance.
Problem: You are using WP All Import to upload listings directly to the second language on your site, but the translated listings are going into the English listing section. Solution: It is not possible to directly import translated listings into the second language in WPML using a single import. To properly import listings into multiple languages, including already translated ones, you will need to perform two separate imports: 1. First Import: Import the listings in the default language (English, in this case). 2. Second Import: Import the listings in the second language. For this to work, you must add a unique identifier to your spreadsheet. This identifier will allow WPML and WP All Import to correctly link the translated listings to the original ones. For more details, please refer to the following documentation:
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: When translating listings in bulk, approximately 30% of the translated listings are missing photos. The images are not copied over from the original English listing, and this issue persists even after deactivating Jetpack's image CDN, clearing cache, resaving permalinks, and re-uploading and translating the listings. Solution: First, ensure that Jetpack's image CDN is disabled as it might be serving images from incorrect paths. Follow these steps: 1. Disable Jetpack's image CDN. 2. Resave the permalink structure by navigating to Settings > Permalinks. 3. Make a minor edit in the default listing and update the translation. 4. Clear the caches on your site and browser. If the issue persists, perform these additional steps: 1. Navigate to WPML > Support > Troubleshooting. 2. Select 'Listings' from the dropdown under cleanup and click on the "Synchronize Post taxonomies" button. Then select "Media" and repeat the process. 3. Click the following buttons in WPML: - Clear the cache in WPML - Set language information - Fix post-type assignment for translations 4. Clear the caches again on your site and browser. If these steps do not resolve the issue, you may need to update the translation of those listings again to ensure the image paths are also updated correctly in the translation.
If the solution provided here 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 the problem persists, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client reported an issue where the "origin" value reverts back to its previous state every time a translation is run, even after clearing the cache.
Solution: We recommend using the Glossary feature of the Advanced Translation Editor. For translations using DeepL, the Glossary will automatically apply the suggested term. However, for Google or Microsoft translation engines, this feature is not supported, and manual adjustments using the Glossary inside the Advanced Translation Editor will be necessary. Additionally, any translations already saved in the translation memory will need to be corrected manually.
If this solution does not apply to your case, or if it is outdated, we encourage you to open a new support ticket. We also 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 need further assistance, please contact us in the WPML support forum.
