Associated Command Failed
Moderator: Project members
-
- 500 Command not understood
- Posts: 4
- Joined: 2015-01-15 19:32
- First name: Fox
- Last name: Poole
Associated Command Failed
The first time I use the edit command to launch my editor it works fine. If I attempt to launch it again for the same file I get the following alert box:
The file 'C:\[folder]\[folder]\[file].html'
could not be opened:
The associated command failed
Any ideas or recommendations? Thanks
This just started with version 3.10.0.1
The file 'C:\[folder]\[folder]\[file].html'
could not be opened:
The associated command failed
Any ideas or recommendations? Thanks
This just started with version 3.10.0.1
Re: Associated Command Failed
Which program are you opening the file with? What is the associated command?
-
- 500 Command not understood
- Posts: 4
- Joined: 2015-01-15 19:32
- First name: Fox
- Last name: Poole
Re: Associated Command Failed
I use Notepad for HTML editing.botg wrote:Which program are you opening the file with? What is the associated command?
-
- 500 Command not understood
- Posts: 4
- Joined: 2015-01-15 19:32
- First name: Fox
- Last name: Poole
Re: Associated Command Failed
I reset the location of Notepad in the settings. But that did not work.FoxMuldr wrote:I use Notepad for HTML editing.botg wrote:Which program are you opening the file with? What is the associated command?
Re: Associated Command Failed
Check if the Notepad task properly closes after the first time.
No support requests over PM! You will NOT get any reply!!!
FTP connection problems? Please read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
FileZilla Pro support: https://customerforum.fileZilla-project.org
FTP connection problems? Please read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
FileZilla Pro support: https://customerforum.fileZilla-project.org
Re: Associated Command Failed
I have the same problem with FileZilla 3.10.x and using any editor, whether or not the editor task is closed. Started from version 3.10 (3.9.0.6 was fine).
Found several bugreports too: http://trac.filezilla-project.org/searc ... on&wiki=on
Found several bugreports too: http://trac.filezilla-project.org/searc ... on&wiki=on
-
- 500 Command not understood
- Posts: 4
- Joined: 2015-01-15 19:32
- First name: Fox
- Last name: Poole
Re: Associated Command Failed
I have found as a work around to [check] the 'Finish Editing and delete local file' and it will open again without error (only if you made changes). In the previous version if you didn't check it you got a warning to overwrite it. This version gives you the command fail error.Mardu wrote:I have the same problem with FileZilla 3.10.x and using any editor, whether or not the editor task is closed. Started from version 3.10 (3.9.0.6 was fine).
Found several bugreports too: http://trac.filezilla-project.org/searc ... on&wiki=on
- Dougmc
- 500 Command not understood
- Posts: 5
- Joined: 2012-08-02 14:15
- First name: Doug
- Last name: McLean
- Location: UK
Re: Associated Command Failed
Same problem here. Happens on 3.10.0, 3.10.1 and 3.10.2. Using Windows 8.1 64bit.
My file editing settings are:
- Default editor: Use system's default editor for text files
- Always use default editor
- "Watch locally edited files and prompt to upload modifications" is ticked
Under "Filetype associations" I've set it to inherit the system's filetype associations and there are no custom associations.
My system's default editor for text files is UltraEdit.
My file editing settings are:
- Default editor: Use system's default editor for text files
- Always use default editor
- "Watch locally edited files and prompt to upload modifications" is ticked
Under "Filetype associations" I've set it to inherit the system's filetype associations and there are no custom associations.
My system's default editor for text files is UltraEdit.
What the hell is a jigawatt?
Re: Associated Command Failed
Same problem too, if anyone can help :/
Re: Associated Command Failed
A fix for this is already in the repository.
Current workarounds are to either use remote file editing or to always unedit the file prior to editing it again.
Current workarounds are to either use remote file editing or to always unedit the file prior to editing it again.