Problem: The client needed assistance with displaying a widget in different languages. Solution: 1. We instructed the client to navigate to the WordPress Dashboard > Appearance > Widgets. 2. Check the Footer area where the widgets are located. 3. Look for an option within the widgets to select the language in which to display the widget, as shown in these images:
4. Select English for the current widget. 5. Create a new widget or copy the existing one and select Spanish, then manually add the content and title in Spanish.
If this solution does not resolve the issue, we asked the client to provide the URL, username, and password for their WordPress dashboard, ensuring that they have a backup of their website before proceeding.
If the provided solution is not relevant due to being outdated or not applicable to your case, we recommend opening a new support ticket. We also 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 further assistance is needed, please contact us through the WPML support forum.
Problem: The client is experiencing issues with automatic synchronization of menus in different languages, despite all pages being translated. Solution: We recommend trying the "Fully Custom" approach for creating and managing menus manually. This method allows for more control over the translation and synchronization of menu items. You can find detailed instructions on how to implement this solution in our documentation: Translating Menus.
Please note that this solution might not be relevant if it's outdated or not applicable to your specific case. If after following the steps the issue persists, we encourage you to open a new support ticket. We also highly recommend checking our related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you need further assistance, please contact us in the WPML support forum.
Problem: The client has automatically translated their website and found that the URLs have been translated as well, which is causing issues with SEO and redirections. They are looking to revert the URLs to their original state, preferably only for blog articles.
Solution: We recommend checking the translation of the primary language page to see if the URL slug string is visible. If it is not found there, proceed to search for the string "address" in the string translations. If the string has been translated, you should undo the translation. If you're experiencing this issue, follow these steps to correct the URL translations: 1. Edit the translation of the primary language page to look for the slug string. 2. If the slug string is not there, go to the string translations and search for "address". 3. If you find that "address" has been translated, undo the translation.
Please note that this solution might be outdated or not applicable to your case. If the issue persists, we highly recommend checking the related 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 do not hesitate to open a new support ticket. You can reach our support forum here.
Problem: The client needed assistance with an issue related to translating taxonomy terms, as described in a video they shared. Solution: We advised the client to navigate to WPML → Taxonomy Translation and use the drop-down menu to select the taxonomy they wish to translate. Then, they should click the plus icon to add or adjust the translations and remove the '-es' if necessary. For more detailed instructions, we provided a link to our documentation: Translating Post Categories and Custom Taxonomies. If that method does not resolve the issue, we recommended going to Posts → Categories, selecting the Spanish language, and editing the category to adjust it.
Please note that this solution might be irrelevant due to being outdated or not applicable to your case. If so, we encourage you 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. If you need further assistance, please contact us in the WPML support forum.
Problem: The client needed assistance with reclaiming WPML credits after transitioning their website from WordPress to Shopify and no longer having backend access. Solution: We moved the remaining credits back to the client's WPML.org account. The client had an existing balance of credits, and with the addition of the reclaimed credits, their total is now updated. The client can view their credit balance on their WPML account page. Furthermore, we advised the client on how to remove the WPML key for the site that has been moved to Shopify through their WPML account sites page.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If you're experiencing similar issues and the provided solution does not help, we encourage you to open a new support ticket. We also highly recommend checking the related 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 contact us on the WPML support forum.
Problem:
If you're trying to add a language switcher to your menu instead of the footer or if you're facing issues with the styling of your language switcher, such as wanting a floating language switcher or dealing with a call-to-action (CTA) that is cut out on different devices and resolutions.
Solution:
To add a language switcher to different locations on your site and customize it to your needs, we recommend following these guides:
For a floating language switcher, please refer to the guide on creating a custom language switcher.
If you encounter a CTA that is cut out, this issue is related to your theme's CSS and is beyond the scope of our support. We suggest learning more about CSS and how to adjust your design for various devices and resolutions through online resources.
If you still need assistance, don't hesitate to open a new support ticket. You can reach out to us on the WPML support forum.
The client was experiencing an issue with the banner section on their multilingual website, where the Italian version was showing Html
1
<br />
code on several bannel text blocks.
Solution:
We asked the client how they were creating the banner section, whether they were using a page builder or theme options. Upon receiving access to the website, we identified that the correct line break tag is
1
<br />
not
1
< br >
.
We updated the Italian version with the correct line break tag. We advised the client to check the changes and informed them that if the solution provided does not seem relevant or if they need further assistance, they should not hesitate to open a new support ticket.
Problem: The client was experiencing an issue where the review process was continually loading, and they were also unable to include a language selector in the main navigation menu of their website.
Solution: For the infinite loading of the Review button, we recommended the following steps: 1. Ensure no languages are hidden in "WPML > Languages". 2. Clear the site's and server's cache. 3. Navigate to "WPML > Support > Troubleshooting" and press the following buttons: - "Clear the cache in WPML" - "Remove ghost entries from the translation tables" - "Fix element_type collation" - "Set language information" - "Fix post type assignment for translations" - "Synchronize local job IDs with ATE jobs"
For the issue of posts not appearing in the Italian version, we advised the client to translate the posts within the "Nos Chambres" and "Activités à Solenzara" sections.
To add a Language Selector in the Main Navigation, we provided a guide on configuring the Language Switcher: Language Switcher Options.
If the layout of the review page appeared broken, we suggested conducting a plugin conflict test by deactivating all plugins except for WPML and its add-ons and then checking the translation review page.
The issue with the broken review page was resolved by correcting the HTTPS configuration. We updated the Site URL and WordPress URL in (Settings > General) to use 'https' instead of 'http', which fixed the problem.
If this solution doesn't look relevant, please open a new support ticket at the WPML support forum.
Utilizamos cookies para optimizar nuestro sitio web y nuestros servicios. Su consentimiento nos permite procesar datos como el comportamiento de navegación. No dar su consentimiento puede afectar a algunas funciones.
Funcional
Siempre activo
Necesario para que nuestro sitio web funcione y se comunique correctamente.
Preferencias
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Estadísticas
Las utilizamos para analizar las estadísticas de nuestro sitio. La información recopilada es totalmente anónima.El almacenamiento o acceso técnico que se utiliza exclusivamente con fines estadísticos anónimos. Sin una citación, el cumplimiento voluntario por parte de su proveedor de servicios de Internet, u otros registros de terceros, la información almacenada o recuperada solo para este propósito generalmente no puede usarse para identificarlo.
Marketing
Estas cookies rastrean su navegación para proporcionar anuncios relevantes para usted.
