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

Remote folder acts like it loops back to its parent folder #7128

Closed
cyberduck opened this issue Mar 8, 2013 · 2 comments
Closed

Remote folder acts like it loops back to its parent folder #7128

cyberduck opened this issue Mar 8, 2013 · 2 comments
Assignees
Labels
bug ftp high priority worksforme
Milestone

Comments

@cyberduck
Copy link
Collaborator

cyberduck commented Mar 8, 2013

8a85a48 created the issue

I have a "demo" folder on my website to share files with clients and colleagues.

I just created an "ABC demo" subfolder, which appeared in /demo list. When I double-click the "ABC demo" line, the entire window stays the same except for the path menu, which changes to this:

/demo/ABC demo

It appears that Cyberduck thinks the new subfolder is somehow an alias of its parent /demo folder.

Double-clicking the "ABC demo" line several more times yields this path:

/demo/ABC demo/ABC demo/ABC demo/ABC demo

When I open the /demo folder in Fetch, I'm able to open the empty /ABC demo subfolder. So it doesn't appear there's anything wrong with the subfolder.

I created a separate "ABC demo2" subfolder. Cyberduck as no problem opening it.

-- Ward

@cyberduck
Copy link
Collaborator Author

cyberduck commented Apr 4, 2013

@dkocher commented

Please post the transcript from the log drawer (⌘-L).

@cyberduck
Copy link
Collaborator Author

cyberduck commented Apr 4, 2013

8a85a48 commented

I should have thought to check the log when I opened this ticket.

I just tried reproducing the problem using CyberDuck 4.2.1 on 10.6.8. The "/ABC demo" folder is behaving correctly now.

As I recall, the problem persisted for a couple of days and several CyberDuck sessions. I have no idea what may changed in the interim.

You can close this ticket.

-- Ward

@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.
Labels
bug ftp high priority worksforme
Projects
None yet
Development

No branches or pull requests

2 participants