Problem: The client wants to display different currency symbols ('BGN' in English and 'лв.' in Bulgarian) on their website without using WooCommerce Multilingual & Multicurrency. Solution: If you're experiencing this issue, we recommend implementing custom code to check the website's language and adjust the currency symbol accordingly. Here is an example of how you can do this:
Please note that custom coding is beyond our support scope, so it's your responsibility to maintain and update this code as needed.
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 is trying to fetch a localized string for a JavaScript file in the Gutenberg editor, but the string is not being returned in the current language of the admin screen, even after attempting to switch languages programmatically. Solution: We recommend using the
wp_set_script_translations
function to ensure that the JavaScript file recognizes the localized strings. This involves generating a .json file from the .po file and ensuring it is loaded through a WordPress hook. Here are the steps:
For more detailed guidance, refer to the WordPress documentation on how to handle internationalization in block editors: Internationalization in Gutenberg.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, we highly recommend checking related known issues at WPML Known Issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. Additionally, you can open a new support ticket for further assistance at WPML Support Forum.
Problem: You need to redirect the root URL of your website to a language-specific version using WPML, but you are unable to create a template for the redirection. Solution: 1. First, create a PHP template in your site’s theme folder. You can name it 'Root redirect'. It's recommended to add PHP files to a child theme. For more details on creating custom page templates, visit Creating Custom Page Templates for Global Use. 2. Add the following content to your new PHP page template file:
3. Edit your root page and in the right sidebar, expand the Summary section and select the template you just created. 4. Update the page.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we recommend opening a new support ticket. Also, 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, please visit our support forum at WPML Support Forum.
Problem: If you're experiencing issues with URL parameters not being passed when switching languages on your site, despite having 'Preserve URL arguments' correctly configured, this might be due to the parameters being populated via JavaScript.
Solution: We recommend modifying your 'Search' button to submit and reload the page. This adjustment should ensure that the parameters are correctly passed to the language switcher. If you prefer to keep your current setup, you will need to implement custom code to modify the language links in the language switcher to include these client-side populated parameters.
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 for further assistance.
Problema: Se stai riscontrando la duplicazione degli articoli tradotti visualizzati in entrambe le lingue sul tuo sito, il problema potrebbe essere dovuto alla mancanza di filtri per la lingua nel codice che gestisce la visualizzazione degli articoli. Soluzione: Per risolvere questo problema, dovresti aggiungere alcuni filtri specifici per WPML nel tuo array di argomenti quando recuperi gli articoli. Modifica il tuo codice come segue:
$current_language = apply_filters('wpml_current_language', NULL);
$args = array(
'numberposts' => -1, // -1 per tutti
'post_type' => 'annunci', // oppure 'post', 'page'
'orderby' => 'date', // oppure 'date', 'rand'
'order' => 'DESC', // oppure 'DESC'
'suppress_filters' => false, // Assicurati che WPML filtri i risultati
'lang' => $current_language, // Filtra per lingua corrente
);
Questo codice assicura che gli articoli vengano filtrati per la lingua corrente, evitando così la duplicazione nei risultati. Per ulteriori dettagli, consulta la pagina degli hook di WPML.
Se questa soluzione non dovesse essere più rilevante o non risolvere il tuo problema, ti consigliamo di aprire un nuovo ticket di supporto. Ti raccomandiamo inoltre di verificare la presenza di problemi noti correlati su https://wpml.org/known-issues/, di controllare la versione della correzione permanente e di assicurarti di avere installato le ultime versioni dei temi e dei plugin.
Problem: The client is developing a multilingual site using WPML and ACF (flexible content) and needs to handle the 'wpml_cf_preferences' differently based on the editor mode (WP Editor or WPML translation editor) for specific posts. They encountered issues with repeater fields not syncing correctly between translations depending on the translation mode used. Solution: We do not have a direct hook to dynamically change 'wpml_cf_preferences' based on the editor mode at the moment. However, you can check the editor mode used for translation by querying the 'editor' column in the 'icl_translate_job' database table or the '_last_translation_edit_mode' meta. Based on this information, you can programmatically set the 'wpml_cf_preferences'. For detailed guidance on setting translation preferences for ACF fields, refer to our documentation here: Setting the Translation Preferences for ACF Fields Created Using PHP Code.
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 at WPML support forum for further assistance.
Problem: The client is developing a site and encountering an issue where the WooCommerce cart does not add more than 2 products. This problem occurs when the 'WooCommerce Multilingual & Multicurrency' plugin is active. Deactivating the plugin resolves the issue, suggesting a potential conflict. Solution: We recommended conducting a conflict test to pinpoint the source of the issue. This involves: 1. Deactivating all plugins except WPML, String Translation, WooCommerce, and WooCommerce Multilingual. 2. Switching to a default theme like 'Twenty Twenty-One' to check if the theme is causing the conflict. Since changing the theme was not an option for the client, we provided an alternative solution by offering access to our sandbox environment for further testing. This helps in isolating the issue in a controlled setting, free from server or external factors that might influence the behavior on the main site.
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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: The client added text that was not appearing for translation in WPML. Solution: First, we recommend wrapping the string with the gettext function to make it translatable. For example, use the following code:
Next, follow these steps to ensure the string appears in WPML's String Translation: 1. Go to String Translation. 2. Enable the "Auto-register strings" option. 3. Visit the page on the front end where the string is displayed. 4. Disable the "Auto-register strings" option. 5. Search for the string to translate it. For detailed instructions, please visit our guide on finding strings that don't appear on the String Translation page.
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.
Problem: The client was experiencing an issue where the category links on the shop page were incorrectly set to random product URLs instead of the correct category links. This problem was observed in both the default and translated versions of the site. The client had already tried disabling WooCommerce, which did not resolve the issue. Solution: We recommended the client to disable WPML and its add-ons to verify if the issue still persisted on the default shop page. Upon further investigation, it was found that switching to a default theme like Twenty Twenty-One or Storefront resolved the issue, indicating a compatibility problem with the 'Windazo' theme. We advised the client to contact the theme's support team for a possible fix and suggested that the theme developers might consider joining the Go-Global program to ensure compatibility with WPML.
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 the issue persist, please do not hesitate to open a new support ticket with us for further assistance.