Plugin Author
Bjoern
(@greencp)
I have to admit, I’ve got no experience with Multisite setups and have only tested the plugin on single site installations. Also I didn’t write the native gettext implementation myself and it changes locale settings which might be the cause for it not working in the Multisite setup.
So, regarding gettext – I’ll have to look into that. I’ll try to contact the original author, maybe he can help out. Else I’ll have to dig into it deeper. Might take some time…
Network activation – I’ll set up a multisite installation to test it and fix the options issue. But as MO-Dynamic doesn’t depend on any locale settings I see no reason why it shouldn’t work network activated.
BTW: 0.3 will get some small improvements in MO-Dynamic wich will reduce memory consumption and runtime even more (though just a Little bit).
Plugin Author
Bjoern
(@greencp)
Just a small status info: I might have found the reason why native gettext doesn’t work with multisite. So maybe a fix is on it’s way 🙂
Plugin Author
Bjoern
(@greencp)
Version 0.2.1 includes a possible fix for the multisite native gettext issue. Please update and give it a try.
Thanks for the quick reply,
We just updated to v0.2.1 and also tried it on a single site.
Unfortunately the issue remains. Even on the single site. 🙁
Do you experience the same issue on your sites?
Could it be because of the greek language (NON latin characters) ?
We also noticed an error which occurs when (steps):
1. Have both Use MO-Dynamic, Use native gettext checked
2. Uncheck both of them at the same time and save (meaning, nothing is checked)
3. Error
Warning: Invalid argument supplied for foreach() in /……/wp-content/plugins/wp-performance-pack/wp-performance-pack.php on line 59
Warning: Cannot modify header information – headers already sent by (output started at /……/wp-content/plugins/wp-performance-pack/wp-performance-pack.php:59) in /……/wp-includes/pluggable.php on line 896
Plugin Author
Bjoern
(@greencp)
The error should be fixed in 0.2.2 – it didn’t occur with my test Installation, but I added some extra checks which should prevent it. Please try to confirm this.
Native gettext on the other hand… the gettext Extension selects the translation by using system locale which has to be set correctly for it to work. This however can be quite difficult which is the reason why the native gettext patch didn’t make it into WordPress core yet. Setting the right locale (if it is possible at all) differs from system to system is seems (have a look here: http://www.php.net/manual/de/function.setlocale.php).
Thes plugin [em]Native gettext diagnosis[/em] (http://ww.wp.xz.cn/plugins/native-gettext-diagnosis/) performs some tests if native gettext can be used. I plan to include those tests into WPPP and extend them.
One solution (which the diagnosis plugin doesn’t test) could be to append the codeset to the locale which I guess would be UTF8 in your case. You can try it yourself if you want. Change line 227 in class.native-gettext.php from
setlocale (LC_ALL, $locale);
to
setlocale (LC_ALL, $locale.'.UTF8');
This might help, or not.
Plugin Author
Bjoern
(@greencp)
Version 0.3 includes multisite support. When network activated only the network admin can see and change options.
Plugin Author
Bjoern
(@greencp)
Version 0.4 brings another change to the way the locale is set when using native gettext. Please give it a try.
