Problem: The client is unsure about the impact and differences between using the WordPress Editor and the WPML Translation Editor for translating pages, specifically regarding the accuracy or functionality of translated pages. Additionally, the client seeks guidance on translating schema markup content like FAQ schema. Solution: We recommend using the WordPress Editor for cases where script or code translation is involved, as the WPML Translation Editor cannot handle these elements. Using the WordPress Editor allows you to manually add and adjust translated content similarly to how you manage content in the default language. This method does not affect the accuracy or functionality of your page. However, if you switch back to the WPML Translation Editor in the future, any changes made manually will be overwritten. If you have not already created an Italian page, you can start with a blank page or use our duplication method, which copies content from the default language for manual adjustments. For more details, please visit: Using Different Translation Editors for Different Pages.
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. If further assistance is needed, please open a new support ticket at WPML Support Forum.
Problem: The client is trying to add FAQ schema in JSON-LD format to their web pages using an HTML block and wants to translate the 'name' (Question) and 'text' (Answer) values using WPML's Advanced Translation Editor (ATE). However, the content injected via an HTML block doesn't appear as translatable fields in ATE by default. Solution: We explained that the Advanced Translation Editor is not designed for handling script tags, which are excluded and copied over to the translation unchanged. This can lead to issues when trying to translate content within script tags directly in ATE. As an alternative, we suggested switching to the Classic Translation Editor, which allows the translation of HTML, CSS, and JavaScript, if the client does not require features like automatic translation or glossary provided by ATE. For more detailed guidance, we recommended checking out the documentation on choosing your translation editor at https://wpml.org/documentation/translating-your-contents/using-the-translation-editor/#choosing-your-translation-editor and using different translation editors for different pages at https://wpml.org/documentation/translating-your-contents/using-different-translation-editors-for-different-pages/.
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 at https://wpml.org/forums/forum/english-support/.
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: The client needed guidance on managing the WPML license for a new testing environment that will eventually become the production site. Solution: We recommend registering the new instance with a new key as a development site. Once development is complete and you are ready to transition this to a production environment, you can update the site key to a production site key from the WPML accounts section. For more details, please visit How to remove the 'This site is registered on WPML.org as a development site' notice.
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.
