Bug

Problem:
Sie können das WPML Multilingual CMS nicht aktualisieren, da es einen kritischen Fehler verursacht.
Lösung:
1. Deaktivieren Sie alle Plugins.
2. Stellen Sie das Theme auf das Standard-Theme ein.
3. Installieren Sie WordPress neu auf die Version 6.9.
4. Aktualisieren Sie alle Plugins.
5. Stellen Sie das Theme wieder auf das von Elementor ein.
6. Aktivieren Sie die Plugins eins nach eins.

Wenn diese Lösung für Sie nicht relevant ist, weil sie veraltet ist oder nicht auf Ihren Fall zutrifft, empfehlen wir Ihnen, ein neues Support-Ticket zu öffnen. Wir empfehlen Ihnen auch, die bekannten Probleme zu überprüfen, die Version der dauerhaften Lösung zu verifizieren und zu bestätigen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben.

Für weitere Unterstützung besuchen Sie bitte unser Support-Forum.

Problem:
If you're experiencing issues with assigning WPML automatic translation credits to your website, where it shows zero credits despite having credits in your WPML account.
Solution:
We recommend checking the 'Translation Tools' tab under WPML > Translation Dashboard on your website. This display shows your total available credits, not just the estimate for the selected job. If the credits displayed there are correct, it indicates that the issue might be with the job selection rather than the total credits.

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 the problem persists, please open a new support ticket.

Problem:
The client has a page translated using credits, but some content, specifically a flexbox element created with full HTML in Elementor, is not translated.
Solution:
We recommend two alternative approaches to resolve this issue:
1. Recreate the grid using standard Elementor tools instead of using full HTML. This method allows Elementor to handle the grid creation, which might be more compatible with WPML.
2. Recreate the translation directly in Elementor, bypassing the WPML Translation Editor for this specific content. This can be done by following the steps outlined in the WPML documentation: Using different translation editors for different pages.
We suggest option 2 as it provides more flexibility and is likely easier for achieving specific results.

Please note that this solution might not be relevant if it's 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 the issue persists, please open a new support ticket at WPML support forum.

Problem:
If you're experiencing warnings on your website related to 'open_basedir restriction' after updating to WordPress 6.9 with WPML String Translation, it's due to the plugin sometimes requesting the folder of a translation file and receiving an empty path from WordPress. This results in PHP checking the filename in the current working directory, which is outside the allowed 'open_basedir' paths, thus triggering the warning.

Solution:
We recommend two temporary workarounds:
1. Modify the code in

wp-content/plugins/wpml-string-translation/classes/MO/Hooks/LoadTranslationFile.php

. After the line:

$defaultPathDirectory = $wp_textdomain_registry->get( $domain, $locale );

Add:

/** temporary safeguard */<br />if ( ! is_string( $defaultPathDirectory ) || '' === trim( $defaultPathDirectory ) ) {<br />    return null;<br />}

This prevents the 'open_basedir' warning by stopping the function if no real path is provided.

2. Hide the notice from your site visitors by modifying the 'wp-config.php' file as follows:

define( 'WP_DEBUG', true );<br />define( 'WP_DEBUG_LOG', true );<br />define( 'WP_DEBUG_DISPLAY', false );<br />@ini_set( 'display_errors', 0 );

This configuration logs the warnings without displaying them on the front end. For more details, visit Debugging WPML.

Please note that these are temporary solutions. Our developers are preparing an official fix to be included in a future WPML release.

If this solution does not resolve your issue or seems irrelevant due to different configurations or outdated information, 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.