Plugin Author
Tim W
(@timwhitlock)
This means Loco Translate is failing to get the standard WordPress remote connection interface.
Shown here: https://localise.biz/wordpress/plugin/manual/filesystem#remote
I can’t speculate as to the reason for the failure, but can you normally use this connection dialogue in your WordPress, like installing themes and plugins from in the browser?
Yes, I haven’t had any issues with anything else and the author selection works, so it is able to connect. I tried clicking “start translating” anyway and got this “Error: Parent directory doesn’t exist”. The directory does exist and was created by this plugin so I’m not sure what’s going on…
Plugin Author
Tim W
(@timwhitlock)
Well if the connection dialogue failed then you won’t be connected, which probably explains why it thinks the parent directory doesn’t exist.
Either way, let’s tackle your first problem first. Presumably you get this error when you press “Connect”? Please elaborate on when you see it and what you’re doing at the time. I need as much relevant detail as possible because I have no way to reproduce your problem otherwise.
Plugin Author
Tim W
(@timwhitlock)
Also, do you have FS_METHOD defined in your wp-config.php ?
I’m going to Loco Translate > Plugins > [choose plugin] > I’ve chosen a language > Click choose a location >> error.
FS_METHOD is not defined in wp-config file.
Plugin Author
Tim W
(@timwhitlock)
I can’t explain why your credentials form fails, but there is one alarm bell from your screenshot.
The Author path is correct (beginning with “plugins/”), but Custom and System paths are wrong. (They should not begin with “/wp-content”). All paths in Loco Translate should be relative to wp-content or something has gone wrong. Not much use me guessing though. Do you have a non-standard file layout? or are you using symbolic links or something?
Can you translate other plugins or themes? Do they show incorrect paths too?
No,I think my file layout is typical. I haven’t changed anything.
It looks like all plugins/themes are incorrect.
Plugin Author
Tim W
(@timwhitlock)
I need to see what your site defines as WP_LANG_DIR. Can you debug your site to find this out? Loco Translate relies on this and if it’s wrong then System and Custom paths will be wrong too.
Plugin Author
Tim W
(@timwhitlock)
That looks wrong to me.
Is /wp-content really in the root of your operating system? It’s very unlikely that it is.
Correct this to the real path to your wp-content directory and you should find that things work as expected.
