Problem: You have a bilingual site in English and Arabic, with English as the default language. While creating posts in Arabic, you want the taxonomies to display in English in the backend, but they currently appear in Arabic. Solution: We currently do not support changing the backend language for taxonomy terms while maintaining different front-end translations directly through WPML settings. However, you can achieve this by implementing a custom filter in your theme's functions.php file. Here is a sample code you might consider:
This code checks if you are in the admin area and modifies the term names to their English versions for specific taxonomies. Note that you might need to define the function
1
get_english_version
to fetch the English names based on term IDs. For further customization, you may consider hiring a developer from our contractors' page.
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 issue persists, we highly recommend opening a new support ticket for personalized assistance.
Problem: Sie können die Flaggen im WPML Language Switcher nicht anklicken, um die Sprache auf Ihrer Website zu ändern. Solution: 1) Erstellen Sie zunächst ein Backup Ihrer Website. 2) Deaktivieren Sie Ihr aktuelles Theme und aktivieren Sie ein Standard-Theme, wie zum Beispiel TwentyTwenty-One. 3) Testen Sie, ob der Language Switcher mit dem Standard-Theme funktioniert. Wenn ja, liegt das Problem wahrscheinlich an spezifischen CSS-Anpassungen in Ihrem Theme. Überprüfen Sie insbesondere die CSS-Selektoren für ::active oder ::hover.
Falls diese Lösung nicht relevant ist oder veraltet erscheint, oder wenn das Problem weiterhin besteht, empfehlen wir Ihnen, ein neues Support-Ticket zu öffnen. Wir empfehlen auch, die Seite mit bekannten Problemen 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: 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:
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: The client is trying to synchronize product stock statuses across translations in a WordPress site using WPML. They imported products using WP All Import, and while the stock quantities sync correctly, the stock statuses do not. Translated products remain marked as 'In stock' even with 0 quantity. Solution: If manually updating each product is not feasible due to the large number of products, we recommend implementing a custom code solution. Here are the steps to follow: 1) Ensure you back up your site before proceeding. 2) Add the following code snippet to the end of the functions.php file of your active theme:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
add_action('admin_init', function() {
// Only run for admins
if(!current_user_can('manage_woocommerce')) {
return;
}
// Fetch all published product IDs
$product_ids= get_posts([
'post_type'=> 'product',
'post_status'=> 'publish',
'posts_per_page'=> -1,
'fields'=> 'ids',
]);
foreach($product_idsas$product_id) {
$product= wc_get_product($product_id);
if($product) {
$product->save(); // Re-saves the product, triggering related hooks
}
}
echo'<div class="notice notice-success is-dismissible"><p>All published products have been re-saved.</p></div>';
});
3) Visit any page in your WP Admin (like Dashboard or Products page) to trigger the script. 4) Once the script completes and shows a success notice, remove the snippet from your functions.php file. This solution requires some technical knowledge, and it's recommended for a web developer to implement it. Additionally, consider using the WPML Export & Import addon for similar tasks.
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 issue persists, we highly recommend opening a new support ticket at WPML 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:
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: Sie möchten WPML von Version 4.6.x auf 4.7.x aktualisieren und verwenden viele individuelle WPML-Filter und Aktionen sowie das globale
1
$sitepress
-Objekt für
1
get_current_language()
und
1
switch_lang()
. Sie fragen nach möglichen breaking changes, die Entwickler berücksichtigen sollten. Solution: Wir sind uns keiner Änderungen bewusst, die Probleme verursachen könnten. Wir empfehlen Ihnen, das Changelog von WPML zu überprüfen, um sicherzustellen, dass keine relevanten Änderungen übersehen werden. Das Changelog finden Sie hier: WPML Changelog. Außerdem sollten Sie die aktuellen Hooks überprüfen, die hier verfügbar sind: WPML Hooks Reference. Um sicherzugehen, empfehlen wir, zuerst eine Staging-Site einzurichten und das Update dort zu testen, bevor Sie es auf Ihrer Live-Site durchführen.
Falls diese Lösung veraltet ist oder nicht auf Ihr Problem zutrifft, empfehlen wir Ihnen, ein neues Support-Ticket zu öffnen. Überprüfen Sie auch die bekannten Probleme unter https://wpml.org/known-issues/, bestätigen Sie die Version der dauerhaften Lösung und stellen Sie sicher, dass Sie die neuesten Versionen von Themes und Plugins installiert haben. Für weitere Unterstützung besuchen Sie bitte unser Support-Forum: WPML Support-Forum.
Problem: Vous avez créé un thème WP avec un header, un footer, et un composant CTA, tous traduits dans deux langues supplémentaires. Ces éléments s'affichent correctement traduits sur toutes les pages, sauf pour les single posts, où ils restent en français malgré la configuration pour afficher les traductions si elles existent. Solution: 1. Assurez-vous que vos modèles sont correctement traduits et assignés. Allez dans Apparence > Éditeur de site (Site Editor). Cliquez sur Modèles > Single. En haut à droite, cliquez sur l’icône de langue et vérifiez qu'une version existe pour chaque langue. Si ce n’est pas le cas, créez une version traduite du modèle via l’éditeur. Dans la version traduite, réinsérez manuellement les éléments globaux traduits (Header, Footer, CTA). 2. Si vous chargez des éléments via
Si cette solution ne résout pas votre problème ou semble obsolète, nous vous recommandons de vérifier les problèmes connus, de vérifier la version du correctif permanent et de confirmer que vous avez installé les dernières versions des thèmes et plugins. Si le problème persiste, n'hésitez pas à ouvrir un nouveau ticket de support sur notre forum de support.
Problem: You are trying to display a list of posts using WP_Query in the site's current language, but the query returns posts in the default language. Solution: To ensure that WP_Query returns posts in the current language of the site, you need to modify your query arguments. Specifically, add
1
"suppress_filters=0"
to your arguments in the WP_Query or get_posts function. This change will allow WP_Query to filter the posts according to the current language. For more detailed guidance on achieving WPML compatibility with your themes and plugins, please visit: WPML Theme and Plugin Compatibility
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. Additionally, we highly recommend checking related known issues at WPML 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 at WPML Support Forum.
Problem: You are using custom code to automatically duplicate new posts into another language on your site. However, when updating the translation of a post and then updating the original post again, the translation gets overwritten unless 'translate independently' is manually selected. Solution: When duplicating a post, the duplicated posts contain a meta_key entry "_icl_lang_duplicate_of" in the wp_postmeta table. To prevent translations from being overwritten, you can remove this meta_key entry. This can be done either manually or by writing custom code. For more information on how to implement this, you can refer to the WPML Coding API at https://wpml.org/documentation/support/wpml-coding-api/ and the WPML Hooks Reference at https://wpml.org/documentation/support/wpml-coding-api/wpml-hooks-reference/.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also 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. For further assistance, please visit our support forum at https://wpml.org/forums/forum/english-support/.
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:
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.
Utilizziamo i cookie per ottimizzare il nostro sito web e i nostri servizi.
Il tuo consenso ci permette di elaborare dati come il comportamento di navigazione.
Il mancato consenso potrebbe compromettere alcune funzionalità.
Funzionale
Sempre attivo
Necessario affinché il nostro sito web funzioni e comunichi correttamente.
Preferenze
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistiche
Li utilizziamo per analizzare le statistiche del nostro sito.
Le informazioni raccolte sono completamente anonime. L'archiviazione tecnica o l'accesso che viene utilizzato esclusivamente per scopi statistici anonimi. Senza un mandato, la conformità volontaria da parte del tuo fornitore di servizi Internet o altri registri di terzi, le informazioni memorizzate o recuperate per questo scopo da sole non possono generalmente essere utilizzate per identificarti.
Marketing
Questi cookie tracciano la tua navigazione per fornirti annunci pubblicitari pertinenti.
