Problem: You are trying to save data on an ACF option page in various languages using ACFML, with fields set as 'copy' to maintain the same values across all languages. While the backend shows values correctly copied and locked, the frontend still displays values from the main language (Italian). Even after updating the value in the main language, you need to manually update it in each secondary language to reflect changes on the frontend. Solution: The behavior you're experiencing is expected when using ACF fields with the copy translation preference. To apply these values to the secondary languages on the frontend, you must re-save the options page in those languages. This process is necessary to ensure consistency across languages as currently implemented by WPML and ACFML. For more details, you can refer to our documentation here: Translating the ACF Options Page Custom Fields with WPML. If this manual update process is cumbersome, we can submit a feature request to explore the possibility of automatically copying the options page values into the secondary languages upon saving the default language options page. Please let us know if you would like us to proceed with this request.
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.
Problem: The client is experiencing issues with the translation engine in WPML, where it deletes progress and fails to maintain colored highlights for HTML attributes. Additionally, the cross icon does not clear these highlights, and placeholder tags appear in the source text without being able to be added to the translated field. The engine also refuses to mark the translation as complete, and formatting must be applied to save the translation. Solution: We recommend applying the same marker to your translated content as in the original to ensure it can be saved. If you need to remove and re-add markers to different parts of a sentence, this is expected behavior in the translation process. For issues with different formatting across languages, you can use CSS to apply different styles or assign markers to a dot and hide them in the second language. For more details, please see our forum post: https://wpml.org/forums/topic/issues-in-translation-workflow/#post-13119257
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client needed a way to display the currency code instead of the symbol across various sections of their WooCommerce site, including product pages, store, cart, and checkout.
Solution: We recommended a temporary solution to display the currency code everywhere on the site. Here are the steps we suggested: 1. Take a backup of your site and database. 2. Edit your active theme's functions.php file. 3. Add the following code at the end of the file:
Additionally, if you want to edit the currency switcher: 1. Go to WooCommerce -> WooCommerce Multilingual & Multicurrency -> Multicurrency. 2. Scroll down to "Product page Currency Switcher" section. 3. Edit the currency switcher and remove "%symbol%" from "Template for currency switcher" field. 4. Save the changes.
For more details on managing multi-currency in WooCommerce, please see our documentation.
If this solution does not apply to your case, or if it becomes outdated, we highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. Should you need further assistance, please open a new support ticket.
Problem: Sie möchten wissen, wann es möglich sein wird, Inhalte, die nicht in der Standardsprache der Website erstellt wurden, automatisch zu übersetzen. Solution: Sie können Inhalte, die nicht in der Standardsprache erstellt wurden, direkt im Übersetzungseditor automatisch übersetzen. Diese Inhalte werden in Ihre oder die Warteschlange Ihres Übersetzers aufgenommen. Sobald sie dort sind, kann der Übersetzer darauf zugreifen, sie öffnen und das ATE-Tool zur Unterstützung bei der Übersetzung verwenden. Für zusätzlichen Komfort können Sie die Inhalte auch automatisch mithilfe der entsprechenden Schaltfläche übersetzen. Weitere Informationen finden Sie in unserer Dokumentation: Übersetzen Ihrer Inhalte. Leider gibt es derzeit keine Pläne, zusätzliche Funktionen oder Änderungen an diesem Prozess umzusetzen.
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 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.
Problem: The client requested two enhancements for the WPML plugin to optimize translation time. First, an automatic fill-in feature in the media gallery of the post being translated, similar to a find and replace function, to rename multiple media titles at once. Second, a feature to mark all text boxes as 'completed' in manual translation mode before publishing, to facilitate bulk actions. Solution: We have acknowledged the client's suggestions and have forwarded them to our development team for consideration in future updates.
Please note that the solution provided might be irrelevant if it is 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: The client needs to automatically create a duplicate of each Spanish (Spain) page/post for Spanish (Mexico) on their multilingual site, but only for certain pages. Solution: We recommend using the WPML hook for duplicating posts automatically. First, ensure you back up your site and database. You can implement the following code in your theme's functions.php file or a custom plugin:
This script checks if a post is a new or updated Spanish post and duplicates it for Spanish (Mexico) if no translation exists. Modify the condition inside the function if you want to limit this behavior to specific post types. For more details on the hook used, visit WPML admin make post duplicates.
If this solution does not apply to your case, or if it seems outdated, please check the related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If further assistance is needed, we encourage you to open a new support ticket.
Problem: The client wants the language switcher in the nav bar to display the name of the other language instead of the active language. The site uses Gutenberg blocks, and the switcher currently shows only two letters representing the active language (German), but the client wants it to display the name of the other language (French). Solution: We recommend two methods to achieve this: Method 1: Hide the current language using CSS 1. Edit the Language Switcher block. 2. Set the "Layout" to list. 3. Add the following CSS in the custom CSS section of the theme:
Method 2: Add language switcher using shortcode 1. Go to the WPML >> Languages page. 2. Enable the Custom Language Switcher. 3. Replace the language switcher block with a shortcode block and use the following shortcode:
If these solutions do not resolve your issue or if they seem 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: You are using WP-CLI to list all media IDs in the trash across all languages but the command only returns media IDs for the main language. Solution: We have identified two potential workarounds to include media IDs from all languages: 1) Use the WP-CLI parameter
--suppress_filters=true
which allows the command to work across all languages. 2) Use the parameter
--url="https://yourwebsite.com/en"
to force WP-CLI to work in the language based on the URL.
Additionally, our 2nd Tier Support suggests modifying the code in
function with the following code to include a condition that checks for the 'lang' parameter in the query:
public function posts_where_filter( $where, $query ) {
if ( $query === null || $this->where_filter_active( $query ) === false ) {
return $where;
}
$requested_id = isset( $_REQUEST['attachment_id'] ) && $_REQUEST['attachment_id'] ? $_REQUEST['attachment_id'] : false;
$requested_id = isset( $_REQUEST['post_id'] ) && $_REQUEST['post_id'] ? $_REQUEST['post_id'] : $requested_id;
$requested_id = (int) $requested_id;
$default_language = $this->sitepress->get_default_language();
$post_language = $this->post_translations->get_element_lang_code( $requested_id );
if (isset($query->query["lang"])) {
$post_language = $query->query["lang"];
$requested_id = "1"; //hack needed because then $current_language will not get the $post_language, but will call for get_current_language
}
$current_language = $requested_id && $post_language ? $post_language : $this->sitepress->get_current_language();
$condition = $current_language === 'all' ? $this->all_langs_where() : $this->specific_lang_where( $current_language, $default_language );
$where .= $condition;
return $where;
}
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 these solutions do not resolve your issue, please open a new support ticket at WPML support forum.
Problem: You have created a custom post type (CPT) with the slug 'event' using the ACF Pro plugin and defined a custom archive slug 'events'. You have translated the base default slug 'event' to 'événement' in French via WPML > Settings > Post Types Translation, but you are unable to find where to translate the archive slug. Solution: Currently, WPML does not support the translation of custom slugs set in the
has_archive
option for custom post types. You can read more about this limitation here. We recommend enabling the archive option and leaving the slug field empty for custom post types created with ACF. This approach uses the default slug, and when you switch languages, the translated slug set in "WPML > Settings > Post Type Translation" will display.
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking related known issues at known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: The client needed a way to customize the ALT text for flag images in the WPML language switcher to improve accessibility and comply with WCAG 1.1.1, without modifying WPML core files. Solution: We advised the client that currently, the best approach to achieve the desired ALT text customization is to follow the workaround provided in our errata, which involves modifying the 'class-wpml-ls-model-build.php' file.
Unfortunately, there are no suitable hooks or filters available for this customization, and implementing custom code would be complex. We also informed the client that there is no ETA for a permanent fix but have taken their feedback as a feature request. We recommended trying the workaround after ensuring a site backup.
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 this does not resolve your issue, please open a new support ticket at WPML support forum.
