Problem: The client is experiencing an issue where the hreflang links are pointing to the wrong domain on their multilingual sites, specifically the Swedish links are incorrect, pointing to .de and .com instead of .se. Despite having the WPML SEO addon installed and ensuring all plugins are updated, the issue persists. Solution: We identified that the problem stems from the code in the wp-config.php file, which uses
$_SERVER['HTTP_HOST']
to define WP_SITEURL and WP_HOME. This can lead to incorrect domain references because it depends on the main site defined in the server configuration. We recommend modifying this code to avoid reliance on
$_SERVER['HTTP_HOST']
, or alternatively, contacting your hosting provider to address this configuration issue.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client reported that the featured image and attribute images were not displaying on the translated version of a WooCommerce product, although they appeared correctly in the original version.
Solution: We identified two separate issues causing the image display problems:
1) For the product images: - Open the product for editing in the default language. - Switch to Croatian from the top admin bar to load the translation within the WordPress editor. - Add or update the product images (featured and gallery) and then update.
2) For the variation images:
- First, we adjusted a setting in WPML -> Settings -> Custom Term Meta Translation for the field "st-image-swatch" from 'don't translate' to 'Copy'.
- Navigate to Products -> Attributes in the default language. - Click "Configure terms" for the attribute "Barva". - After loading the terms, switch to Croatian from the top admin bar. - Click "Quick edit" for a term missing the image. - Simply click "Update Barva" without making any changes to the term. Repeat the last two steps for each term needing this fix.
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 needed, please open a new support ticket at WPML support forum for further assistance.
Problema: Se stai riscontrando problemi con la visibilità dei campi customizzati in italiano (lingua default) dopo aver tentato di attivare le traduzioni con WPML e ACF, e non riesci a compilare questi campi quando crei un nuovo articolo, il problema potrebbe essere legato alla cache. Soluzione: Ti consigliamo di svuotare la cache del tuo sito. Questo può risolvere il problema di visibilità e accessibilità dei campi nelle diverse lingue. Se il problema persiste, potrebbe essere utile verificare le impostazioni di traduzione per i gruppi di campi in ACF. Assicurati che le impostazioni siano corrette per il tuo caso specifico, ad esempio se hai scelto di avere 'stessi campi tra le lingue', 'campi diversi' o 'esperto'. Se questa soluzione non risolve il problema o se le informazioni sembrano non aggiornate o non applicabili al tuo caso, ti consigliamo di visitare la pagina dei problemi noti e di verificare che tu abbia installato le versioni più recenti dei temi e dei plugin. Se necessario, non esitare a aprire un nuovo ticket di supporto.
Problema: Después de migrar el sitio web a un nuevo hosting, se presenta un error 500 al cambiar de idioma en las versiones en inglés e italiano, causando un bucle de redirecciones internas. El hosting sugiere que el problema podría estar en la configuración del archivo ".htaccess". Solución: Si estás experimentando este problema después de una migración, es probable que no sea causado directamente por WPML, sino por una configuración en el sitio migrado. Te recomendamos seguir los pasos de nuestra guía para identificar y resolver problemas de configuración del archivo ".htaccess" en https://wpml.org/faq/why-is-htaccess-getting-overwritten-with-the-language-folder-on-my-wpml-website/.
Si esta solución no resuelve tu problema o si la información parece desactualizada o no aplicable a tu caso, te sugerimos abrir un nuevo ticket de soporte. Te recomendamos encarecidamente revisar los problemas conocidos en https://wpml.org/known-issues/, verificar la versión de la solución permanente y confirmar que tienes instaladas las últimas versiones de temas y plugins. Para más asistencia, visita nuestro foro de soporte en https://wpml.org/es/forums/forum/ayuda-en-espanol/.
Problem: You are trying to translate the intake forms on your site into Spanish, but despite purchasing additional translation credits, the forms remain in English. Solution: If you're experiencing this issue, it's likely because the intake forms are managed by a third-party service. We recommend checking with the service provider to see if they offer options to translate or create separate forms for each language. Then, you can integrate these forms accordingly on your site. Additionally, ensure that your website setup is optimized for translations by providing us with debug information. You can find instructions on how to provide this information here: https://wpml.org/faq/provide-debug-information-faster-support/ For more initial troubleshooting steps, please visit: https://wpml.org/faq/checklist-before-opening-a-ticket-in-wpml-support/ For details on privacy and security when providing debug information, see: https://wpml.org/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/
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: The client was experiencing slow page load times on their WooCommerce site and was unsure about the necessity of the 'make it multilingual with ID' feature for their theme. They also encountered a PHP error related to the theme triggering a function incorrectly, which could affect WPML String Translation performance.
Solution: 1. We adjusted the WPML settings for 'product_variation' post type to 'Translatable - only show translated items' to ensure global product attributes can be translated. 2. We recommended running the troubleshooting options available under WooCommerce > WooCommerce Multilingual & Multi-Currency > Status > Troubleshooting to help improve site performance. 3. We deactivated the unsupported 'WPML All Import' addon and suggested removing unnecessary plugins. 4. We identified a PHP error caused by the theme related to the premature loading of text domains. We advised reporting this to the Porto Support Team and provided a link to further information on this issue: https://wpml.org/errata/php-error-wp-6-7-notice-function-_load_textdomain_just_in_time-was-called/ 5. We tested the site with a default theme, which significantly improved the load time, suggesting the theme might be a contributing factor to the performance issues.
If this solution does not resolve your issue or seems irrelevant due to being 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 issues persist, please open a new support ticket at our support forum.
Problem: If you're experiencing issues where translated product pages lead to a '404 Not Found' page instead of displaying correctly in other markets, it might be due to a conflict with a specific plugin. Solution: We recommend deactivating the 'Permalink Manager for WooCommerce' plugin to resolve this issue. After deactivation, the translated products should display correctly. If this solution does not resolve your issue or 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 the problem persists, we highly recommend opening a new support ticket for further assistance. You can do so here: WPML support forum.
Problem: The client is experiencing an issue with the taxonomy general name in WooCommerce, where the name displays as 'Product Product line' instead of the desired format. The client wants to remove the redundant 'Product' from the taxonomy name. Solution: We recommended the client to first deactivate all WPML plugins and test with only WooCommerce active to check if the issue still occurs. This should be done after taking a full backup of the website and ideally on a staging or development site to avoid affecting the live site. If the issue persists even without WPML, it suggests that the problem might not be related to WPML. In such a case, the client should follow up with the theme provider, Woodmart, for further assistance.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, we highly recommend opening a new support ticket. Additionally, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. For further assistance, you can also visit our support forum at https://wpml.org/forums/.
Problema: Il cliente stava affrontando un errore 500 sulle pagine del suo sito. L'errore era stato inizialmente attribuito al plugin WPML, in particolare a 'sitepress-multilingual-cms'. Un messaggio di errore nel file di registro indicava problemi di compatibilità con la versione della piattaforma, specificamente 'Composer detected issues in your platform: You are running 8.4.3.' Inoltre, un ulteriore approfondimento ha rivelato che un script JSON (
<script type="application/ld+json">
) conteneva errori di sintassi, presenti in tutte le versioni linguistiche del sito, ma causando l'errore 500 solo nelle pagine in inglese. Soluzione: Dopo aver identificato che l'errore 500 non era direttamente legato a WPML ma piuttosto a un errore di sintassi in uno script JSON, il cliente ha corretto gli errori nello script. Questa correzione ha risolto il problema dell'errore 500.
Se la soluzione proposta risulta non pertinente, perché potrebbe essere datata o non applicabile al tuo caso, ti consigliamo di aprire un nuovo ticket di supporto. Ti raccomandiamo inoltre di consultare la pagina dei problemi noti, verificare la versione della correzione permanente e confermare di avere installato le ultime versioni dei temi e dei plugin. Per ulteriore assistenza, visita il forum di supporto WPML.
Problem: The client is experiencing an issue when trying to edit 'Propertys' pages in Greek on their website. The error message displayed is 'You attempted to edit an item that doesn't exist. Perhaps it was deleted?'. This problem occurs even when WPML is disabled, suggesting it might not be related to WPML. Solution: 1. Verify the issue by disabling WPML to confirm if it persists, which in this case, it does. 2. Since the issue also occurs with WPML disabled, it suggests that the problem might be with the theme or another plugin. We recommend contacting the Houzez Support Team for further assistance as the issue might be related to the theme used.
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.
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.
