Problem: The client reported that Elementor was not loading properly, suspecting a conflict caused by a custom code snippet. Solution: We suggested a workaround to help isolate the issue: 1. Use another admin account or create a new admin account. 2. Log in with this new admin account and test the Elementor page to see if it still displays in Safe Mode or functions correctly.
If this solution does not resolve the issue or seems irrelevant due to being outdated or not applicable to your case, we recommend opening a new support ticket. Additionally, 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. For further assistance, please visit our support forum at WPML Support Forum.
Problem: If you're experiencing issues installing WPML CMS and String Translation via the OTGS installer, such as receiving a 'Download failed. (Method Not Allowed)' error or no installation occurring despite no error messages, the problem might be due to hosting limitations. Solution: We recommend trying a manual installation of the WPML plugin. Here are the steps: 1. Log in to your WPML account at https://wpml.org/account. 2. Navigate to the 'Downloads' section and download the latest version of the plugin(s) you need. 3. In your WordPress admin panel, go to Plugins → Add New and click 'Upload Plugin'. 4. Choose the ZIP file you downloaded and click 'Install Now', then 'Activate'.
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 for further assistance.
Problem: If you're experiencing issues with updating images in blog posts and syncing them across different languages using WPML, and if you find the process time-consuming, especially with multiple posts, you're not alone. Additionally, if user profile images are not visible in other languages when media is translatable, or if popups, modals, and title bars are not showing correct translations, these could be indicative of configuration issues. Solution: We recommend checking the translation settings for your templates and ensuring that the template IDs are correctly translated. For instance, to address the title and widget translation issues, you can translate the template ID at WPML String Translation page. After making these adjustments, please verify the changes by visiting your translated pages.
It's important to 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 problem persists, please open a new support ticket.
Problem: The client is experiencing issues with updating images in blog posts and syncing translations, which is time-consuming. Additionally, user profile images are not visible in other languages when media is translatable. There are also problems with popups and modals not showing correct translations, and the title bar in the blog section not reflecting the correct language. Solution: We addressed the popup modal issue by correcting the links in the templates. For the issue of category titles and widgets not showing translations, we have created a separate ticket to follow up. Currently, there is no automated way to assign correct popups with their translations without manual template editing. We recommend installing the required plugins and replicating the issue on our sandbox site for further investigation by our 2nd Tier Support.
If this solution does not resolve your issue or seems outdated, 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 the problem persists, we highly recommend opening a new support ticket at WPML support forum.
Problem: If you're experiencing an issue where the resource count in your inventory drops twice as much as expected when booking an activity with a resource using WooCommerce Booking, this might be due to a known issue. Solution: We recommend checking if your issue matches the known problem described here: WooCommerce Bookings Max Bookings Per Block Not Working Correctly. If this matches, please update WooCommerce Multilingual & Multicurrency to the latest version (5.5.1 or higher), as this issue has been resolved in these updates.
If the solution provided here is outdated or does not apply 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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: The client experienced 404 errors and missing admin panel lists for posts, pages, and custom post types after activating the WPML plugin on their production site, despite the staging site working correctly. Solution: 1. We recommended creating a staging site using the WP Staging plugin to safely replicate the issue without affecting the production environment. 2. After verifying that the WPML plugins were not causing the 404 errors on the staging site, we suggested manually checking the WPML tables in the database, which appeared correct. 3. We advised the client to try reproducing the 404 errors by activating the theme and plugins one by one to identify the problematic component. 4. If the issue persisted, we recommended manually uploading the WPML plugins via the Plugins section in the WordPress admin. 5. We identified missing tables related to WPML in the database on the production site and fixed them.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please visit our known issues page and ensure you have the latest versions of themes and plugins installed. If the problem continues, we highly recommend opening a new support ticket at WPML support forum.
Problem: You are trying to auto-translate products using WPML and encountering an error message indicating insufficient credits, despite having a valid credit card linked to your account. Solution: The issue arises because you may have reached the safety limit for translations set by WPML. There are two thresholds: €100 and €4,000 in a single month. Once these limits are reached, you need to pay upfront to continue. The prepaid amount will be deducted from your total monthly invoice. To resolve this, follow these steps: 1. Navigate to a page or post with a lot of untranslated content. 2. Click the "+" icon to add a translation. 3. In the Automatic Translation Editor (ATE), if you exceed the safety limit, a "Not enough credits" message will appear with a link to "Get more credits." 4. Click this link to make a payment and unlock further translations. For more details, refer to the WPML’s terms and conditions.
If this solution does not apply to your case, or if it seems outdated, 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. Should you need further assistance, please open a new support ticket.
Problem: The client reported an issue where it seemed that translation jobs were stuck or not updating properly in the WPML Translation Management system. Solution: We checked the WPML > Translation Management > Jobs and confirmed that there were no jobs "in progress"; all jobs were marked as completed. We also manually opened the translation editor for the pages, verifying that each was at 100% completion and that there were no issues with saving the translations. It appears that clearing the cache might have resolved the issue, as the client suggested.
If you're experiencing similar issues, we recommend trying to clear your site's cache and then check the status of translation jobs in WPML > Translation Management > Jobs. If the problem persists, please visit our support forum for further assistance. Additionally, 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.
Problem: You are unable to register WPML on your site despite multiple troubleshooting steps, including contacting your hosting provider, deactivating plugins, and reinstalling WPML. Solution: We have checked & unblocked your site and tested it, confirming that it is now working correctly. To successfully register WPML, please follow these steps: 1. Log in to your WPML.org account and navigate to the Sites page. 2. Delete the existing site key. 3. Log in to your site, go to the Dashboard >> Plugins >> Add new >> Commercial tab and click the Unregister WPML from this site link. 4. Click the Register WPML link. 5. Click the Get a key for this site link to generate a new key. 6. Copy and paste the new key into the input box and press the Register button.
If this solution does not resolve your issue or seems irrelevant 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 problems persist, please open a new support ticket.
Problem: After migrating the domain from gstcouncil.org to gstc.org and re-registering WPML with a new license key, some translation pages are not visible to users who are not logged in, showing a 404 error instead. The error log indicates a URL change detected by WPML. Solution: The issue was identified as related to the Toolset Access Plugin. We recommend checking the configuration of the Toolset Access Plugin to ensure it is not misconfigured, which might be restricting access to certain pages. If deactivating the Toolset plugin resolves the issue, confirming that pages become visible, further assistance should be sought from the Toolset support team. You can open a new ticket for Toolset-related issues at Toolset Professional Support.
Please note that this solution might be outdated or not applicable 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 the problem persists, please contact our support team for further assistance.
Problem: The client is unable to see some links in the Advanced Translation Editor while trying to translate the homepage. Additionally, the language flag is not displayed on some pages, and there are concerns about design changes post-translation. Solution: We enabled translation for the homepage and suggested using the search form in the Advanced Translation Editor to type "HTTP" to list all links for translation. For the design issues on the translated page, we created a separate support ticket to address this specifically. If you're experiencing similar issues, we recommend trying the following steps: 1. Ensure that the translation for the homepage is enabled. 2. In the Advanced Translation Editor, use the search form and type "HTTP" to find and translate missing links. 3. Check the separate support ticket for solutions related to design changes after translation.
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 https://wpml.org/forums/.
Problem: The client imported glossary entries successfully but later could only see a fraction of these entries when trying to edit them. Despite expecting to see all 396 entries, only 5 were visible.
Solution: We recommend the following steps if you're experiencing similar issues: 1) Ensure to take a full backup of your site and database. It's best to perform these steps on a development or staging site first. 2) Deactivate all plugins except for WPML and String Translation. 3) Switch to a standard theme, such as 2024 or 2021. 4) Check if the glossary entries are visible. If not, attempt to re-import the CSV file, making sure to check “Overwrite existing terms” during the import and ensure the "kind" column only contains the value "name" (Reference Errata). 4.1) If the issue persists, stop here and do not proceed further. 5) If the entries are visible, begin reactivating plugins one by one, checking after each to see if the issue reoccurs. This will help identify any plugin conflicts. 6) If after reactivating all plugins the entries are still visible, switch back to your original theme to check if it causes the issue.
If these steps do not resolve the issue or if the solution 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: You are trying to activate automatic translations on a WPEngine instance but encountered an issue where the system reports you are out of credits despite having allocated them. Additionally, on your local development instance, the WPML -> Translation Management -> Translation Tools page is endlessly loading, and you are seeing 500 errors from the WPML API indicating a MySQL server read-only error. Solution: The 500 errors and the MySQL server read-only messages suggest a server-side limitation, not an issue directly caused by WPML. This server state is preventing the automatic translation services from functioning correctly. For the credits issue, once credits are allocated in your WPML.org account for the WPEngine instance, they should appear there. The error about missing credits likely stems from the server's inability to validate the credit balance properly due to the same API access issue. When migrating from a development to a live environment, ensure you use the Automatic Translation Editor (ATE) for moving or copying the site to maintain the link between the instances and manage the translation memory effectively. If you skip the migration code, the sites won't be linked, which can overwrite the live site's organization ID and its translation memory.
If this solution does not resolve your issue or seems irrelevant due to being 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 problems persist, please open a new support ticket at WPML support forum.
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 problem persists, please open a new support ticket with us.
Problem: The client is unable to edit automatic translations on their bilingual website created with WPML, receiving a warning about potential loss of changes when using the page builder. Additionally, they face issues with URL translations for English posts, where 'nyheder' (Danish for 'news') does not automatically translate to 'news' in the URL, despite using a custom permalink structure. Solution: To address the issue of editing automatic translations without losing changes, we recommend avoiding direct edits in the page builder, as this can overwrite existing translations. Instead, use the Advanced Translation Editor provided by WPML. For the URL translation problem, first, ensure you have utilized the Translate Link Targets feature found under WPML → Settings. This feature helps in updating internal links to correctly point to the corresponding content in the target language. If 'nyheder' still does not translate to 'news' in your URLs, consider creating a custom parent category with the desired English slug and assign it to the relevant posts. This approach leverages the category/post-name permalink structure to maintain consistent URL appearances across different languages. Please note, if these solutions do not resolve your issues or if they seem 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 problems persist, do not hesitate to open a new support ticket for further assistance at WPML support forum.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
