Giải pháp có sẵn

Problem:
The client was unable to export translation files (ZIP or XLIFF) from their WordPress site using WPML with BeTheme and Muffin Builder. Despite following previous advice to ensure Muffin Builder content was stored as serialized and consulting relevant documentation, the exported files were still coming out empty.
Solution:
1. Confirm that Muffin Builder data storage is set to 'Serialized | Readable format' under BeTheme → Theme Options → Global → Advanced.
2. Edit the affected page in WordPress, make a temporary change to the page title, update it, then revert the change and update again.
3. Re-export the translation files. If the issue persists, check the XLIFF file options under WPML → Settings to ensure they are set to default and not excluding content.
4. Verify the translation job status in WPML → Translations to see if it is listed and check its status.
5. If the problem continues, it may be necessary to inspect the site’s translation job queue and XLIFF export logic, focusing on global WPML export settings and any server-level blockers.

If this solution does not resolve the issue or seems outdated, 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 problems persist, please open a new support ticket.

Problem:
The client is experiencing issues with the translation of home page filtering not appearing as expected on their website.
Solution:
We recommend the following steps to resolve the issue:
1. Ensure all WPML plugins, including WPML Multilingual CMS and String Translation, are updated to the latest versions. You can update these in the Plugins -> Add new -> Commercial tab.
2. Increase the WordPress memory limit to at least 256MB. This can be done by adding the following line to your

wp-config.php

file:

define('WP_MEMORY_LIMIT', '256M');

Place this line just above the '/* That's all, stop editing! Happy publishing. */' line.
3. Depending on how your filters are constructed:
- If based on categories, tags, or custom taxonomies: Translate these under WPML → Taxonomy Translation.
- If based on custom fields: Set the translation preferences for these fields under WPML → Settings in the Custom Field Translation section.
- If the filters involve strings from your theme or plugins: Use WPML → String Translation, and you might need to scan your theme or plugins for strings first under WPML → Theme and plugins localization.

If these steps do not resolve the issue or if the solution seems 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 further assistance is needed, please open a new support ticket at WPML support forum.

Problem:
The client was experiencing issues with 'Jobs could not be loaded' and cURL 28 timeouts after trying to reset the Advanced Translation Editor (ATE) communication record and reinstalling WPML Translation Management.
Solution:
1. **Increase WP Memory Limit**: Access the site's

wp-config.php

file and add or update the line:

define('WP_MEMORY_LIMIT', '256M');

to ensure sufficient memory for WordPress and WPML operations.
2. **Cancel Stuck Translation Jobs**: Navigate to **WPML → Translation Dashboard**, switch to the **Jobs** tab, select any jobs showing errors, and click **Cancel selected jobs**. Make a minor edit to the content and resend for translation.
If these steps do not resolve the issue or if the problem persists, it might be due to outdated solutions or specific circumstances not covered here. We recommend visiting https://wpml.org/known-issues/ to check for any related 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 continues, please open a new support ticket with us for further assistance.

Problem:
The client was experiencing an issue where the translation status of a self-translated article on their website was not updating correctly, showing as still in progress despite efforts to resolve it.
Solution:
Еnsure that you have cleared the cache, deleted any translation jobs related to the post, and then delete and re-add the translated article. This process should help ensure the translation status is updated correctly. If you're experiencing this issue, we recommend you try these steps:
1. Clear your site's cache.
2. Delete any existing translation jobs for the affected article.
3. Remove the translated article and add it back to your site.
This approach should resolve the issue with the translation status not updating. However, if this solution does not work or seems outdated, or if it does not apply to your case, please visit our known issues page to check for related issues. We also recommend verifying that you have installed the latest versions of themes and plugins. If the problem persists, do not hesitate to open a new support ticket with us for further assistance.