Problem: The client is trying to ensure their logo appears on all language versions of their site using Astra and Elementor Pro. The logo only displays on the English version, and when attempting to set it for other languages via the WordPress Customizer, the logo field is unresponsive and cannot be edited.
Solution: 1. Confirm the logo is set in the Customizer’s header/logo section for the default language (English). 2. Switch the Customizer preview to another language using the language switcher in the top WordPress admin bar (e.g., select Danish). 3. Check if the logo field is filled for the secondary language. If it’s empty, select the same logo image as your default language and click Publish. 4. If the logo field is already filled for each language but still not showing, further troubleshooting might be needed to check for header template overrides or caching issues.
This solution might be outdated or not applicable to your specific case. If the issue persists, 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 needed, please open a new support ticket here.
Problem: The client is experiencing an issue where a URL in the footer does not translate correctly on the Danish and German versions of their site, despite being saved in WPML's string translations. The issue is that the URL appears with an extra 'www' which leads to missing links. Solution: We recommend checking and adjusting the URL directly in the menus for each language. Here are the steps to follow: - Go to Appearance > Menu - Click the Pencil icon beside the Language name. - Open the menu item and adjust the link by removing the 'www' part.
This solution might not be relevant if the details of the issue have changed, or if it's outdated. If this doesn't resolve the issue, or if the problem described doesn't exactly match your situation, please visit our support forum to open a new 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.
Problem: The client was unable to display the same logo across all pages on their secondary domains when using Elementor Pro and the Astra Pro theme.
Solution: We recommended the following steps to resolve the issue:
Go to WPML > Languages > Languages URL format.
Temporarily change the URL format from
Pass arguments via GET (the URL)
to
Pass arguments via POST
.
Remove "www" from the secondary domains.
Save the changes.
Resave permalinks.
Clear the cache from Lightspeed. It might be necessary to log in per language and clear the cache for each language separately.
By following these steps, the client was able to resolve the issue.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If you're still experiencing issues, we encourage you to open a new support ticket. We also highly recommend checking related 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 contact us through the WPML support forum.
Problem: The client reported that an automatic translation was stuck and mentioned a specific job ID. After blocking the latest stuck translation update, the translation seemed to be working again. Solution: We recommended the client to try using the WPML Translation Editor in a different browser and to perform a hard refresh by pressing
Ctrl + Shift + R
(or
Cmd + Shift + R
for Mac users) while using the Translation Editor. Upon further investigation, we identified a fatal error related to Elementor Pro, which prevented the translation job from being downloaded back to the website. We resolved the issue by canceling the pending automatic job, making a slight change to the original homepage, reverting it, saving it, and completing the translation again.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If you're still experiencing issues, we highly recommend checking the related 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 with us.
Problem: The client is experiencing an 'Internal Server Error' on their website pages when activating WPML or reviewing translated pages. The error log indicates a PHP Fatal error with the message 'Uncaught InvalidArgumentException: Argument ID must be numeric and greater than 0.' This issue is related to the WPML plugin and Elementor page builder. Solution: 1. We recommend activating the WordPress debug mode by following the steps described in this guide. 2. After enabling debug mode, reproduce the error to generate a new entry in the debug.log file. 3. Review the debug.log file for the latest fatal error message. 4. Apply the workaround provided on the WPML errata page, which can be found here: WPML Errata. 5. Ensure to create a full backup of the site before applying the workaround.
Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, 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 assistance, please open a new support ticket with us.
Problem: The client was unable to review translations on their other domains and received the error message "Sorry, you are unable to review drafts". They had already tried clearing the cache and checking for valid domain registration and translation pairs.
Solution: We recommended increasing the WP memory limit to at least 128MB, as per WPML's minimum requirements. The client was instructed to add the following code to their
We also advised the client to check with their hosting provider if the hosting settings limit these values and to verify the changes on the WPML Support page.
Additionally, we suggested ensuring that the server meets WPML's minimum requirements and that the latest WPML versions are in use. If the problem persisted, we advised testing for a compatibility issue by deactivating all non-WPML plugins, switching to a default WordPress theme, and then trying to recreate the issue. If the issue was resolved, the client should reactivate plugins one by one to identify the cause.
If the solution provided here is not relevant due to being outdated or not applicable to your case, we highly recommend checking related 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 with us.
