[Resuelto] How to translate filters and static and dynamic texts of a View
Este hilo está resuelto. Aquí tiene una descripción del problema y la solución.
Problem:
I'm trying to translate Toolset fields with WPML, but if i check fields as translatables in WPML>Configuration and translate it in WPML>String translation, there is no change.
This support ticket is created hace 1 año, 5 meses. There's a good chance that you are reading advice that it now obsolete.
This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
Hoy no hay técnicos de soporte disponibles en el foro Juego de herramientas. Siéntase libre de enviar sus tiques y les daremos trámite tan pronto como estemos disponibles en línea. Gracias por su comprensión.
Sun
Mon
Tue
Wed
Thu
Fri
Sat
-
9:00 – 12:00
9:00 – 12:00
9:00 – 12:00
9:00 – 12:00
9:00 – 12:00
-
-
13:00 – 18:00
13:00 – 18:00
13:00 – 18:00
13:00 – 18:00
13:00 – 18:00
-
Supporter timezone: America/Sao_Paulo (GMT-03:00)
Este tema contiene 7 respuestas, tiene 2 mensajes.
I'm trying to translate Toolset fields with WPML, but if i check fields as translatables in WPML>Configuration and translate it in WPML>String translation, there is no change.
I have searched your documentation but have not found anything similar to what I want to solve. How can i do this?
You do not need to set the Toolset types as translatable in WPML -> Settings -> Post Types Translation. If you have settled it, please revert this change.
If you simply translate a page having these fields, they should be available to be translated in the Translation Editor. The same is for Views, Forms, and Toolset elements in general. Please check our doc related:
I followed the documentation you sent me but it did not work. I will divide my problem into points:
1. I want to translate the filters generated by the views; i searched it in WPML->Translation Management and WPML->String translation as the documentation says, but i don't see nothing. In the attached image (1) you can see text strings what I'm trying to translate .
2. I tried to activate the Views checkbox at WPML->Settings to search the text strings into filters. I searched it in WPML->String translation, and when i found it, the text string is checked as translatable in the language that i have set as default, as you can see in the attached image (2). I want translate Spanish to english
3. I didn't used WPML translator, so the documentation i found at Toolset don't work in this case.
Could you please show us every Toolset element you want to translate, as well as where they're located in the frontend? Also, I would like to request temporary access (wp-admin and FTP) to your site to take better look at the issue. You will find the needed fields for this below the comment area when you log in to leave your next reply. The information you will enter is private which means only you and I can see and have access to it.
Our Debugging Procedures
I will be checking various settings in the backend to see if the issue can be resolved. Although I won't be making changes that affect the live site, it is still good practice to backup the site before providing us access. In the event that we do need to debug the site further, I will duplicate the site and work in a separate, local development environment to avoid affecting the live site.
- Please make a backup of site files and database before providing us access.
- If you do not see the wp-admin/FTP fields this means your post & website login details will be made PUBLIC. DO NOT post your website details unless you see the required wp-admin/FTP fields. If you do not, please ask me to enable the private box. The private box looks like this: enlace oculto
Please, let me know if you need any additional details. Have a nice day.
We want to ask to apologize for this confusion, but it seems that the Views filters can be translated using the String Translation module, indeed. We have followed these steps:
- First, in WPML -> String Translation we enabled the 'Look for strings while pages are rendered' option, located at the bottom of the page
- Then, we visited the homepage, since the "Listado de estudios con filtro para móvil" View is there
- This registered the " TIPO DE ESTUDIO " string: enlace oculto
- However, it was registered as an English string. So we just selected it, and used the "Change the language of selected strings" button in order to assign the correct idiom
- After this, we could translate it into English and the translation displayed fine, please check the 'TYPE OF STUDY' filter: enlace oculto
Also, as a note, just bear in mind that it's important to disable the 'Look for strings while pages are rendered' option in the end of the process, since it considerably increases the load time of the website.
We kindly ask you to review these steps and check if you're able to fix the issue with them.
Now about the slug question you brought in the last reply, you should:
- use the " Set different slugs in different languages for Profesores. " link in WPML -> Settings -> Post Types Translation
- change the slug to Spanish, since it is being considered as English (similar as what happened above with the strings)
- translate it to English
After these steps it should be solved. Please give it a try and let us know if it works.
the filters are now translated, thank you so much, but the solution you give me to translate slugs doesn't work.
When i follow the steps you gave me for translate slugs, i saved changes, and there aren't any changes applied, i don't know why. But if I go to WPML>String translation, and i follow the same steps (i take the slugs and change to spanish as default language), and i return to WPML>Configuration>Post Type Translation, the slugs default language has changed (to spanish); however, i translate the slug, save changes and the changes has no applied.
Why do you think is this happening?
Thank you,
regards.
Los hilos nuevos creados por Mateus Getulio y vinculados a este se encuentran a continuación:
Glad that we were able to resolve the previous issue.
Regarding the new issue with the slug and strings translations, due to our support policy of having one issue per ticket, I had to open another topic for this problem. This is necessary in order to avoid mixing a lot of questions in the same ticket.
