Problem: The client is experiencing unresolved issues with their WordPress site using WPML, specifically related to 404 errors when translating product brand slugs. Solution: If you're experiencing similar issues, we recommend trying the following workaround: Navigate to Settings > Permalinks in your WordPress dashboard, and manually set a static value for the brand slug. Initially, 'brand' will appear as a placeholder slug. To use 'brand' as a manually set slug, you must edit the field, type the value, and save it. This solution is based on a known issue which can be further explored here: Translating Product Brand Slug Can Lead to 404s.
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 issue persists, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is experiencing an issue where email notifications sent from their multilingual e-commerce sites viviscal.bg and viviscal-store.com are displaying in multiple languages instead of just the language in which the order was made. This problem is linked to the YAY Mail plugin's handling of languages. Solution: We recommend updating the YAY Mail plugin's code to ensure that emails are sent in the correct language. Specifically, modify the
get_site_language
function in the WPMLIntegration.php file. Here's the step-by-step guide:
Backup the original WPMLIntegration.php file located in /wp-content/plugins/yaymail-pro/includes/Integrations/Translations/.
public static function get_site_language( $order ) {
global $sitepress;
// Use default language as safe fallback
$language = apply_filters( 'wpml_default_language', null );
if ( null !== $order || isset( $GLOBALS['yaymail_set_order'] ) ) {
$order_data = ( null !== $order ) ? $order : $GLOBALS['yaymail_set_order'];
$order_language = $order_data->get_meta( 'wpml_language', true );
if ( ! empty( $order_language ) ) {
$language = $order_language;
}
}
do_action( 'wpml_switch_language', $language );
return $language;
}
After updating the code, test the email notifications to ensure they are now sent in the correct language.
If this solution does not resolve your issue or seems irrelevant due to updates or different configurations, 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: Sie können die Shortcodes von TablePress nicht in der String Translation oder im Advanced Translation Editor finden oder übersetzen. Dies liegt daran, dass TablePress Tabellen in einer eigenen Custom-Struktur erzeugt, die nicht kompatibel mit der normalen String Translation ist. Solution: Die bisherige Methode, Shortcodes über die String Translation zu übersetzen, war nicht korrekt, da es sich um _postmeta-Inhalte handelt. Stattdessen sollten Sie Inhalte von TablePress aus der _options-Tabelle über
admin_texts_tablepress_tables
registrieren. Sie haben folgende Möglichkeiten: 1) Nutzen Sie den Workaround, um die Inhalte zu registrieren. 2) Legen Sie, wie von den Autoren beschrieben, separate Tabellen an. 3) Ziehen Sie alternative Plugins zu TablePress in Betracht. Eine Übersicht finden Sie hier: TablePress-Tables are not translating
Falls 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 eröffnen. Wir empfehlen Ihnen auch, die Seite mit bekannten Problemen (https://wpml.org/known-issues/) 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.
Problem: You are trying to import products in two languages (EN and DE) using the built-in importer. Initially, both language versions display correctly. However, after updating the EN product, the DE product attributes like size and color are no longer displayed in the webshop. Solution: We have identified that this behavior is expected due to the limitations in WPML's handling of attribute translations. In WPML, attribute names themselves cannot be translated, only their labels can be. These labels are what you see on the frontend, provided by the theme. Unfortunately, the attribute names included in the export CSV file are not translatable. If you're experiencing this issue, we recommend checking the known issues page and verifying that you have the latest versions of themes and plugins installed.
If this solution does not apply to your case, or if it seems outdated, please do not hesitate to open a new support ticket. We highly recommend visiting the WPML support forum for further assistance.