Language not working in widgets

[hubosh]

I just started using qTranslate XT and I was hoping for a fix to this problem.
When using text in a widget I can't change the languages, it just copies the last data I entered and stores it in all language tabs.

[herrvigg]

Can you give more details about this problem? I guess you are referring to switching tabs but i can't see in which context. The widgets in the sense "qtranslate Widget" are meant to change language on the front-end so there's no data to enter there. So i suppose it's an admin page but which one? A screenshot could also help.

[herrvigg]

About the widget admin menu, the only translatable field is the title and this works fine for me.

[hubosh]

Can you give more details about this problem? I guess you are referring to switching tabs but i can't see in which context. The widgets in the sense "qtranslate Widget" are meant to change language on the front-end so there's no data to enter there. So i suppose it's an admin page but which one? A screenshot could also help.

What I meant is when I use text in a widget, I can't translate it, not even the title.
Here's a screenshot

[forexmd]

I also have problem with translating widgets, on old qtranslate-x and the same on qtranslate-xt , which i just installed. When i save some text on one language immediately appears the same text for the second language. Do you have any idea how to make it work normal. Website forex.md . Thanks

[herrvigg]

OK now i see, i can reproduce the problem. The input and textarea fields don't have the blue marker, which means they are not considered as translatable but i guess they are supposed to be part of those. I tried quickly to update the json config but it didn't work. I'll see if i manage to fix it.

[forexmd]

whatever it is worth, the problem is only on the latest version of WP. With previous version of WP, was no problem, i have always made changes in footer/widgets before and had no problems with that.

[herrvigg]

Oh i thought it was a much older problem.
If you look into i18n-config.json the selectors are input[id^='widget-'][id$='-title'] and textarea[id^='widget-text-'][id$='-text'] but this does not hold anymore. I tried other selectors simply with input.title and textarea.text but it doesn't work. At least we know the widget-right selector works as the switching tabs are shown.
Also i'm not sure why there are some similar selectors in widgets-exec.js, i thought this was supposed to be done with the json file only. If someone finds a solution let me know.

[herrvigg]

Mmmm this looks more problematic than it first appeared. All these elements are created dynamically under div.text-widget-fields which does not exist when the page is loaded... but only when the drop down button is clicked.

I don't think such behavior exists in any other UI element. Technically it should still be possible but it becomes more complex and i'm not sure what is the best solution. Any suggestion welcome.

[herrvigg]

I found more info about the underlying changes. It came with WP 4.8 (May 2017!) so that's not really new but no qTranslate handles this yet.

https://make.wordpress.org/core/2017/05/23/addition-of-tinymce-to-the-text-widget/

Since the new Widget is using TinyMCE it should be possible to make it work as for the Classic Editor. But i don't know yet how to do so properly.

[forexmd]

@herrvigg thanks for help. It took me a lot of time to realize that the problem was in my .htaccess file, there has been added a command .
Header set Referrer-Policy "origin"
and for some reason this command brought up the issue. I removed it and work like a charm. Unfortunately I still cant use the qtranslate-xt because it does not integrates with Yoast SEO (with plugin, Yoast SEO & qTranslate-X). Hope will have in near future

[herrvigg]

Mmm now i'm quite confused. Good if this solved something but i'm not sure we talk about the same things. Imo there is still a problem. How can the new text widget work? How is the translation managed in the edit boxes? Do you have the blue line on the left side of the title and the content?

[hubosh]

I found more info about the underlying changes. It came with WP 4.8 (May 2017!) so that's not really new but no qTranslate handles this yet.

https://make.wordpress.org/core/2017/05/23/addition-of-tinymce-to-the-text-widget/

Since the new Widget is using TinyMCE it should be possible to make it work as for the Classic Editor. But i don't know yet how to do so properly.

Yeah it's an old issue with qTranslate X, I once found a solution that includes downloading a plugin called Classic Text Widget. hope that can help.
Thanks for your amazing effort.

[dreamliner789]

I installed today the new translate-xt.
It seems to work wonderful and fine. Thanks to all who work on that helpful plugin.

But the bug with the widget translation is not solved in my case.
I tried to handle it with the recommended "Classic Text Widget" but that doesn't show me the true text in backend and doesn't works with html code.
The lines with header and policy is not written in my htaccess.

Did someone made the same experience and could solve this issue?
Thanks for any help and recommedations.

[herrvigg]

Here also i'm a bit lost with all the different widgets and screens. What is this issue exactly about?

• It seems the widget works when used from /wp-admin/widgets.php
• but not from /wp-admin/customize.php

Is that the problem raised here? Is it for any widget or for a specific plugin?

[forexmd]

hI, I am having troubles with QTranslateSlug. The field that we add the translation disappeared from the page editor. Any Idea how to fix it? Thanks

…

On Mon, Nov 2, 2020 at 5:30 PM Hr0bar ***@***.***> wrote: No, the opposite is true, it doesnt work at: /wp-admin/widgets.php it works at: /wp-admin/customize.php Here you can see a video of the latest XT, all kinds of bugs happen, not all were captured in the video... https://www.youtube.com/watch?v=dA03SXlyhLg&feature=youtu.be https://www.youtube.com/watch?v=FyChSDyRiXA&feature=youtu.be — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#616 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKY5DP4522U5FMLZOSFKAW3SN4XHPANCNFSM4GFLJZEA> .

[herrvigg]

Finally, a new solution to fix the text widget is now made available by #1042.

[Hr0bar]

Awesome !! Thank you a lot for this.

…

On Sat, Jun 26, 2021, 16:06 Herr Vigg ***@***.***> wrote: Finally, a new solution to fix the text widget is now made available by #1042 <#1042>. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#616 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABTNGZTCTD2EMFFC5SDPARTTUXNE3ANCNFSM4GFLJZEA> .

[herrvigg]

Merged in master for testing.

[herrvigg]

Released in 3.11.0.