Custom Query (8117 matches)


Show under each result:

Results (31 - 33 of 8117)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
Ticket Resolution Summary Owner Reporter
#10153 rejected Error to process queue files. Agiper

Processor: Intel Core I7 3770k 3.50GHz

Seems that there is an error in the last version

When there are 2 or more files to upload in queue, the first file is uploaded successful but the upload of second file and the others fail.

I tested upload the same files using other ftp client (Core FTP - ) and all files of queue where uploaded without error.

I attached a txt file of Filezilla log with the error message.

#11769 rejected "Watch locally edited files" feature does not update its link when the remote server is changed Airacobra

When the Watch locally edited files and prompt to upload modifications feature is turned on, it does not update its links when the remote server is changed. This may lead to overwriting a wrong remote file.

Consider the following scenario:

  1. Connect to server A.
  2. Download file X from server A to a local folder.
  3. Edit the file X (right-click it in the local folder and select Edit).
  4. Do some edits, save the file, close the editor and return to FileZilla.
  5. You are prompted to upload modified file back to remote server A (so far so good).
  6. Select ‘No’ to close the prompt.
  7. Connect to server B.
  8. Download file X from the server B to the same local folder as in step 2.
  9. Open the new file X in your editor.
  10. Do some edits, save the file, close the editor and return to FileZilla.
  11. Now, you are prompted to upload modified file X back to remote server A!

That is wrong because the file was downloaded from server B and should be uploaded there. If you do not read the prompt carefully, you can easily overwrite the file at the wrong remote server. FileZilla should update its internal link when the monitored file is downloaded from a different location.

#8224 duplicate z/VM: Unable to analyze the returned directory Alain


FileZilla Client

Version: 3.5.3

Build information:

Compiled for: i586-pc-mingw32msvc Compiled on: x86_64-unknown-linux-gnu Build date: 2012-01-08 Compiled with: i586-mingw32msvc-gcc (GCC) 4.2.1-sjlj (mingw32-2) Compiler flags: -g -O2 -Wall -g -fexceptions

Linked against:

wxWidgets: 2.8.12 GnuTLS: 2.10.4

Operating system:

Name: Windows NT 6.1 (build 7601, Service Pack 1) Version: 6.1 Platform: 64 bit system

Statut : Connexion à Statut : Connexion établie, attente du message d'accueil... Réponse : 220-FTPSERVE IBM VM Level 540 at, 14:27:57 EDT SATURDAY 2012-09-08 Réponse : 220 Connection will close if idle for more than 5 minutes. Commande : USER anonymou Réponse : 230 ANONYMOU logged in; working directory = /../VMBFS:DWSYS:ANONYMOU/ Statut : Connecté Statut : Récupération du contenu du dossier... Commande : PWD Réponse : 257 "/../VMBFS:DWSYS:ANONYMOU/" is working directory Erreur : Impossible d'analyser le chemin retourné. Erreur : Impossible de récupérer le contenu du dossier

With a previous version of filezilla we have at work, I can do what I want. Now with this one from home I can't... The deal is to send windows files to a z/VM mainframe. The target is BFS file architecture.

Able to test/send anything you ask me.

Regards Alain

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.