Plugin Author
Tim W
(@timwhitlock)
I don’t know of any compatibility issues with twentyfifteen. I can’t speak about your custom theme though.
The invalid MO message usually occurs when Loco can’t find the right files. And that usually occurs when things aren’t named conventionally. Based on what you’ve told me I don’t have any suggestions.
Thank for you answser.
The situation is much more complicated than just a file location. The error message come from gett-text-compile.php (function isBigendian). It’s looks like the plugin can’t read binary data.
It’s weird because, if i use locao translat to create a .pot file , it’s work, but if i go back and click on the file created, i have the error.
Plugin Author
Tim W
(@timwhitlock)
What happens if you drop the MO file onto here?:
https://localise.biz/free/poeditor
If i drop the .pot file I can see the messages, as i expect to see in WP-LocoTranslate.
I suspect this issue come from a filesystem problem (like a file corruption or dedup on ZFS), not really from the plugin, because, the same WP setup works on different servers (same config).
The site migration was the last hope I had… sounds I need to prepare some coffee and start the migration asap 🙂
thank for your help and your great plugin
Plugin Author
Tim W
(@timwhitlock)
I asked you to drop the MO file because you said “It looks like the plugin can’t read binary data.” It can, so I wanted to check if the MO file was valid or not.
yes, but if i upload the file, the real file is not the one which is installed on my setup.
it’s a new one stored on localise.biz.
That’s why i suspect this issue is a file system issue. I will try to rename the theme to see if a new fresh name solve my problem.
thank again.
Looks the issue come from the server :(.
Thank you again for your help
Sorry to bothering you again.
Fresh install on a totally different server : same problem.
If i click your pot file… i have the same issue.
https://www.dropbox.com/s/qxoh8la25z7b91v/Capture%20d%27%C3%A9cran%202015-09-01%2011.40.39.png?dl=0
Plugin Author
Tim W
(@timwhitlock)
my POT file? you mean it’s loco-translate.pot that causes this error?
The current live version (1.5.3) contains 14 languages and none of them are showing in your screenshot. This hints at a file system problem.
What version do you have and how are you installing it?
Get wordpress.zip (4.3) from ww.wp.xz.cn => unzip
upload to a ftp
update the config
via the admin, get loco translate from plugin pane
activate loco translate
open the module
click loco-translate.pot
booum
any idea ?
I have an idea…
does your plugin communicate with localize.net ?
Plugin Author
Tim W
(@timwhitlock)
I meant what version of the plugin, but if you install from WordPress panel, then I guess it’s the latest.
For some reason your system cannot see the files. Off the top of my head the only known issue is that Solaris isn’t supported, because it can’t support PHP’s glob functions.
Are you on Solaris?
Enable WordPress debug mode and see if you get any warnings.
Plugin Author
Tim W
(@timwhitlock)
I assume you mean localise.biz. And no, it doesn’t.
yep, my mistake.
I do not succeed to use this plugin with a particuliar “.fr ” domain. Is there any chance that a DNS problem can affect the behaviour of this plugin ?
Thanks again for your help and your support
All my website are store in a reverse DNS folder hierachy :
– /home/fr.domain/www/(wp here)
I change for
/home/domain/www
and the plugin is now working correctly.
maybe the dot sign in the path is in conflict with the extension name
