Plugin Author
Gunu
(@grafcom)
@damir Calusic
See this Integration Guide Keep us informed…
Hi Gunu,
I tried this –> add_filter(‘widget_text’, ‘qtranxf_useCurrentLanguageIfNotFoundUseDefaultLanguage’, 9999);
I added it to my functions.php and I tried it even in a custom plugin but I guess I am missing out on something?
The latest on GitHub has it fixed. Could you please test?
Awesome, the text works perfectly now!
Plugin Author
Gunu
(@grafcom)
@damir Calusic
You are welcome!
You can review this plugin to help other people to find out the value.
Will this be available after an update?
Plugin Author
Gunu
(@grafcom)
@mtporter
yes, but you can download it now here
@gunu I just saw this. Having the same widget problem. Downloaded the master that you posted above and I was getting: [:] , [:es] & [:en] on top of different sections. Had to put the old one back up since the website is live…
Plugin Author
Gunu
(@grafcom)
@gediweb
you use the default WP text widget?
Can you show me a screen-shot?
@gunu yes. I just put the updated plugin back in so you can see on the home page: http://onezoneusa.com/ & http://onezoneusa.com/es/
Plugin Author
Gunu
(@grafcom)
This is a default WP text widget????
Can you give a screen-shot how it looks at admin side?
Yes. WP text widget, but now that I think about it, the sections that are giving me the error are WPBakery Visual Composer. I’m using WPBakery Visual Composer & qTranslate-X plugin…
No its not the visual composer. Just deactivated it and I’m still showing those tags on the front end. I also just noticed it’s showing part of the home page and blue widget areas in both languages. In english and spanish. Repeating it.
here is a screenshot of the back-end widgets: http://onezoneusa.com/Capture.PNG
Plugin Author
Gunu
(@grafcom)
show the open widget please 🙂
