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 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.
