Hello,
ever since updating to FileZilla_3.66.0.1_macosx-x86.app.tar.bz2 from 3.65.0.0, i can reproduce a critical transfer error with all files that include the following character:
’ (I'm not sure if it is parsing correctly, it seems to be a weird way the apostroph gets used on Russian computers (I'm not Russian, the files originate from a Russian))
Downloading from proftpd to a local samba share. Zero issues with the same configuration and 3.65.0.0 on MacOS. The second i upgrade, the critical transfer error comes back.
PS: Is there a way to setup filezilla in a way that it respects the "do not look for updates" option instead of still looking for updates and just not showing the new version number, yet nagging to upgrade at every program start?
Critical transfer error introduced with FileZilla_3.66.0.1_macosx-x86
Moderator: Project members
Re: Critical transfer error introduced with FileZilla_3.66.0.1_macosx-x86
Please post a complete log of a transfer attempt.
"Do not check for updates" works exactly as it says. If unchecked, FileZilla truly does not check for updates. As updates are important, it politely asks you to check for updates yourself after some time.
"Do not check for updates" works exactly as it says. If unchecked, FileZilla truly does not check for updates. As updates are important, it politely asks you to check for updates yourself after some time.