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.

Sign up for GitHub

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

Jump to bottom

Edited file no longer uploaded when parent directory name changes #8351

Closed
cyberduck opened this issue Nov 21, 2014 · 3 comments
Closed

Edited file no longer uploaded when parent directory name changes #8351

cyberduck opened this issue Nov 21, 2014 · 3 comments
Labels
bug core wontfix

Comments

@cyberduck
Copy link
Collaborator

ff970c1 created the issue

Everything works as expected when editing some html files. But when I edit a file with an uncommon file extension, when I save it Cyberduck doesn't upload it to the FTP server.

Attachments
@cyberduck
Copy link
Collaborator Author

ff970c1 commented

After more testing, I noticed that the description isn't correct, but the bug is on a different level. It is not about file extensions.
The local version of the directory I was working on (inside /private/var) hadn't followed a rename on the server: I had renamed 'contents' to 'Contents', and Cyberduck stopped receiving notifications about local file changes.
So, the bug is: case change on the server side don't seem to be properly followed in the temporary local directory.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:3 nugget]:

I just tried the history log to see what happens. The result is the screenshot cyberduck2(access denied 530 error message). The second screenshot is ( I hope) the log you requested.
When I tried the history log try the last day I was able to successfully log in was 11/21/2014. Hope this helps.

I think this was comment was intended for #8348.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

An error message like

Screen Shot 2014-12-05 at 13.47.53.png

is expected in this case as the file cannot be uploaded to the previous location.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug core wontfix
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cyberduck