Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add folder does not work #877

Closed
Jozzeh opened this issue Jul 4, 2017 · 4 comments
Closed

Add folder does not work #877

Jozzeh opened this issue Jul 4, 2017 · 4 comments
Assignees
Labels

Comments

@Jozzeh
Copy link

Jozzeh commented Jul 4, 2017

Remote FTP version 1.1.0 -- Local OS : Windows 10 -- Connection type : FTP -- Remote OS : Linux

Test 1. When creating a new folder (right mouse click a folder in the remote panel -> add folder) , the folder is not created on the remote. (no error or success notifications, no special console logs)

Test 2. Create a folder locally, right click it, and choose 'Upload' leads to a success notification, but does not create the folder on the remote server.

Test 3. --> Create a file in the local folder and choose to upload the file. This results in an error notification 'could not upload' and the console logs : 553 Could not create file

EDIT
This issue is only on FTP connections. On SFTP-connections, all 'tests' above succeed at what they should do.

@icetee icetee self-assigned this Jul 4, 2017
@icetee icetee added the bug label Jul 4, 2017
@aaronvalavi
Copy link

I faced to the same situation. Surprisingly, it works for some directories and not for the others. The problem started after upgrading to v1.1.0

icetee added a commit that referenced this issue Jul 6, 2017
+ Optimized structure query for mkdir
+ Add notification if exists file / folder on server (Only
remote-ftp:add-file and remote-ftp:add-folder command)
@icetee
Copy link
Owner

icetee commented Jul 8, 2017

Is the new version solved the problem?

@aaronvalavi
Copy link

Thanks Icetee. Yes, once I updated that to v1.1.1, it worked with no problem. Today, I updated it to 1.1.2 and it works great. Thanks a lot.
Still don't know where the problem was.

@icetee
Copy link
Owner

icetee commented Jul 8, 2017

It was a wrong condition 😕
Thanks for answer!

@icetee icetee closed this as completed Jul 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants