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

Was not offered to import FileZilla's bookmarks upon installation #5289

Closed
cyberduck opened this issue Oct 6, 2010 · 4 comments
Closed

Was not offered to import FileZilla's bookmarks upon installation #5289

cyberduck opened this issue Oct 6, 2010 · 4 comments

Comments

@cyberduck
Copy link
Collaborator

7f2f993 created the issue

Just like the title says. As stated in the initial email, I expected to be prompted to import FileZilla's bookmarks.

@cyberduck
Copy link
Collaborator Author

@ylangisc commented

Can you send us your sitemanger.xml file in Application Data\FileZilla inside your home directory to [mailto:feedback@cyberduck.ch feedback@cyberduck.ch].

@cyberduck
Copy link
Collaborator Author

@dkocher commented

On my machine your file was successfully detected. Having Cyberduck on a different drive is not a problem. Cyberduck tries to locate sitemanager.xml in the system's AppData path. Can you check the APPDATA path on your machine (with cmd.exe):

echo %APPDATA%

Your sitemanager.xml file should be located in *%APPDATA%\FileZilla*

@cyberduck
Copy link
Collaborator Author

7f2f993 commented

The sitemanager.xml is indeed located in the system's AppData path. It did work when I re-installed Cyberduck the 2nd time (on C:\ this time). I may try to re-install it on my other drive to see if it's still a problem.

@cyberduck
Copy link
Collaborator Author

@ylangisc commented

That's weird. In my view there is no relation between the installation drive and the AppData path. Would be nice if could retry it on your other drive. Since the FileZilla import status is stored in the settings files please make sure to remove the Cyberduck folder from the AppData path before running the freshly installed version.

@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.
Projects
None yet
Development

No branches or pull requests

1 participant