Hi,
I noticed that my settings in Site Manager disappeared after I updated FileZilla to 3.27.0.1. After further research, I noticed
* directory FileZilla was created under C:\Users\\AppData\Local and it has the image files similar to what I saw in Data\Cache
* setting XML's are in C:\Users\\AppDataRoaming\FileZilla
I wonder whether this is a bug or something changed in this new release?
Thanks.
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on BlueSky
Follow us on Facebook
Follow us on LinkedIn
Follow us on Mastodon
Follow us on Twitter
Hi there,
i got the same problem and found the solution of it. It looks like that the following file is missing in the filezilla application directory "PortableApps\FileZillaPortable\App\filezilla":
fzdefaults.xml
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<FileZilla3>
<Settings>
<Setting name="Config Location">$FILEZILLA_PORTABLE_SETTINGS</Setting>
<Setting name="Cache directory">$FILEZILLA_PORTABLE_CACHE</Setting>
</Settings>
</FileZilla3>
After I recreated this file, everything is back again.
I can confirm that it most definitely is a bug.
For some reason, the fzdefaults.xml was not included in the installer. As a workaround until it gets fixed, use the following pastebin and save it to App\filezilla\fzdefaults.xml
the missing fzdefaults.xml
EDIT: Lol, got beaten to the punch while I was getting this ready (I couldn't get the xml to show correctly for some reason)
It is better to get multiple answers, which give the information to all of us, to solve the problem for now.
That is true.
As a bonus, what I have provided also completely disables the update check.
Yeeee!! this works for me
Thanks to both!
Yeeee!! this works for me ))
Thank you for the fix.
A revision to fix this is now mirroring. Posting shortly...
Sometimes, the impossible can become possible, if you're awesome!
This is fixed in FileZilla Portable 3.27.0.1 Rev 2 which was just posted. I've added an additional check to the FileZilla Portable build process to ensure it does not happen again. I've also added a check to the launcher that will be included in the next release that will cause it to refuse to run without that file present. My apologies for any inconvenience.
Sometimes, the impossible can become possible, if you're awesome!
Thanks, John! (and the two others who posted the missing file in the meantime) This community of developers and users is awesome!
Now that I have the new 3.27.0.1 and Help->About says it's getting settings from the correct place again, is it safe to delete the FileZilla folder in AppData\Roaming? It appears to have been created when I first opened the buggy version, and renaming it seems to have no adverse effect, but I thought I should confirm with the experts.
It is safe to delete the folder, provided the application has been exited to ensure no unintended file locks exist.
Just an idea, but wouldn't it be better to have the "Disable update check" setting set to 1 in fzdefaults.xml so that the launcher doesn't have to keep turning off the update check? When set FileZilla completely hides its update checker and doesn't run the check regardless of what the "Update check" setting in filezilla.xml is set to. If users really want to update FileZilla before the PortableApps package gets updated, they can do so manually with the zip download of FileZilla.