Problem: You are trying to translate the English elements of an Elementor checkout page using WPML string translation, but despite translating them in the string translation section, no changes are visible on the page. Solution: 1. First, ensure that you have followed the steps mentioned in this forum post. 2. If the issue persists, go to WPML-> String Translation, search for the problematic strings, delete their translations, and then re-translate them.
If these steps do not resolve your issue, or if the solution seems outdated or not applicable to your case, we recommend opening a new support ticket. Additionally, 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. For further assistance, please visit our support forum at WPML support forum.
Problem: The client is trying to translate the site logo using WPML but encounters an issue where the logo does not change per language, remaining as the default language logo. Solution: 1. Ensure that the theme used (e.g., The7 theme) supports setting different logos via theme options. 2. Translate the logo ID in WPML's String Translation to inform WPML which logo to display for each language. If the default language logo ID is not visible on the String Translation page, use the 'Translate texts in admin screens' link to add it to the String Translation table. Then, add your second language image ID. For detailed guidance, visit How to Translate Theme Options. 3. If the logo images are not added for translation, navigate to WPML > String Translation > Admin text, search for your logo URLs/image, and add those strings for translation. 4. Check if the Multibyte String PHP extension is enabled on your hosting, as its absence can affect functionality.
If these steps do not resolve the issue or if the solution 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. If problems persist, please open a new support ticket.
Problem: The client is experiencing an issue with WooCommerce products in WPML where some products are duplicated in the secondary language. Some duplicates have the same URL, while others have a '-2' suffix. All problematic products have lost their translation connection with the default language. Solution: We recommend the following steps to address the issue: 1. Use the 'Set Language Information' option in WPML > Support > Troubleshooting Link to correct products/posts/pages that have been assigned to the wrong language. It's crucial to create a backup before performing this step. 2. If duplicates persist, follow the steps to disconnect and reconnect translations: - Disconnect the translation using the guide at How to Disconnect Translations - Reconnect the translations as per the instructions at How to Link Already Translated Pages - Manually delete the duplicated product. 3. If the issue is related to images not copying over, resave the primary language product and trigger the translation again.
Please note that these solutions might become irrelevant due to updates or specific site configurations. If these steps do not resolve your issue, or if you encounter different symptoms, 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 trying to activate a redirect for users based on their browser language on your bilingual site (Greek as default and English). You are unsure about the behavior when a user from Spain with Spanish as their browser language visits your site. Solution: We recommend setting up the browser language redirect feature. This feature will redirect users to the language that matches the language in their browser. If the visitor's browser language doesn't match any of the languages on your site, they will be redirected to the site's default language, which in your case is Greek. For detailed guidance on setting this up, please visit our documentation on Automatic Redirect Based on Browser Language.
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 our support forum.
Problem: The client was experiencing an issue where after renaming attributes and changing their slugs in YITH ajax product filters, the new names were not appearing in the filter settings dropdown. Instead, the old names were displayed. This issue was suspected to be related to how WPML manages terms. Solution: We recommended the client to: 1. Create a full backup of the site. 2. Update all outdated plugins and themes, especially the WPML plugins. This can be done in Plugins -> Add new -> Commercial tab -> Click on the button to search for new versions -> Download and install the latest version of the WPML plugins. 3. Flush any cache memory that might exist. 4. Apply the workaround described in this errata page: https://wpml.org/errata/wordpress-6-7-mo-files-not-loaded-and-leading-to-missing-translations-on-front-end/ 5. Go to Woocommerce -> Woocommerce Multilingual & Multicurrency -> Status tab -> Fix any error that might appear in the first two sections. 6. Edit the filters manually on the secondary languages and manually add the changes to the configuration of each translated filter -> Save the changes -> Double-check if the issue disappeared.
If the solution provided here 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 the problem persists, please open a new support ticket at WPML support forum.
Problem: The client is experiencing an ERR_TOO_MANY_REDIRECTS error when using the 'Use directory for default language' option in WPML. Despite following the guide on setting up directory defaults and redirections, the error occurs intermittently. Solution: 1. We confirmed that the homepage redirection to the language directory is an expected result due to the settings applied. This is in line with the documentation provided at https://wpml.org/documentation/getting-started-guide/language-setup/directory-default-language/#redirect-the-root-domain-to-the-default-language-directory. 2. We suggested checking if the
home_url()
function is being filtered by other plugins or the theme, which might be causing the error. As a troubleshooting step, we recommended using a hardcoded URL (https://****/el) to see if the issue persists.
If this solution does not resolve the 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 the problem continues, please open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue where the WooCommerce Gift Cards plugin sends notification emails in Greek regardless of the site language from which the gift card was purchased. Previously, a snippet was used to solve this, but it now causes a fatal error. Solution: We recommended updating the functions.php file with the following code:
We asked the client to verify if the last email is translated correctly by checking their WPML plugin log.
Please note that this solution might be outdated or not applicable to your specific case. If this solution does not resolve your issue, we highly recommend checking related 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.
