Problem: You are experiencing issues with WPML not properly displaying the Elementor loop of boats on your custom post type "Boat" created with Pods. Additionally, translations are detected but not saved on your staging site, and you are concerned about the consumption of AI translation credits. Solution: First, ensure that both your production and staging sites are connected to the same Automatic Translation Engine (ATE) account to share translation memory and credits. This setup prevents the consumption of additional credits for re-translating the same content. You can confirm your setup under WPML → Translation Dashboard → Tools. For more details, visit Automatic Translation Subscription for Multiple Sites.
For the issue of translations not being saved, it is recommended to switch to manual translation for the affected content. This involves disabling the WPML Translation Editor for these specific pages and manually adjusting the translations. You can find more information on this process at Pods Custom Content Types and Fields and Using Different Translation Editors for Different Pages.
If these solutions do not resolve your issues or if they seem outdated or irrelevant 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 further assistance is needed, please open a new support ticket at WPML Support Forum.
Problem: The client reported that despite having a completed German translation of their homepage, the page still displayed in Dutch when accessed via the German URL. This issue was specific to the homepage, as other German pages displayed correctly.
Solution: We recommended several troubleshooting steps: 1. Update the original Dutch homepage in the WordPress editor without making changes to help WPML re-register all content for translation. 2. Re-send the homepage for translation via WPML → Translation Dashboard, ensuring German was selected, and then finalize it in the Advanced Translation Editor. 3. Clear Elementor's cache and regenerate CSS by navigating to Elementor → Tools → Regenerate CSS & Data and clicking the Regenerate Files button, followed by clearing the cache in Elementor → System Info → Tools. When these steps did not resolve the issue, we escalated the problem for further investigation, suspecting a synchronization or caching conflict due to Elementor Pro integration.
If this solution does not resolve your issue, or if it 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.
Problem: The client has a WPML website with many ACF groups, including clones with repeaters inside. Despite setting translation preferences correctly, many fields set to 'Translate' do not appear in the Advanced Translation Editor (ATE) or get translated automatically via the Translation Dashboard. Solution: The issue was due to clone fields used multiple times on a single page where some inner fields had the same name, set to seamless without a field name prefix. This caused problems with translating specific sections. The solution involved: 1. Activating an inactive field group. 2. Synchronizing field translation preferences with JSON using the ACF tools. 3. Resaving the original homepage and its translations. For detailed steps on setting translation preferences for ACF fields and synchronizing them with WPML, visit WPML documentation.
If this solution does not resolve your issue, or if it 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 needed, please open a new support ticket at WPML support forum.
Problem: The client reported that WPML was not saving translations on their staging site, despite showing a green checkmark. They also encountered a 500 Internal Server Error when trying to access the admin login, and had issues with server restrictions based on geographic location. Solution: We advised the client to share admin access and the steps to reproduce the issue for efficient troubleshooting. After several attempts with different VPN locations, the client managed to provide correct access. We discovered that the issue was related to incorrectly migrated or created database entries. We reset WPML, set it up again, and successfully translated the front page. We also moved the translation memory from the previous website to the new one, ensuring that the client could re-translate pages without being charged for existing translations.
If this solution does not resolve your issue, or if it 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 problems persist, please open a new support ticket at WPML support forum.
Problem: If you're experiencing a layout issue in the WordPress admin post list where the post title column becomes extremely narrow when WPML is active, making the titles wrap vertically and difficult to read. Solution: This issue is not specifically related to WPML. In WordPress, the number of columns in the admin post list can cause the title column to be squeezed, especially when SEO plugins that add additional columns are active. We recommend that you click on Screen Options at the top of your admin panel and deselect the columns that are not necessary. This action will free up more space and potentially resolve the layout issue.
Please note that this solution might be irrelevant if it's 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 for further assistance.
Problem: The client reported an issue with the property slider on the French version of their website, where the cover photo appears in the desired size, but subsequent photos are smaller. This problem does not occur in the English version. Additionally, there was a problem with a translation not being published, potentially due to a server connection issue or a previously created page not being fully deleted. Solution: We suggested monitoring the situation with the property images to see if the issue recurs with future listings, as it was initially observed with only one property. For the translation issue, we recommended checking the server connection and ensuring that any previously created pages were fully deleted. If these steps do not resolve the issues, we advised the client to try using the
Regenerate Thumbnails plugin
to rebuild all image sizes from the original files.
Please note that this solution might be outdated or not applicable to your specific case. If the problem 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 necessary, please do not hesitate to open a new support ticket for further assistance at WPML support forum.
Problem: The client was facing an issue where the header and footer created with Elementor and Ultimate Addons for Elementor were not displaying for non-default languages, despite having completed translations for these elements. Solution: We identified that the "Display Rules" were missing on the translated templates. To resolve this, we: 1. Navigated to WPML > Settings > Custom Fields translation. 2. Set the following fields to "Copy":
ehf_target_include_locations
ehf_target_exclude_locations
ehf_target_user_roles
ehf_template_type
display-on-canvas-template
3. Updated the translations for the templates, which resolved the issue. For more detailed guidance, please refer to our documentation on Translating Custom Fields.
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 persists, please open a new support ticket.
Problem: The client was experiencing an issue where the homepage translation in WPML was getting stuck with a gear icon and not completing, despite the job showing as completed. This was only happening on the homepage, and other pages were translating normally. The issue was observed when using the Avada Live Builder, and the client noted that the loader spun indefinitely when clicking 'Save', although the changes were saved upon refreshing.
Solution: We first attempted to clear any stuck translation jobs and ensured no automatic translation jobs were interfering. After confirming these settings were correct, we identified a PHP Fatal Error due to memory exhaustion as the root cause. We resolved the issue by increasing the memory limits in the 'wp-config.php' file with the following code:
After increasing the memory limit, we retranslated the homepage via WPML->Translation Dashboard, and the translation was successfully completed, indicated by a pencil icon.
If you're experiencing similar issues, we recommend checking your memory settings and ensuring they are sufficient for your site's demands. Additionally, if this solution does not resolve your issue or seems irrelevant due to different configurations or updates, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If problems persist, do not hesitate to open a new support ticket with us for further assistance at WPML support forum.
Problem: The client experienced an issue where PayPal charged the wrong card during a transaction. Solution: If you're experiencing a similar issue where the wrong card was charged, we recommend you directly email our administrative team at https://wpml.org/home/contact-us/contact-form/.
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.
