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: 1. Icons not displaying when switching languages due to CORS errors. 2. Slider Revolution content translation error, even after following the documentation.
Solution: 1. For the icons issue, we recommended adding the following code to the .htaccess file to fix CORS errors:
<filesmatch ".(eot|otf|ttf|woff|woff2)">
Header always set Access-Control-Allow-Origin "*"
</filesmatch>
2. We advised updating Elementor Pro to the latest version and re-checking the steps for translating Slider Revolution content as per the documentation.
If the solution provided here is not relevant to your case, either because it's outdated or not applicable, we highly recommend checking related known issues at WPML's known issues page, 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 in the WPML support forum.
