Problem: The client is encountering PHP deprecation warnings related to the creation of dynamic properties in WooCommerce when editing products. These warnings appear specifically when the WPML plugins are activated.
Solution: If you're experiencing similar PHP deprecation warnings, we recommend the following steps: 1. Ensure you have a backup of your site. 2. Temporarily disable all plugins except for WPML and WooCommerce, and switch to a default WordPress theme to check if the issue persists. 3. If the warnings disappear after deactivating other plugins and themes, it indicates a possible conflict with other installed extensions or the theme. 4. The issue has been identified as related to PHP 8.3+ versions, and a fix will be included in upcoming releases of the WPML plugins, specifically versions beyond 5.5.2.2.
Please note that these warnings are not indicative of functional problems with your site but are meant to inform about deprecated practices. If this solution does not apply or is outdated, or if the problem persists, 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 needed, do not hesitate to open a new support ticket at WPML support forum for further assistance.
Problem: After switching from 'WPML Multilingual & Multicurrency for WooCommerce' to 'CURCY - WooCommerce Multi Currency Premium', the client encountered issues with the secondary 'shop' page layout and the language switcher link not updating to reflect the new 'store' slug. Solution: The client resolved the issue by reinstalling the 'WPML Multilingual & Multicurrency for WooCommerce' plugin. This action corrected the language switcher link, syncing it with the updated page slug.
If you're experiencing similar issues, we recommend reinstalling the WPML plugin and verifying that all settings are correctly configured. Additionally, if this solution does not apply or seems outdated, 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 problems persist, feel free to open a new support ticket at WPML support forum for further assistance.
Problem: The client is experiencing an error with the [esi wpml_language_selector_widget] in the Bricks editor for the secondary language, and issues with currency not updating correctly in the cart when using ESI blocks. Solution: For the Bricks editor issue, we recommend wrapping the shortcode in a conditional to differentiate between the Bricks editor and the frontend. Use the following code:
Remember, WPML does not control how LiteSpeed parses or caches ESI blocks, and issues might arise if ESI is not enabled correctly or if the theme or builder does not support ESI context.
If these solutions do not resolve your issues or seem outdated, please check related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket if problems persist.
Problem: After enabling opcache manager and LiteSpeed Cache plugins on the client's website, the language flags in the WPML language switcher disappeared and were replaced by the text "english german". Solution: We recommend flushing the cache memory and then double-checking if the issue has resolved. If you inspect the HTML, you should be able to see the flag files 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. Should you need further assistance, please do not hesitate to open a new support ticket or visit our support forum at WPML Support Forum.
