Problema: Il cliente ha implementato uno shortcode per inserire dati automatici da Plastic Bank. Lo shortcode funziona correttamente nella pagina in italiano, ma causa un crash del sito con un errore 500 quando viene implementato nella pagina in inglese. Soluzione: Il problema era causato dal modulo shortcode di Elementor che non gestiva correttamente la traduzione dello shortcode. La soluzione trovata dal cliente è stata quella di inserire lo shortcode all'interno di un modulo di testo, il che ha risolto il problema sia nella versione italiana che in quella inglese del sito.
Se stai riscontrando un problema simile, ti consigliamo di provare a spostare lo shortcode in un modulo di testo anziché utilizzare il modulo shortcode di Elementor. Inoltre, se la soluzione proposta non dovesse essere applicabile al tuo caso o risultasse obsoleta, ti invitiamo a visitare la pagina dei problemi noti e a verificare che tu abbia installato le versioni più recenti dei temi e dei plugin. Se il problema persiste, non esitare a aprire un nuovo ticket di supporto.
Problem: If you're using WPML with Learndash and Elementor and encounter the error 'the preview could not be loaded' when trying to edit course content in a second language with Elementor. Solution: We recommend checking your theme's
functions.php
file for any custom functions that might be affecting the URLs of your courses. Specifically, look for a function that modifies the course links based on the language. Here is an example of such a function that could cause issues:
function change_link_corsi( $permalink, $post ) {<br /> if ( $post->post_type === 'sfwd-courses' ) {<br /> $resource_terms = get_the_terms( $post, 'ld_course_category' );<br /> $term_slug = '';<br /><br /> // Get the current language code<br /> $language_code = apply_filters( 'wpml_current_language', null );<br /><br /> // Dynamically retrieve the slug for the current language<br /> $default_slug = 'i-nostri-corsi'; // Default slug in the primary language<br /> $translated_slug = apply_filters( 'wpml_get_translated_slug', $default_slug, 'sfwd-courses', $language_code, 'post' );<br /><br /> // Fallback to default slug if translation is missing<br /> $translated_slug = $translated_slug ?: $default_slug;<br /><br /> if ( ! empty( $resource_terms ) ) {<br /> foreach ( $resource_terms as $term ) {<br /> if ( $term->slug === 'featured' ) {<br /> continue;<br /> }<br /> $term_slug = $term->slug;<br /> break;<br /> }<br /> }<br /><br /> // Build the final permalink<br /> $permalink = trailingslashit( get_home_url() ) . $translated_slug . '/' . ( $term_slug ? $term_slug . '/' : '' ) + $post->post_name;<br /> }<br /> return $permalink;<br />}<br />add_filter( 'post_type_link', 'change_link_corsi', 10, 2 );
Try commenting out or adjusting this function and see if Elementor loads correctly.
If this solution does not resolve your issue or seems irrelevant due to updates or differences in your setup, 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 developing a site using WPML to translate group types into different languages and want to order the group type list in the drop-down menu alphabetically. However, the drop-down list of group types is not ordered alphabetically, and changes made in one language affect the order in other languages as well. Solution: We have identified that the option to order group types alphabetically in the drop-down menu cannot be translated in WPML and requires custom programming. This is beyond the scope of our support. We recommend contacting one of our certified partners for custom programming assistance. You can find a suitable partner at http://wpml.org/documentation/support/wpml-contractors/. Additionally, consulting the BuddyBoss plugin author might provide further customization options.
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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: After migrating content from a test site to a live site, the client faced issues with the translation backend interface where brands were unavailable. Specific problems included the inability to add or update translated products in brand categories, and navigational issues on translated brand pages. Solution: We recommended the following steps to resolve the issue: 1. Navigate to WPML > Settings > Category Translation. 2. Locate Brand (product_brand) and set up different aliases for your brand in different languages. Change 'Brands' to 'Brand'. 3. Click save. We advised the client to check if the issue was resolved by visiting their brand page.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 problems persist, please open a new support ticket at WPML support forum for further assistance.
Problem: You are trying to display selected English translated posts in other translated languages using Advanced Custom Fields, but face issues where the database query reverts to the current page language. Additionally, using the 'use translation if available or fallback to default language' option disrupts pagination. Solution: We recommend implementing a custom solution where you switch the language on-the-fly to the desired one, query the intended posts, and then switch back to the current language for the rest of the process. This approach is not supported out of the box by WPML, as it is designed to display content based on the "current language" only. You can use WPML's filters and action hooks for proper multilingual support in your theme or plugin. For more details, visit the following resources:
If you require further custom work, consider contacting WPML Contractors at 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 this does not resolve your issue, please open a new support ticket at WPML Support Forum.
Problem: The client is using Elementor and WooCommerce to display carousels with links to product attributes (brands) that are set to 'not translatable'. The links should link to the current language version, but WPML is altering them to the default language. The client wants these specific links to remain unchanged in the translated pages. Solution: We recommended adding a custom filter to the theme's functions.php file to prevent WPML from altering these specific links. Here is the code snippet to add:
This code will add the specified brand to a blacklist, preventing WPML from translating the URL. For more information on managing sticky links in WPML, visit WPML Sticky Links documentation.
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 issues persist, please open a new support ticket.
Problem: You need to change the footer content of your DIVI theme and cannot find the footer template in the translation management page after modifying the default English content. Solution: If you're experiencing this issue, we recommend checking the specific post types for your DIVI theme's footer, header, and body layouts directly in your WordPress admin area. You can access these areas using the following links:
Please visit the following URLs and check if you can translate the templates.
Footer: yourdomain/wp-admin/edit.php?post_type=et_footer_layout
Header: yourdomain/wp-admin/edit.php?post_type=et_header_layout
Body: yourdomain/wp-admin/edit.php?post_type=et_body_layout
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 this does not resolve your issue, please open a new support ticket with us for further assistance.
Problème : Vous tentez de traduire des custom fields ajoutés sur des catégories produits WooCommerce via un fichier JSON géré par ACF, mais vous rencontrez des difficultés pour les rendre accessibles dans WPML > Settings > Custom Fields Translation, même avec l'option 'show System fields' cochée. Les champs sont visibles dans Custom Terms, mais pas dans l'endroit attendu. Solution : 1. Assurez-vous que les custom fields pour les catégories WooCommerce, qui sont considérées comme une taxonomie, soient cherchés dans 'Custom Term Meta Translation' plutôt que dans 'Custom Fields Translation'. 2. Vérifiez les paramètres de traduction dans WPML et ACF. Pour les champs textuels et les images, ils doivent être déclarés avec l'option 'Translate' pour être traduisibles via l'éditeur de traduction. Pour les images, vous pouvez également utiliser l'option 'Copy' pour que l'ID de l'image d'origine soit copié comme valeur de traduction, ce qui permettra d'appeler l'image traduite via Media Translation. 3. Alignez vos paramètres de mode de traduction dans les réglages WPML et ACF pour obtenir le comportement désiré.
Si cette solution ne résout pas votre problème ou semble dépassée, nous vous recommandons de vérifier les problèmes connus, de confirmer que vous avez installé les dernières versions de vos thèmes et plugins, et si nécessaire, d'ouvrir un nouveau ticket de support sur notre forum de support.
