Jili 291 casino login.Enjoy Free 888+200 Daily Legal Bonus

marcusschreiter
(@marcusschreiter)

9 years, 9 months ago

Unfortunately mqTranslate plugin will not be supported in future any more. They recommend to switch to qTranslateX plugin instead, what I did.

Result: my translation database was not imported properly. Lot’s of translations remain like this: [:en]English Text[:hu]Hungarian Text etc… in the frontend. With the previous plugin everything worked quite well.

Language switcher in the topbar only works well as long as I was logged in, when I was logged out I wasn’t able to change language as the window moved to quick away … bug?

After several import-export trials it crashed totally … finally not an option for me.

Honestly I am a bit exhausted of updating qTranslate supporting plugins again and again. I can just hope that there will be a stable solution for qTranslate soon, as WPML is also not an option for me … had a try with that. Would even pay for it.

Anyway I appriciate very much all the energy and time you guys invest in plugin development, a big ‘thank you’ to all of you developers!!!

Viewing 8 replies - 1 through 8 (of 8 total)

Plugin Author John Clause
(@johnclause)

9 years, 9 months ago

Hi, which version did you use? We are testing now 3.2 release candidate. Could try that? It is on GitHub, where you can download it with ‘Download ZIP’ button on GitHub page or press here for the sake of convinience.

This version fixes a few things, and most importantly it has a better conversion tool for mq-migrating users, who must read this article https://qtranslatexteam.wordpress.com/2015/02/24/migration-from-other-multilingual-plugins/ before engaging with the migration.

I am really sorry for your trouble. The author of mq decided to deprecate without coordinating with us. I accept that we are not really ready to get mq- users smoothly enough, and we have now no choice, but to go ahead and fix the stuff as soon as possible …

Thread Starter marcusschreiter
(@marcusschreiter)

9 years, 9 months ago

Dear John,
thanks for your kind support. I tried your 3.2. beta version and unfortunately it also doesn’t fix my problems. The speciality in my eCommerce shop is it includes some product configuration features which uses WooCommerce product attribute.

qTranslateX is not able to translate or modify the attribute names, even manually I am not able to do so (see attachment!)

https://dl.dropboxusercontent.com/u/12328764/product-attribute-names.jpg
https://dl.dropboxusercontent.com/u/12328764/attribute-names.jpg

That is also influencing the frontend:
https://dl.dropboxusercontent.com/u/12328764/attribute-names_frontend.jpg

Under mqTranslate it works all well, unless l am importing from there to your plugin or even WPML … ??

Any other ideas?

Plugin Author John Clause
(@johnclause)

9 years, 8 months ago

I assume your import from mq problem was solved?

As for Woocommerce integration, there is new plugin “WooCommerce & qTranslate-X“. Did you try it?

Thread Starter marcusschreiter
(@marcusschreiter)

9 years, 8 months ago

Dear John,
great stuff you programmed recently ;), congratulations!

The WooCommerce/qTranslate+X problem is solved now with your new plugin “WooCommerce & qTranslate-X”.

Still the defined attributes are not working with some widgets (e.g. Yith-WooCommerce-Ajax-Navigation widgets). Here the old problem remains unfortunately:

https://dl.dropboxusercontent.com/u/12328764/AJAX-Navigation-widget-problem_1.1.jpg

https://dl.dropboxusercontent.com/u/12328764/AJAX-Navigation-widget-problem_1.jpg

A bug which might be fixed in the next version ?? ?????

Anyway, thanks a lot!

M.

Plugin Author John Clause
(@johnclause)

9 years, 8 months ago

Hi @marcusschreiter: we had some progress, not sure if your problems are solved by now. I tried to reproduce your pictures and failed so far. It seems to work better now. Could you tell me if you still have any problem?

Thread Starter marcusschreiter
(@marcusschreiter)

9 years, 8 months ago

Hello John,
thanks, I realized that there has been changed things on the newest update in the attribute section.

I updated the existing attributes, but somehow it does not have any effect on widgets or product attributes ?? (see links below!)

– attribute screenshot

– widget screenshot

– product screenshot

Somehow it keeps the old attribute values/names starting with [:en] …. [:hu] …. [:de] …

Maybe the cache should be cleaned??? Any other idea?

Thanks for that great support!!!

M.

Plugin Author Gunu
(@grafcom)

9 years, 8 months ago

@marcusschreiter,

with all support still only one star worth?

Thread Starter marcusschreiter
(@marcusschreiter)

9 years, 8 months ago

good point …. support convinced me.

Viewing 8 replies - 1 through 8 (of 8 total)

The topic ‘Not an option’ is closed to new replies.