Please note that this solution might be irrelevant due to changes in the theme or our code. 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: You are trying to translate a dynamically populated ACF field using the ACFML plugin, but the field is not translating or appearing in the other language. Solution: 1. Verify that your ACF Select Field has Choices set. If no Choices are declared, WPML cannot translate them using the WPML Translation Editor because the values are set through custom code. 2. To translate such fields, use the WPML String Translation. You can register the strings for translation using a GetText call in PHP or by utilizing the WPML hook: https://wpml.org/wpml-hook/wpml_register_single_string/ 3. For additional guidance on translating themes and plugins you've created, refer to: https://wpml.org/documentation/support/translating-the-theme-you-created/
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: WPML Support Forum.
Problem: You need custom behavior that falls outside the standard options of WPML. Solution: Since this involves custom work which is not covered by our standard support, we recommend contacting the theme author. They might be able to resolve the issue by using the code similar to what is used for WooCommerce stock.
Please note that this solution might be irrelevant 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: The client wants to translate custom post type (CPT) slugs without using WPML's String Translation, aiming for a cleaner approach while maintaining language-specific URLs (e.g., English: example.com/en/products/, German: example.com/produkte/). They are experiencing issues with 404 errors and incorrect language detection in requests. Solution: We recommend using WPML's String Translation for translating CPT slugs as it is a mandatory plugin for such functionality. Ensure that the 'has_archive' is set to true in your code, as shown below:
'has_archive' => true,
WPML supports custom slug translation when the custom type is registered but does not support custom permalink structures. For more details, please refer to our documentation on translating slugs for custom post type archives. If you require a custom solution, we suggest using the services of WPML contractors, which can be found here: WPML contractors.
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: You are trying to translate all link targets on your website using the Divi side by side buttons module, but the links are still pointing to English pages on the French version of the website. Despite re-translating the page, the side by side buttons on the home page and articulated arms page still link to English pages. Solution: We found that the dual buttons module needed to be registered for translation. We registered it by adding the following code to WPML-> Settings-> Custom XML tab:
After adding this code, update the home page in the default language and update its translation using the translation editor to translate the URLs in the editor. Check the French home page to see if the buttons now correctly link to the French pages.
If this solution does not resolve your issue or seems outdated, we 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 at WPML support forum.
Problem: You are using WPML to manage a multilingual site and need to set up permissions so that translators can only view the original language content and edit their assigned language translations. You are looking for a way to make the original content 'view-only' and inquire about any available WPML filters or hooks to implement these restrictions. Solution: The client has managed to achieve it using custom code on his own. Please note that the solution might be 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.
Problem: The client is attempting to disable the WPML permalink changes on a specific page using custom code, but WPML is blocking these changes. Solution: We recommend using the
wpml_permalink
hook to specify a language code. Setting this argument to the site's default language code should help achieve the desired functionality of disabling WPML permalink changes on the specific page without affecting the entire site. For more details on how to use this hook, please visit WPML permalink hook documentation.
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: You are trying to display all posts in all languages on a US page using WPML, but the default WPML settings do not support this functionality. Solution: We recommend adjusting your query to bypass WPML's default language filtering. Here's how you can modify your WP_Query:
// Perform your WP_Query with suppress_filters set to true
$query = new WP_Query( array(
'post_type' => 'post', // Or your custom post type
'posts_per_page' => -1, // Show all posts
'suppress_filters' => true, // Disable WPML language filtering
) );
// Apply the 'the_posts' filter manually to get posts in all languages
if ( $query->have_posts() ) {
$all_posts = apply_filters_ref_array( 'the_posts', array( $query->posts, $query ) );
// Now $all_posts will contain all posts from all languages
$query->posts = $all_posts;
}
// Loop through and display the posts
if ( $query->have_posts() ) {
while ( $query->have_posts() ) {
$query->the_post();
// Your loop code (e.g., the_title(), the_content(), etc.)
}
}
// Don't forget to reset post data after the loop
wp_reset_postdata();
Please note that this solution is a custom workaround and was not extensively tested. If this solution does not work or seems outdated, or if it does not apply 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You want to create an overview on your website using WPML to see the original page and all connected pages with their translated slugs, organized in columns. Solution: We recommend developing a new functionality with custom code. Although creating custom code solutions falls outside our support scope, you can explore our hooks that might help you achieve this. Please check the WPML Hooks Reference for potential solutions.
If this solution does not apply to your case, or if it 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. Should you need further assistance, please do not hesitate to open a new support ticket or visit our support forum at WPML Support Forum.
The client is experiencing an issue where editing a job post in one language results in updates being saved across all language versions, leading to prolonged save times. They seeks a solution to save the job in the original language without automatically updating all the language versions immediately.
Solution:
We informed that due to the nature of WPML and its handling of duplicated posts, any updates to the original post would automatically sync with the duplicates. To manage this, the client can manually set the duplicates to 'Translate Independently' by clicking the Translate Independently button on the duplicate post in the secondary language. This action prevents automatic updates to the translated versions when the original is edited. Later, if needed, the translated versions can be updated manually by selecting the Overwrite with - option.
For detailed steps, please refer to the following documentation:
If this solution does not apply or is outdated, we 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.