Support ForumSlow backpanel using WPML string translation – Support Forum https://support.ishyoboy.com/forums/topic/slow-backpanel-using-wpml-string-translation/feed/ Sat, 18 May 2024 06:38:44 +0200 http://bbpress.org/?v=2.5.12-6148 en-US https://support.ishyoboy.com/forums/topic/slow-backpanel-using-wpml-string-translation/#post-3331 <![CDATA[Slow backpanel using WPML string translation]]> https://support.ishyoboy.com/forums/topic/slow-backpanel-using-wpml-string-translation/#post-3331 Mon, 07 Jul 2014 14:06:20 +0000 dpcdpc11 I’m using WPML string translation plugin and since I’ve enabled the theme translation everything in working slow as hell, specially the backend when I need for example to edit a post/page.
I think it’s somehow related to the VC since the js_composer has 770 strings indexed by the WPML.
Is there a way to improve the performance of the website, maybe by forcing WPML to ignore the strings in js_composer?
Any ideas?

]]> https://support.ishyoboy.com/forums/topic/slow-backpanel-using-wpml-string-translation/#post-3353 <![CDATA[Reply To: Slow backpanel using WPML string translation]]> https://support.ishyoboy.com/forums/topic/slow-backpanel-using-wpml-string-translation/#post-3353 Tue, 08 Jul 2014 06:24:10 +0000 IshYoBoy Hey,

Would you find it as a solution if you did the translations using the String Translations plugin and then exported them as .PO/.MO files and then loaded them into the theme?

In this way the theme and plugins would be loaded trough text-domain files not the WPML plugin.

What do you think?

Cheers

A 5 star rating is always a great motivation for us if you are happy with our theme or support!
Themeforest | MojoMarketplace | Creative Market

]]> https://support.ishyoboy.com/forums/topic/slow-backpanel-using-wpml-string-translation/#post-3389 <![CDATA[Reply To: Slow backpanel using WPML string translation]]> https://support.ishyoboy.com/forums/topic/slow-backpanel-using-wpml-string-translation/#post-3389 Tue, 08 Jul 2014 10:30:20 +0000 dpcdpc11 Yes that could be a good solution. Didn’t know I could do that using WPML.

But I think somehow this needs to be fixed on a long term.
What if you put the js_composer (which I think is part of the Visual Composer) into a plugin? This way it could be ignored by WPML.
I think the WPML string translation plugin stresses too much on the mysql database because of the many strings, which slows down the whole website.

Best,
Cristian

]]> https://support.ishyoboy.com/forums/topic/slow-backpanel-using-wpml-string-translation/#post-3416 <![CDATA[Reply To: Slow backpanel using WPML string translation]]> https://support.ishyoboy.com/forums/topic/slow-backpanel-using-wpml-string-translation/#post-3416 Wed, 09 Jul 2014 14:08:41 +0000 IshYoBoy Hey Christian,

You are right! The WPML String Translation plugin is a resource sucker if you use it to translate all the strings. Therefore the best way is to use the .PO/.MO files. This is the original way how WordPress is made and runs much much smoother.

The “js_composer” is the Visual Composer actually. We decided to add it into the theme, as if it was used as a separate plugin we could not assure compatibility. Many users could use different version and problems/errors could be caused because of that. This could cause too much frustration.

Cheers

A 5 star rating is always a great motivation for us if you are happy with our theme or support!
Themeforest | MojoMarketplace | Creative Market

]]>