Problem: You want to use prepaid credits for automatic translation with WPML, but your site does not detect these credits despite them being assigned. The error logs show 'Api error missing resource: No sitekey found for this website', although it is registered. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Ensure you back up your site first for safety reasons. 2. Temporarily deactivate the HelloPack Client plugin. 3. Unregister and then re-register the WPML plugins. For detailed instructions, please refer to our documentation here: WPML Documentation. 4. Reactivate the HelloPack Client plugin after re-registration. If the problem persists, please provide temporary access (WP-Admin and FTP Login info) to your site, preferably a staging site, so we can further investigate and debug the issue.
Please remember to back up your database and website before making these changes. We also need your permission to deactivate and reactivate plugins and the theme, and to change configurations on your 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. If needed, do not hesitate to open a new support ticket with us for further assistance at WPML Support Forum.
Problem: If you're experiencing issues with certain elements not appearing translated on your German page, such as 'stratégie' not showing as 'Strategie', despite using the advanced translator. Solution: We recommend you try the following steps: 1. Add the following XML in WPML >> Settings > Custom XML Configuration section:
2. Make a small change in the default language page to reload the translation. 3. Open the translated page in WPML Advanced Translation Editor and press the Complete Translation button. If the issue persists, try these additional steps: 1. Open the default language page in Edit mode. 2. Make a small change, such as adding a space or + sign in the accordion title where you are facing issues. 3. Save the page. 4. Remove the small change made in step 2. 5. Update the page again. 6. Try to translate the page again. If you still encounter problems, especially with strings containing the ampersand (&) symbol, replace "&" with "and" in the default language accordion title and check if that resolves the issue. Alternatively, consider using a WPML-compatible blocks plugin from this list: WPML-compatible blocks plugins.
If these solutions do not resolve your issue or if they seem 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is experiencing a 'too many redirects' error when switching languages on the login page of their site. This issue arises while using a third-party plugin, Woocommerce Members Only, to create a login page. Solution: 1. Ensure that all WPML plugins and add-ons are updated to the latest version, currently 4.7.2, to benefit from recent bug fixes and improvements. Update instructions can be found at http://wpml.org/faq/install-wpml/. 2. Verify the setup of the WPML and the member plugin on your site to match the configuration on your website. If discrepancies are found, adjust accordingly. 3. If the problem persists, consider contacting the plugin author to report the issue, especially since the plugin claims to be WPML compatible. They can also seek direct support from us through the Go Global program at https://wpml.org/documentation/support/go-global-program/.
If this solution does not resolve your issue or seems outdated, we 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: You are using the Download Monitor plugin to manage site downloads and have encountered issues with translating shortcodes for different language pages. Specifically, the shortcode [downloads category="plumbing" orderby="date"] works on the English page but not on the Welsh page, where it is ignored and displays nothing. Solution: We have identified that the Download Monitor plugin is not currently compatible with WPML. To address this, we recommend the following steps: 1. Set the plugin's custom post type, taxonomies, and related custom fields to translatable. 2. Translate the "download" endpoint and the category using WPML's String Translation. 3. Update the page translation to include the translated shortcode with the translated Welsh category. This can be done by switching from the top admin menu. 4. If these steps do not resolve the issue, we suggest contacting the plugin author to request a compatibility update with WPML. You can provide them with resources on making their themes/plugins compatible by directing them to achieving WPML compatibility for themes and plugins and the Go Global program.
If this solution does not apply to your case, or if it seems outdated, 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. We highly recommend opening a new support ticket if further assistance is needed. Visit our support forum at WPML support forum for more help.
Problema: El cliente ha creado y subido el feed de productos al Google Merchant Center en español y desea saber si es posible subir el feed en otros idiomas configurados con WPML (EN, FR, IT, DE) para que Google los muestre en diferentes países. Solución: Actualmente, el plugin Google for WooCommerce que el cliente está utilizando no es compatible con WPML para manejar feeds multilingües.Puedes explorar el plugin WooCommerce Google Product Feed que sí ofrece compatibilidad con WPML para esta funcionalidad.
Si esta solución no resuelve tu problema o si la información proporcionada se ha vuelto obsoleta, te recomendamos abrir un nuevo ticket de soporte. También es aconsejable revisar los problemas conocidos, verificar la versión de la solución permanente e instalar las últimas versiones de los temas y plugins. Para más asistencia, visita nuestro foro de soporte.
Problem: The client is unable to upload SVG files through WPML Media Translation after updating WPML plugins. They encounter a default image or a 'Security check failed' message depending on the SVG plugin used. This issue persists across multiple environments. Solution: We recommend verifying the compatibility of the SVG plugin with WPML. WordPress does not natively support SVG, and third-party plugins like 'Safe SVG' might not be compatible with WPML. Check if the plugin has been updated recently and might require a compatibility update with WPML. Encourage the plugin author to join WPML's Go Global program to ensure compatibility. For more details, visit WPML's Go Global program.
However, if the problem is outdated or if you have further questions, feel free to open a new support ticket. We also 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.
Problema: Utilizas el tema ThemeRex. Y en la sección Servicios de tu sitio web, al hacer clic en cualquiera de los servicios en español, te redirige a un error 404. Aunque las páginas están traducidas, no se muestran correctamente incluso después de cambiar el slug. Solución: El slug del CPT creado por el tema no se puede traducir.Seguimos estos pasos: 1. Accedimos a WPML > String translation. 2. Buscamos "services" asegurándonos de marcar "Exact match". 3. Seleccionamos la entrada que corresponde al dominio "trx_addons". 4. Eliminamos esta entrada. Después de realizar estos pasos, los servicios en español aparecieron, aunque con el slug sin traducir. Identificamos que el problema está relacionado con el uso del plugin ThemeREX Addons, el cual no es compatible con WPML. Puedes encontrar más información sobre la incompatibilidad aquí: https://wpml.org/es/plugin/themerex-addons/ Te recomendamos cambiar de plugin para los CPTs o evitar traducir el slug. Aquí tienes una lista de plugins compatibles con WPML para trabajar con custom post types: https://wpml.org/plugin-functionality/custom-post-types-taxonomy/ Si esta solución no resuelve tu problema o si la información proporcionada se ha vuelto obsoleta, te recomendamos abrir un nuevo ticket de soporte. También te sugerimos revisar los problemas conocidos en https://wpml.org/known-issues/, verificar la versión del arreglo permanente y confirmar que tienes instaladas las últimas versiones de los temas y plugins. Para más asistencia, visita nuestro foro de soporte: https://wpml.org/es/forums/forum/ayuda-en-espanol/
Problem: The client is experiencing 404 errors, incorrect URL links on translated pages, and issues with string translations in a WooCommerce environment after restoring a backup. The suspected causes include potential conflicts with SEO plugins or incompatibilities with the 'Divi Plus' plugin. Solution: 1. To address the 404 errors, we recommend resetting the SEO Press plugin by deactivating it, clearing all caches, and reactivating it. This approach has resolved similar issues in the past. 2. If the problem persists, test the website with only WPML plugins and a standard theme, while deactivating all other plugins to isolate the issue. 3. For issues specifically related to the 'Divi Plus' plugin, it appears there is a known compatibility issue with WPML. We advise contacting the plugin author to request a compatibility update. Additionally, plugin developers can refer to WPML's documentation for making their plugins compatible. 4. If you encounter PHP notices related to '_load_textdomain_just_in_time', this is a known issue with WordPress 6.7 affecting many plugins and themes, including WPML. Updating your plugins and themes to the latest versions may resolve these notices.
Please ensure to back up your website before making any changes and, if possible, perform these actions on a staging site to avoid affecting your live site.
If these solutions do not resolve your issues or if they seem outdated or irrelevant 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
