Problem: When saving a page's CSS in a translated page using Cornerstone, the function
copy_meta_fields
does not properly handle the slashing of values before passing them to
update_post_meta
. This results in incorrect unslashing of characters like '\n' to 'n', causing data corruption. Solution: The issue stems from the Cornerstone save routine, not WPML. The correct fix should be implemented in Cornerstone's translation layer. Modify the function
This modification ensures that values are properly slashed before being saved, preventing data corruption. This issue needs to be solved by the Cornerstone Team, a future update would overwrite such a patch. If this solution does not resolve your issue or seems irrelevant due to updates or different circumstances, please 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. If issues persist, we highly recommend opening a new support ticket at WPML support forum.
Problem: The client wants to prevent WPML from automatically creating strings for the Blog Title and Tagline every time the General Settings page is saved. These strings are shared across sites but should remain unique and untranslated for each site. Despite attempts to delete these strings from the WPML interface, they reappear after settings are saved. Solution: We explained that WPML does not provide a hook to prevent the registration of default WordPress strings like Blog Title and Tagline in the WPML String Translation. These strings are automatically saved once option values are updated in WordPress. The client can delete the strings at WPML > String Translation or adjust their translation as needed. Additionally, the actions triggered when these options are updated are:
For more details on WPML hooks, visit WPML Hooks Reference. Please note, we do not support custom code modifications and cannot take responsibility for issues arising from custom implementations. For our support policy, see WPML Support Policy.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also highly suggest checking related known issues at WPML Known Issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum at WPML Support Forum.
Problem: The client has a multisite WordPress installation and wants all the subsites to share the same WPML tables instead of having their own per-site prefixes. They are looking for a way to configure WPML to share the same tables across all subsites and inquire if there is a setting to force a specific prefix. Solution: We explained that sharing WPML tables across all subsites in a multisite installation is not possible with the current setup of WordPress and WPML. This would require significant custom adjustments both to WPML and WordPress itself. For such custom coding, we recommend consulting with WPML contractors who are familiar with WPML's inner workings. You can find a list of contractors here: https://wpml.org/contractors/
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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: The client is experiencing issues where changes made to certain fields are incorrectly applying to English as well, despite using the language switcher. This results in mixed-language emails being sent to English customers. Solution: We recommend translating these items using the String Translation feature of WPML. The language switcher on the page will not work for this purpose. If you're experiencing issues with String Translation, please provide more details so we can assist you further.
If this solution does not apply to your case, or if it seems outdated, we encourage you to check the related known issues and verify that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket.
Problem: The client is running a loop to clean up each subsite's WPML tables in a multisite install, specifically targeting untranslated strings and optimizing tables. They are concerned about whether deleting strings with certain statuses might affect essential translations or other database elements. Solution: We advised the client that while it is generally safe to delete entries from the
wp_icl_strings
table where the status is '0' (indicating untranslated strings), they should avoid deleting data from the
wp_icl_string_packages
table, as it contains crucial string packages necessary for page translations and other elements. We recommended using WPML's tools for safely cleaning up unused data and provided a link for further guidance: WPML Tables Documentation and Reducing Size of WPML Tables. Additionally, we emphasized the importance of performing a full backup before proceeding with any deletions and checking the system after making changes.
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 open a new support ticket at WPML Support Forum.
Problem: You are trying to remove WooCommerce's strings from the database using the 'Remove strings by domain' feature, but it has no effect. Even though you receive a success message, the strings remain in the database. Solution: 1. The 'Remove strings by domain' feature only deletes untranslated strings. If the string is translated, it won't be affected. 2. To delete strings manually, go to String Translation, select the WooCommerce text-domain, and delete the strings. You can show all results using the "Strings per page:" filter below the strings table. 3. If you need to remove strings directly from the database, use the following SQL queries:
DELETE FROM wpif_123_icl_strings WHERE context = 'woocommerce';
DELETE FROM wpif_123_icl_string_translations WHERE string_id IN (SELECT id FROM wpif_123_icl_strings WHERE context = 'woocommerce');
Please note that this custom code is a courtesy and is not officially supported by us. Before applying it to a live site, please test it in a staging environment.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also 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. For further assistance, please visit our support forum at https://wpml.org/forums/forum/english-support/.
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 issues persist, please open a new support ticket at WPML support forum.
