Problem: If you're experiencing issues with the gear icon appearing after manually updating translations using the Classic WPML Editor, and suspect it's causing unnecessary database growth due to repeated update prompts, this might be due to an object cache interference. Solution: We recommend disabling the object cache while performing translations to prevent this issue. Additionally, you can enhance the system by implementing a specific plugin designed to handle such cases. Here are the steps to create and add the plugin: 1. Navigate to the
1
/wp-content/
folder on your site. 2. Create a folder named 'mu-plugins' if it doesn't exist. 3. Inside the 'mu-plugins' folder, create a new PHP file (e.g., 'wpml-non-persistent-cache.php') and insert the following code:
If this solution does not resolve your issue, or if it seems 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. Additionally, feel free to open a new support ticket for personalized assistance at our support forum.
Problem:
Background of the issue:
I want to delete a Category so I previously edited the posts that contained it successfully. I also use Breeze and constantly purge cache so that nothing gets stuck.
Symptoms:
I see 0 posts on the category view for English but 6 on the Portuguese category page, and if I click there are actually no posts in there.
Questions:
Why are there still posts showing in the Portuguese category page after editing?
How can I ensure the category shows 0 posts in all languages?
Solution:
It seems the issue was related to caching. Once the caching plugin was disabled we were able to run the cleanup steps and the numbers were corrected.
Problem: The client reported an error stating 'WPML could not load configuration files, which your site needs.' The RETRY button was not functioning, and despite clearing the log, the issue persisted. The client was concerned about the impact of this error on their site's functionality, especially with an upcoming site update. Solution: We advised the client to ensure their server's connection settings were correct and to check if any IP addresses needed to be whitelisted by their hosting provider. We recommended following the steps in our documentation on connection issues at https://wpml.org/faq/wpml-plugin-cannot-connect-to-wpml-org/ and also referred them to an errata page for a similar issue at https://wpml.org/errata/wpml-could-not-load-configuration-files-which-your-site-needs/. Additionally, we emphasized the importance of keeping all WPML plugins updated for better stability and security, instructing the client to perform a full backup before updating.
If this solution does not resolve your issue, or if it seems 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is experiencing issues with the WPML plugin where after manually translating a post using the WordPress Editor instead of the WPML Translation Editor, they see a 'Translation in progress - wait before editing' message and a gear icon, indicating an ongoing translation job. This occurs even though the client completes the translation manually without using third-party services.
Solution: 1. Cancel any ongoing translation jobs via WPML > Translation Management > Jobs. 2. Ensure the translation method for each content is set to 'WordPress Editor' if not using the WPML Translation Editor. This setting can be found in the right sidebar of the WordPress Editor under the 'Language' section. 3. If a dialog appears when changing the translation method, apply the setting to all similar post types or to all contents of the site. 4. It's safe to dismiss the warning notice about active translations in the WPML Translation Editor and proceed, especially if translating manually. 5. Contact the hosting provider to whitelist necessary domains to ensure proper communication with WPML services. The domains include wpml.org, cdn.wpml.org, api.wpml.org, api.toolset.com, and cloudfront.net. More details can be found in the documentation: WPML connection issues documentation.
If these steps do not resolve the issue or if the solution seems 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 problems persist, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is experiencing issues with WPML taking up a large portion of the database and automatic translation updates occurring despite using manual translations. The client wants to prevent these automatic updates and reduce the database size. Solution: 1. To manage ongoing translation jobs, navigate to WPML > Translation Management > Jobs and cancel all ongoing and in-progress jobs. For any pages still showing an in-progress status, manually save or update them in the second language. 2. For issues related to database size, refer to the errata on reducing the size of WPML tables: https://wpml.org/errata/reducing-size-of-icl_translate_job-icl_translate-and-other-wpml-tables/ 3. Advanced Custom Fields (ACF) field groups should be set as not translatable to avoid unnecessary translations: https://wpml.org/errata/advanced-custom-fields-field-group-should-be-set-as-not-translatable/
If this solution does not apply to your case, or if it seems 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are trying to ensure that CSS customizations made in the Avada Options are applied across all language versions of your site, but changes made on the English default site do not reflect on the Portuguese site. Solution: We recommend following these steps to apply the same CSS customizations across all language versions using the Avada theme: 1. Take a backup of your site first for safety reasons. 2. Navigate to Avada >> Options. 3. Set the language switcher in the admin bar to All languages. 4. Set your theme options/CSS and click Save Changes when done. For more detailed instructions, please refer to our documentation on using WPML with the Avada theme. If these steps do not resolve the issue, please add a debug report in the Debug Information box, which can be found here: Debug Information.
Please note that this solution might be irrelevant if it is 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 at WPML support forum.
Problem: The client is facing issues with some categories being displayed in the wrong language.
Solution: 1) We have published an errata regarding a fix for Object Cache Pro, which seems to be related to the problem. Please see Object Cache Pro - Various issues.
If this solution does not seem relevant to your issue, please feel free to open a new support ticket with us.
