Plugin Author
Tim W
(@timwhitlock)
Presumably you’ve read these other topics?
https://ww.wp.xz.cn/support/topic/error-failed-to-get-credentials-form/
https://ww.wp.xz.cn/support/topic/error-failed-to-get-credentials-form-2/
What have you tried after looking at these?
I’ve been getting this error since last week
What has happened since last week? Was it working before? Loco Translate has not been updated for a month. Have you tried rolling back to the previous version?
Yes, I’ve read both topics. I can’t seem to rollback my plugin version using ww.wp.xz.cn 🙁 There’s no option to do this in the dashboard.
I did change the SFTP password a couple of weeks ago. Could that be the issue?
Plugin Author
Tim W
(@timwhitlock)
I did change the SFTP password a couple of weeks ago. Could that be the issue?
Have you tried changing it back to see if that is the issue?
I can’t set the password to a specific string. It’s a random string everytime I click the button. Is there a way to manually set the password that loco translate is trying to use? I’m thinking maybe Loco cached the initial set of credentials and now they don’t work anymore.
-
This reply was modified 5 years, 11 months ago by
luisrudge.
Plugin Author
Tim W
(@timwhitlock)
Is there a way to manually set the password that loco translate is trying to use?
You can define WordPress FTP constants, but I doubt this would make any difference. If Loco Translate tries to use a password and fails you should see a failure message like “Failed to connect to server…”. The error you are getting has an unknown cause, which is why you don’t see a useful reason.
I’m thinking maybe Loco cached the initial set of credentials and now they don’t work anymore.
Loco allows you to save your credentials in the session. Logging out will clear that, but as above – this is probably not your problem.
Do you have any recommendations for someone running Loco inside ww.wp.xz.cn?
Plugin Author
Tim W
(@timwhitlock)
Do you mean wordpress.com? Either way, no. I don’t have any suggestions.
Yeh, wordpress.com hehe. is there a way to pay for premium support so we can jump on a call to get this fixed?
Plugin Author
Tim W
(@timwhitlock)
The free support here is the only support available.
As I don’t know what’s causing your problem, your options are to (1) debug the code that fetches the credentials form, or (2) use direct file system access.
(1) The credentials form is fetched when the authorize function returns false. The only non-error situation where this can return false without fetching a form is if you have defined FS_METHOD as “direct”. This is mentioned in the first link above, so you must already have ruled this out. Other possible points of failure would be inside WordPress’s request_filesystem_credentials function. I can’t debug that for you.
(2) Setting up your server to write files directly to the file system is the only way to avoid using a remote connection. This is documented.
Many people run this plugin on wordpress.com. I can’t guess what you’re doing differently, or why remote connections suddenly stopped working for you. I find it very unlikely that changing the password would cause this. Something else possibly changed.
If you have any new information, please post it. Otherwise I’m out of suggestions.
