Custom Work

Problem:
Der Kunde kann den Übersetzungseditor nicht verwenden, da er sich beim Laden aufhängt. Es wird ein Fehler angezeigt: "ATE Server Communication: Unable to authenticate". Der Fehler wurde durch eine spezifische Anpassung in der functions.php des Themes verursacht, die das eingebaute jQuery von WordPress deregistriert und es im Footer neu registriert, wodurch jQuery im WP-Admin-Bereich zu spät oder gar nicht geladen wird.
Solution:
Wir empfehlen, das Theme vorübergehend auf ein Standard-Theme zu wechseln, um zu überprüfen, ob das Problem weiterhin besteht. Wenn der Übersetzungseditor unter dem Standard-Theme funktioniert, liegt das Problem wahrscheinlich an der spezifischen Anpassung in der functions.php Ihres aktuellen Themes. Entfernen Sie den Code, der jQuery deregistriert und neu registriert, oder kommentieren Sie ihn aus:

function permalink_trailingslashit($link) {return trailingslashit($link);}<br />add_filter('home_url', 'permalink_trailingslashit');

Diese Lösung könnte veraltet sein oder auf Ihren Fall nicht zutreffen. Wir empfehlen Ihnen, 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. Sollte das Problem weiterhin bestehen, zögern Sie nicht, ein neues Support-Ticket zu eröffnen. Besuchen Sie dazu unser Support-Forum.

Problem:
You are managing multilingual options on your website with English as the default language and French as the secondary. When updating an option with the same value as the default language, the French option in the database becomes empty. This occurs due to the behavior in WPML's class-wpml-multilingual-options.php.
Solution:
This behavior is intentional for optimization in WPML. If the translated option value is identical to the original language's value, WPML deletes the translated option to avoid duplication in the database. This means that if the values are the same, WPML will not store them separately and will fall back to the original value. If you need to force the translation of admin strings or save options in different languages, consider using the following hooks:

• wpml_st_force_translate_admin_options
• wpml_multilingual_options

If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. Also, 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, please visit our support forum.

Problem:
Generally it is expected that a Custom Post Type Archive will not be accessible if no posts have been translated yet. In this case the client tried to create a custom language switcher to solve the issue.
Solution:
For custom language switchers, note that you can use the hook wpml_active_languages to manually generate the correct URLs for your language switcher. Here's an example, but take note that you need to adapt the code to your needs. For example "post-type-name" "slug-name" would be the slug that you would like to translate and this hook will make it translatable:

function force_cpt_archive_language_urls($post_type = 'post-type-name') {
    $languages = apply_filters( 'wpml_active_languages', NULL, array(
        'skip_missing' => 0
    ) );
 
    if ( !empty($languages) ) {
        foreach ($languages as $code => &$lang) {
            // Manually generate the archive link for the CPT in this language
            $translated_slug = apply_filters( 'wpml_translate_single_string', $post_type, 'slug-name', "URL slug: $post_type", $code );
            $lang['url'] = home_url( '/' . $code . '/' . $translated_slug . '/' );
        }
    }
 
    return $languages;
}

Please note, that this is a custom solution and might not have been tested in every setup. It's beyond WPML's built-in functionality, so our support doesn’t cover debugging custom code. 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.