Problem: The client is experiencing a PHP Fatal error during the import process using the WPML plugin, specifically when using the WPML All Import addon. The error message indicates a type error with array_filter() expecting an array but receiving a boolean.
Solution: 1. We recommend deactivating all plugins except for WPML and any essential plugins required for the import. 2. Navigate to WPML → Settings → Troubleshooting and perform the following actions: - Clear the cache in WPML - Set language information - Fix the collation of element types - Remove ghost entries from the translation tables - Assign translation statuses to duplicated content 3. Replace the outdated 'WPML All Import' addon with the new 'WPML Export & Import' addon, which is compatible with WP All Export, WP All Import, and native WordPress and WooCommerce export and import methods. You can download it from here. 4. Ensure that the import process in WP All Import is fully completed before running the WPML importer in WPML > Export & Import.
If you're still experiencing issues after following these steps, or if the solution provided here becomes 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 the problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is experiencing an issue where Divi heading tags, such as blurbs or text, are not being translated when sent to the translation agency, Translate 1.
Solution: We disconnected the sites to access the Advanced Translation Editor on the staging site. We used an example page and confirmed that the header text was visible in the original language and in the Advanced Translation Editor. We then sent the page for translation and verified that the title was present in the downloaded XLIFF file. We suggested that the client should try to reproduce the issue on the staging site, as it might be a plugin conflict that doesn't occur in the minimal settings environment of the staging site. If the issue persists on the staging site, we asked the client to inform us about the specific page and title used for testing so we could investigate further.
