Problem: The client is experiencing issues translating specific checkout text related to the delivery block in the WooCommerce Checkout Block using WPML. The strings do not appear in String Translation, and standard methods including scanning plugins, enabling string detection during page rendering, and using gettext filters have not resolved the issue.
Solution: We recommend updating all WPML-related plugins to ensure compatibility. If the issue persists, try replacing the WooCommerce Checkout Block with the classic WooCommerce shortcode
[woocommerce_checkout]
on the Checkout page. After making this change, perform a new scan for strings in WPML and check if the untranslated strings appear in String Translation. If these steps do not resolve the issue, it may require specialized attention. We suggest opening a new support ticket for further assistance. Additionally, 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 continues, please contact our support team by visiting our support forum.
Problem: The client is experiencing issues with custom widgets turning into 'Missing widget' entries after saving a page in SiteOrigin Page Builder, following updates to WPML v4.8.4 and String Translation v3.4.1. Additionally, there is a 404 error on the pagination of a custom post type archive, which temporarily resolves upon re-saving the ACF custom post type but reappears later.
Solution: We have determined that the issue with the widgets is not directly caused by WPML or String Translation, but rather by how the custom widgets are loaded and registered. Ensure that all custom widgets are registered using the standard
widgets_init
action and confirm that widget IDs and class names exactly match those saved in SiteOrigin. Also, check for PHP 8.3 compatibility as the plugin might use outdated code.
For the 'Missing widget' issue, disabling the 'Automatically detect best options for translating image texts' setting under WPML → Settings → Media Translation might resolve the issue. This is because WPML's media duplication process could be stripping necessary backslashes from the widget's data when saved in a secondary language. If problems persist, it's recommended to use
wp_slash()
when saving data to ensure backslashes are preserved.
If these solutions do not resolve the issues or if new problems arise, we recommend opening a new support ticket. Additionally, it's advisable to check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum at WPML Support Forum.
