Opened 16 years ago

Last modified 12 years ago

#1856 closed Feature request

Split FileZilla.xml in FTP Sites.xml+FileZilla settings.xml

Reported by: kraades Owned by: Alexander Schuch
Priority: normal Component: FileZilla Client
Keywords: Cc: kraades, Alexander Schuch
Component version: Operating system type:
Operating system version:

Description

FileZilla settings.xml and FTP Sites.xml can be
imported/exported separately but are merged into one
file FileZilla.xml that is stored in the FileZilla program
folder.

Because of feature request ID 777731 (see
http://sourceforge.net/tracker/index.php?
func=detail&aid=777731&group_id=21558&atid=372244)
it would be better if the FileZilla.xml is split into two
separate files FTP Sites.xml for the site info and FileZilla
settings.xml for the settings.

The site info can then be stored in a central location
and each user can have there own settings stored
locally.

Now I think of it. It would be great if a user can have a
local copy of their "private" site info stored locally
and "public" site info stored central.

Change History (3)

comment:1 Changed 12 years ago by Alexander Schuch

Can you please check the following RFE as well?
[ 777731 ] Configurable location of FileZilla.xml

FileZilla 3 beta11 has a file fzdefaults.xml which stores the location of the FileZilla configuration directory, among "global" Site Manager items. The global items get merged with the "private" Site Manager items in the given FileZilla configuration directory. The path name to the configration directory can contain environment values, so $USER (or whatever) can be used to give each user a separate FileZilla configuration directory.

Exporting and importing of settings is imported as well already.

Anything else that's missing?

comment:2 Changed 12 years ago by Alexander Schuch

It of course should mean: "Exporting and importing of settings is *implemented* as well already."

comment:3 Changed 12 years ago by sf-robot

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).

Note: See TracTickets for help on using tickets.