Could not determine if file is writeable.

Hello,

I have this weird message appearing when I try to move a file to a directory, using the remote host panel.

1. In the remote host panel, display the contents of your remote host.
2. Right click in your remote host and create a new directory.
2. Select a file and drag it onto a directory (to move the file there).
3. You get the following error: "Move 'name of file' to 'name of directory' failed: failed to move file 'name of file' to 'name of file': could not determine if file "name of directory" is writeable."

In this error, notice the following:

In the second part of the error message (marked with green), it says "failed to move file 'name of file' to 'name of file'". Yes. You did read it right. The error message actually says that it failed to move a file into a file (eg failed to move info.php into info.php)! You can't move a file into a file! I don't know if the error message phrased wrong or the operation is doing something weird.

In the third part of the error message (marked with blue), it's complaining that the directory is not writable. It doesn't have to write the directory. It's moving the file inside the directory. Also, I created the directory from within PhpStorm's Remote Host panel. It should know what it was creating.

So I am not understanding what is the purpose of this confusing message and why it cannot determine if the directory is writable or not. I am using SFTP with an SSH key. Can someone confirm if this is a bug of some sort?

Thanks.

3 comments
Comment actions Permalink

Hi,

Sorry for confusing message. Could you please turn on FTP logging and attach idea.log? If it contains sensitive file names etc. feel free to send to me via kirill (dot) safonov (at) jetbrains (dot) com.

Thanks,
Kirill

0
Comment actions Permalink

Sent the logfile to your email. Thank you!

0
Comment actions Permalink

Hello,

thanks for the log sent. The problem is that library we use tries to get remote user's groups and fails there. Unfortunately, there is no workaround for this problem now. I've created an issue about it, feel free watch it.

Thanks,
Elena

0

Please sign in to leave a comment.