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.
Problem: You are trying to translate a product using WPML, but the translation process is stuck and continuously shows as 'in progress'. Solution: We found that the issue was due to a specific shortcode:
For more details on how to register shortcodes, please check this guide. After registering the shortcode, please resend the products for translation and check if they translate correctly.
If this solution does not apply to your case, or if it seems 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 issue persists, please open a new support ticket.
Problem: The client needed to reinstate the language option next to the search icon on their website. During the translation process, the entire header was deleted, and although the flags were restored, they were incorrectly positioned and styled. Solution: We recommended the client to ensure they have a backup of their site, which can be done using the UpdraftPlus plugin. After confirming the backup, we provided custom CSS to correct the positioning and styling of the language switcher. Here is the CSS code we used:
.sitepress_container > .wpml-ls ul ul li a:hover::after {
background-color: transparent!important;
}
}
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 is working on a site under development and wants to customize the WPML currency switcher by removing the border and adding country flags to the currencies. Solution: To remove the border from the currency switcher, the client should insert the following custom CSS code into WP > Appearance > Customize > Additional CSS:
.wcml-dropdown li {
border: 0px solid!important;
}
If this solution does not apply to your case, or if it seems 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. Should you need further assistance, please do not hesitate to open a new support ticket at our support forum.
