I checked this together with our second-level team and we found the cause of the problem.
The issue was caused by translations in the **default** text domain. Many strings that do not need to be translated had been translated, and some of those translations were incorrect because they were missing required placeholders such as `%s` and `%d`.
We removed the unnecessary translations and corrected the invalid ones. After doing so, the Arabic page is now working correctly.
For future translations, please only translate the strings that are actually displayed on the front end. Also, if a string contains placeholders such as `%s`, `%d`, or similar, make sure to keep them exactly as they appear in the original string, as removing or modifying them can cause unexpected issues.
We are using WPML's automatic translation. In that case, how can we ensure that only the strings that are actually displayed on the front end are translated? Is there any recommended setting or best practice to prevent unnecessary string translations?
1. Some properties imported through WP All Import from our Bitrix feed are not automatically translated into all languages.
2. When properties are removed from the source feed, they are correctly deleted from the English website, but they often remain published on translated versions of the website.
3. We have a very large number of media files (approximately 100,000+) associated with translated content. Please check whether WPML Media Translation or translation records are creating orphaned or duplicated media entries that are not being cleaned up properly. Please help to delete those medias that are unused, becuase manual deleion is not possible for this huge amount.
1. Some properties imported through WP All Import from our Bitrix feed are not automatically translated into all languages.
In this case, after the import, could you please go to Properties in the WordPress admin and click Update on one of the affected properties (without making any changes)? Then check whether the translations are created or updated correctly.
Please let me know the result.
2. When properties are removed from the source feed, they remain published in translated languages.
Could you please try deleting one of these properties directly from the WordPress admin (instead of through the import) and let me know whether its translations are also deleted? This will help us determine whether the issue is related to the import process or to WPML.
3. Large number of media files
This is expected behavior. WPML creates a Media Translation record for each language, so multiple translation records for the same media attachment are normal and do not necessarily mean that duplicate files exist on the server.
Thank you for your message and sorry for late reply.
I updated one of the affected properties without making any changes, and the translations were created/updated correctly.
I deleted a property directly from the WordPress admin, and all its translations were also deleted successfully.
This confirms that the translations are updated correctly when the property is edited directly in WordPress.
For the properties that were not translated during the import, you can simply update the original property (without making any changes). This will trigger WPML to synchronize the translations and update them correctly.