[BUG] Newest Update (3.48.0) Opening File

Come here to discuss FileZilla and FTP in general

Moderator: Project members

Message
Author
marcus7777
500 Command not understood
Posts: 2
Joined: 2020-05-09 17:56
First name: Marcus

Re: [BUG] Newest Update (3.48.0) Opening File

#16 Post by marcus7777 » 2020-05-11 01:07

Thanks, Boco, I did not know.

Bad news especially when Windows 7 still has 5x more users than Windows 8 :(

So bye FileZilla, it was a very nice relationship while it lasted. Thank you!

User avatar
boco
Contributor
Posts: 25275
Joined: 2006-05-01 03:28
Location: Germany

Re: [BUG] Newest Update (3.48.0) Opening File

#17 Post by boco » 2020-05-11 10:10

Not so fast. This specific issue seems to be not specific to Windows 7. So, an eventual fix might benefit us, too. If it still runs after the fix, no guarantees given.

I just meant we cannot request any support anymore, here.
### BEGIN SIGNATURE BLOCK ###
No support requests per PM! You will NOT get any reply!!!
FTP connection problems? Do yourself a favor and read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
### END SIGNATURE BLOCK ###

mleroy
500 Command not understood
Posts: 1
Joined: 2020-05-12 17:24
First name: Mike
Last name: LeRoy

Re: [BUG] Newest Update (3.48.0) Opening File

#18 Post by mleroy » 2020-05-12 17:34

On windows 8.1 before the last update I could open a remote csv or xlsx file created on a Raspberry Pi. The files would open in the same excel session. After the upgrade FileZilla didn't know how to open the files. I found about adding Filetype associations:

xls "C:\Program Files\Microsoft Office\Office14\EXCEL.EXE"
xlsx "C:\Program Files\Microsoft Office\Office14\EXCEL.EXE"
csv "C:\Program Files\Microsoft Office\Office14\EXCEL.EXE"

This works but each file is opened in a separate session of excel.

I tried the "-open" option - same action.

Any hints?

ALINCO
421 Kicked by Administrator
Posts: 1
Joined: 2020-05-28 17:33
First name: GOODLUCK
Last name: ikechukwu
Location: CHINA
Contact:

Re: [BUG] Newest Update (3.48.0) Opening File

#19 Post by ALINCO » 2020-05-29 07:26

Well going back to the old version is risk to me too . i ll stick on new version

uldiomf
500 Command not understood
Posts: 1
Joined: 2020-06-03 15:42
Contact:

Re: [BUG] Newest Update (3.48.0) Opening File

#20 Post by uldiomf » 2020-06-03 15:51

So, Windows 7 is officially dropped? :/ I guess I'll stick to older version.

User avatar
boco
Contributor
Posts: 25275
Joined: 2006-05-01 03:28
Location: Germany

Re: [BUG] Newest Update (3.48.0) Opening File

#21 Post by boco » 2020-06-03 16:32

Still fully works on 7.
### BEGIN SIGNATURE BLOCK ###
No support requests per PM! You will NOT get any reply!!!
FTP connection problems? Do yourself a favor and read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
### END SIGNATURE BLOCK ###

tom_brennan
500 Command not understood
Posts: 2
Joined: 2020-07-13 22:08
First name: Tom
Last name: Brennan

Re: [BUG] Newest Update (3.48.0) Opening File

#22 Post by tom_brennan » 2020-07-13 22:31

The problem is that as mentioned in posts above, Windows has two different associations for opening files - Open, and Edit. You can see these usually as the top two options when you right-click on a (text) file.

The Open settings are the default - what you get when you double-click on a file. You can change the Open settings (not as easily as before) via the Control Panel -> Default Programs.

There appears to be no way for users to change the Edit settings without editing the Registry.

So if you want to change the default text editor, the key you'll need to edit is:
Computer\HKEY_CLASSES_ROOT\SystemFileAssociations\text\shell\edit\command

And the value will be
"C:\Program Files (x86)\Notepad++\notepad++.exe" %1
or whatever your path to your favourite editor is

Given that the average Windows user is going to have trouble setting this up, it would make more sense to use the Open association, not the Edit one. I can see there's an issue with script files, but if we're talking about only using the Default Editor for text files, then the Open association would be fine.
2020-07-14 08_24_53-Settings.png
2020-07-14 08_24_53-Settings.png (17.45 KiB) Viewed 272 times

Cruiser07
500 Command not understood
Posts: 1
Joined: 2020-10-17 18:54
First name: Peter
Last name: Muthsam

Re: [BUG] Newest Update (3.48.0) Opening File

#23 Post by Cruiser07 » 2020-10-17 19:33

I struggle with the filetype association for photos (and other graphic files).
I am using Windows 10. Default app for photos (all common graphic file types) is IrfanView (Settings -> Apps -> Default apps).
I would expect that FileZilla is using this app for View/Edit of JPG files.

However, when I open a remote file with View/Edit, the popup "No program associated with filetype" appears.
And the first option 'Use system association' is totally weird: it is the ancient MS Paint: C:\WINDOWS\system32\mspaint.exe %f !!
How does that come? Where does FileZilla get MS Paint as system association from?

Interesting:
For local files, 'Open' is using the default app IrfanView. 'Edit' brings the "No program associated with filetype" dialog as well.

Why does FileZilla not use the default app, as per Windows systems settings.


Furthermore, I found that the FileZilla setting for Custom filetype association is case-sensitive. I must have two entries, for jpg and for JPG:
JPG "C:\Program Files\IrfanView\i_view64.exe"
jpg "C:\Program Files\IrfanView\i_view64.exe"
Is this a bug?

Post Reply