FileZilla Forums

Hi Team,

First post. Love FileZilla - magic piece of software.

Have searched forum and help files but cant find answer.

Current version 3.41.2

For a few months and versions now, my Synchronised Browsing setting seems to be unsaved between restarts. I have it set in the site manager for the site I regularly connect to, but each time I start I have to reselect Synchronised Browsing.

I tried renaming FileZilla folder .....AppData\Roaming\FileZilla to .....AppData\Roaming\FileZillaold and starting from scratch, but still no joy.

Synchronised Browsing is a brilliant feature for me and I always want it operating.

Any assistance is appreciated.

Cheers
Ian

I have been noticing this lately, too, and don't recall that previously.

I have selected 'restore tabs and reconnect' in Settings. Neither synchronized browsing or directory comparison are restored on restart. I have set restore tabs and reconnect in Settings.

I have not documented this, but my 'file exists' selections do not seem to persist as they once did. Maybe it is just that I have not figured this latter feature out, but I had not noticed this until recently.

FileZilla Client
----------------

Version: 3.41.2

Build information:
Compiled for: x86_64-w64-mingw32
Compiled on: x86_64-pc-linux-gnu
Build date: 2019-03-18
Compiled with: x86_64-w64-mingw32-gcc (GCC) 6.3.0 20170516
Compiler flags: -g -O2 -Wall

Linked against:
wxWidgets: 3.0.5
SQLite: 3.26.0
GnuTLS: 3.6.6

Operating system:
Name: Windows 10 (build 17763), 64-bit edition
Version: 10.0
Platform: 64-bit system
CPU features: sse sse2 sse3 ssse3 sse4.1 sse4.2 lm
Settings dir: C:\Users\allen\AppData\Roaming\FileZilla\

Running latest Filezilla 3.43.0
Seems Synchronised browsing need to be manually selected every time one starts Filezilla. Can this be remembered between restarts as it used to be?

Cheers
Ian

I have to assume no one in development reads here. The problem is a simple and obvious one and maybe someone should submit a ticket, the instructions for submitting a ticket seem designed to discourage all but the most determined reporter.

This flaw is so very obvious that it should not require a ticket unless it only occurs under some circumstances, like for long-term users of certain systems. Perhaps some flag in a config is changed or stuck? Who knows?