Known issue

Problem:
The client is experiencing UI issues on their website pages when the WPML string translation plugin is enabled, specifically in the Indonesian language.
Solution:
We recommended enabling WP Debug to gather more detailed error logs. The steps include modifying the 'wp-config.php' file to enable WP_DEBUG, WP_DEBUG_LOG, and SCRIPT_DEBUG while disabling WP_DEBUG_DISPLAY. This setup helps in logging errors without displaying them on the site. For detailed instructions, visit WPML Debugging Documentation and WordPress Codex on Debugging.
Additionally, to address potential issues with page updates not reflecting in translated versions, we suggested:
1. Open the default language page in Edit mode.
2. Make a minor change (e.g., add a space or + sign in the page title).
3. Save the page.
4. Remove the change made in step 2.
5. Update the page again.
6. Attempt to open the translated page in the WPML Translation Editor to check if it loads correctly.
If these steps do not resolve the issue, we advised opening a new ticket for further investigation.

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 problem persists, please open a new support ticket at WPML Support Forum for personalized assistance.

Problema:
Quando un cliente pubblica un Post o una Discussione nel forum, viene automaticamente creata una notifica nell'activity feed. Il cliente desidera che siano visibili solo le notifiche di una lingua selezionata. Nonostante il comportamento di default dovesse permettere il filtraggio delle notifiche per lingua, una regressione nella versione 2.8.80 di BuddyBoss Platform ha interrotto questa funzionalità. Tuttavia, il cliente utilizza una versione precedente di BuddyBoss, quindi teoricamente il filtraggio per lingua dovrebbe funzionare.
Soluzione:
Abbiamo confermato che si tratta di un bug noto. Abbiamo già contattato BuddyBoss per una soluzione definitiva. Poiché il fix deve essere implementato da BuddyBoss, consigliamo di aprire un ticket di supporto con loro, dato che le richieste dei clienti hanno spesso priorità maggiore.

Se questa soluzione si rivela irrilevante, perché potrebbe essere datata o non applicabile al tuo caso, ti invitiamo a verificare i problemi noti correlati, a controllare la versione del fix permanente e a confermare che hai installato le ultime versioni dei temi e dei plugin. Se il problema persiste, ti raccomandiamo di aprire un nuovo ticket di supporto con noi qui.

Problem:
If you're encountering a PHP Fatal Error when trying to access the WPML admin page, it might be due to a conflict with the Visual Composer PRO plugin, which registers a custom post type without proper labels.
Solution:
First, ensure you back up your database and website. We recommend trying one of the following workarounds:
Workaround 1 (recommended): Add the following code to your theme’s functions.php file:

add_filter( 'wpml_post_type_dto_filter', function ( $postTypeObject ) {<br />    if ( is_object( $postTypeObject ) ) {<br />        $default = $postTypeObject->name ?? '';<br />        if ( ! isset( $postTypeObject->labels ) || ! is_object( $postTypeObject->labels ) ) {<br />            $postTypeObject->labels = new stdClass();<br />        }<br />        if ( empty( $postTypeObject->name ) ) {<br />            $postTypeObject->name = $default;<br />        }<br />        if ( empty( $postTypeObject->labels->name ) ) {<br />            $postTypeObject->labels->name = $default;<br />        }<br />        if ( empty( $postTypeObject->labels->singular_name ) ) {<br />            $postTypeObject->labels->singular_name = $default;<br />        }<br />    }<br />    return $postTypeObject;<br />} );

Workaround 2: Manually edit the plugin file at /wp-content/uploads/visualcomposer-assets/addons/themeEditor/themeEditor/PostTypeController.php. Replace the existing register_post_type function with:

protected function registerPostType()<br />{<br />    if (!isset($this->postNamePlural)){<br />        $this->postNamePlural = $this->postNameSlug;<br />    }<br />    register_post_type(<br />}

Note that this change might be lost if the plugin updates. We also recommend reporting this issue to the Visual Composer PRO team for a permanent fix.

If this solution does not apply to your case, or if it seems outdated, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket with us for further assistance.

Problem:
You are trying to edit the 'Theme and Plugins Localization' section on your WordPress site and encountered an E_ERROR in wpml-string-translation plugin due to an unknown format specifier 't'.
Solution:
This issue is recognized as a known problem. Although the specific plugin mentioned in the errata might not be in use, another active plugin could be registering a text domain improperly, leading to this error. For more information and potential solutions, please refer to the errata page: https://wpml.org/errata/flux-checkout-fatal-error-uncaught-valueerror-unknown-format-specifier-t/.

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 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: WPML Support Forum.

Problem:
Вы пытаетесь автоматически создать sitemap для разных языков на вашем сайте, используя WPML SEO, Yoast SEO, Yoast SEO Premium и Yoast SEO: WooCommerce. Однако, не удается автоматически сгенерировать sitemap на немецком языке.
Solution:
Если вы используете настройку URL «Разные языки в каталогах» в WPML → Languages, sitemap.xml будет генерироваться один для всех языков. Это ожидаемое поведение. Для получения дополнительной информации, пожалуйста, посетите ссылку.

Если данное решение не актуально для вашей ситуации или вышло из строя, рекомендуем открыть новый тикет поддержки. Также настоятельно рекомендуем проверить известные проблемы, убедиться в версии постоянного исправления и подтвердить, что у вас установлены последние версии тем и плагинов.