Known issue

Problem:
You added languages to your pages and included links to the translated pages in your blog posts. However, when you click on these links, they redirect to the original language instead of the translation page.
Solution:
We recommend checking the following documentation on a known issue with Betheme where internal links in translations point to the default language: https://wpml.org/errata/betheme-internal-links-in-translations-point-to-default-language/
Your current version of Betheme is 27.1.5.1, and this issue was resolved in version 27.5.10. Please update your theme to the latest version by following the changelog link here: https://support.muffingroup.com/changelog/
After updating, verify if the issue with the translation links is resolved.

If this solution does not apply to your case, or if it is 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 problem persists, please open a new support ticket at WPML support forum.

Problem:
You are trying to translate a website using Gutenberg blocks with Carbon Fields, but encounter an error when editing the page from the admin panel, and no blocks are displayed on the frontend.
Solution:
We have identified that the issue might be related to the handling of complex or serialized fields by plugins similar to Carbon Fields. We recommend checking our errata on handling custom fields with complex keys stored as serialized arrays in WPML. You can find the temporary workaround here: Custom Fields with Complex Keys Are Stored as Serialized Arrays in WPML. Please try this solution and see if it resolves the issue.

If this solution does not apply to your case, or if it seems outdated, we highly recommend opening a new support ticket. Also, 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. For further assistance, you can contact us directly through the WPML support forum.

Problema:
Dopo gli aggiornamenti automatici di WordPress (6.7.2) e WPML (4.7.0), il sito è crashato. Il problema si verifica solo quando WPML è attivo.
Soluzione:
Il problema che stai riscontrando è noto e documentato qui: https://wpml.org/errata/fatal-error-updating-wpml-4-7/. Ti consigliamo di seguire le istruzioni fornite in quella pagina per risolvere il problema.

Se la soluzione proposta non risolve il problema o se le informazioni sono obsolete, ti invitiamo a verificare la versione della correzione permanente e a confermare che hai installato le ultime versioni dei temi e dei plugin. Inoltre, ti consigliamo di consultare la pagina dei problemi noti di WPML qui: https://wpml.org/known-issues/. Se il problema persiste, ti invitiamo a aprire un nuovo ticket di supporto.

Per ulteriore assistenza, visita il nostro forum di supporto: https://wpml.org/forums/forum/italian-support/.

Problem:
You are experiencing issues with non-Latin slugs for custom post types such as news, events, and resources on your website after updating to WordPress 7.62. These pages stop functioning, and rolling back to a previous version or changing slugs to Latin characters in WPML settings > Post Types Translation resolves the issue.
Solution:
We recommend checking the following WPML errata page for a known issue related to WordPress 6.7, which persists in later versions including 7.62: https://wpml.org/errata/wordpress-6-7-you-attempted-to-edit-an-item-that-doesnt-exist-with-translated-post-type-slugs/. This problem occurs even without WPML if you use non-Latin character slugs for your Custom Post Types.

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 with us for further assistance.

Problem:
The client is experiencing a PHP error related to WooCommerce, indicating that the function

_load_textdomain_just_in_time

was called incorrectly, suggesting that translation loading for the WooCommerce domain was triggered too early.

Solution:
We recommend updating all plugins to their latest versions, as this issue has been addressed in recent updates of WooCommerce, WPML, and other popular plugins. Before updating, please ensure to take a full backup of your website and database. It is highly advised to perform these updates on a staging or development site first to avoid compromising your live website.

If you encounter a fatal error during the update, try disabling all other plugins except for WPML and WooCommerce to check if the error persists. If the issue continues, please provide us with more details, and we will assist you further.

If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable 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.