Problem: The client is experiencing a discrepancy between string translation and theme translation, suspecting it might be related to previously active LiteSpeed caching. Solution: We recommend following the previously suggested steps despite the concerns about LiteSpeed caching, as we have not found any direct connection between LiteSpeed caching and the issue at hand. It is crucial to take a full backup of the site (both files and database) before proceeding to ensure that you can revert to the original state if necessary. After applying the steps, if any unexpected issues arise, we advise you to contact us for further troubleshooting.
Please note that this solution might be outdated or not applicable to your specific 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 the issue persists, please open a new support ticket at WPML support forum.
Problem: The client is trying to auto-translate the product availability date in the Google for WooCommerce settings on their site. They want the same value copied to the Google for WooCommerce settings on product pages in other languages without manually entering them each time. Solution: First, ensure that you are using the WordPress Editor to create translations, as editing translations directly using the WP Editor is not recommended. You can set the WordPress Editor as your translation tool by following this guide: Using different translation editors for different pages.
Next, to auto-copy the availability date field and possibly other fields to other languages when editing and saving the product page in the default language, navigate to WPML > Settings > Custom Fields Translation. Find the specific field and set it to "Copy once" if you want the content to be copied over once the translation is created and remain as is. Alternatively, you can set it to "Copy" if you want the translation to always stay in sync with the original. More details on these options can be found here: Translating custom fields.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client needed to add custom languages for Belgium, Austria, and Switzerland, including details like code, default locale, and hreflang. They also inquired about sources for custom flags and the functionality of the language mapping column in WPML. Solution: 1) The choice of language code, default locale, and hreflang for custom languages is up to the client. We recommend consulting an SEO agency or a list of WordPress locale codes, such as Complete List of WordPress Locale Codes. 2) WPML does not provide an image database for custom flags; clients should use their own sources. 3) Language mapping is useful for automatic translations. It allows mapping a custom language to an existing language that supports automatic translation. This feature is available if the client is using the Advanced Translation Editor or Translate Everything mode in WPML. 4) For translating content, clients can manually translate or use the bulk duplication feature. More information on this can be found here: How to Duplicate Pages and Posts in Bulk.
If this solution does not resolve your issue or 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 further assistance is needed, please open a new support ticket.
