Problem: The client's footer is not translated and does not appear in the strings. Solution: If you're experiencing this issue and you used Divi to create your footer, we recommend you refer to the following articles for instructions on translating the Global Footer:
If you have already completed the translation but it is not displaying correctly on the front end of your site, please try the workaround mentioned in this errata: Divi Global Footer Translation Issue, and see if that resolves your issue.
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.
Problem: You are trying to translate strings using WPML but encounter the 'Waiting for Translator' status instead of seeing the translations. Solution: 1. Navigate to WPML → Translations to manually take and translate the strings, or cancel the string translation jobs from WPML → Translation Management → Jobs tab. 2. Ensure a translator is available by checking WPML → Translation Management → Translators and verifying the correct Translation Pair. For more details on setting up translators, visit Translating Strings Automatically on a Site with Multiple Translators. 3. Update your WPML plugin and add-ons to the latest version, currently 4.7.2, to benefit from the latest bug fixes and improvements. Instructions for updating can be found at WPML Installation FAQ.
If this solution does not apply because it might be outdated or not relevant to your specific case, we highly recommend checking related known issues at WPML 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 help, please open a new support ticket at WPML Support Forum.
Problem: The client is unable to allocate WPML credits on their site, receiving a message that no credits are available. Solution: We adjusted the credits for the client. If you're experiencing this issue, we recommend checking if the credits are now available. Additionally, if you move your site from staging to production, or if there are changes in the site URL or server, you will need to create a new site key at wpml.org and register the site again.
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 at WPML support forum.
