Zugg Software :: View topic

Wizard Joined: 15 Jan 2002 Posts: 1644 Location: USA

Ok since I can't reach the bug rep software and I need to post this before I forget its going here so HA! (will post to mantis when It available)

#FTP great concept lots a bugs :P so here goes

1. Wrong pass/user/address?
#FTP open ftp.com user wrongpass
Displays failed to connect box clicking ok closes box and disconnects but cursor stays an hourglass until you open a diff window //settings, #FTP,#mapquery, #window name etc....

2. After sucessfull connection
#FTP getedit filename.ext
Downloads the file (verified from ftp log) but fails to open the editor and display it.

3. DLing and saving a file to an absolute location
#FTP get filename.ext c:\filename\blah.ext
Saves the file as blah.ext the current char dir.
However relative from char dir works.
#FTP get filename.ext ..\blah.ext
saves blah.ext to the parent folder of the char dir (usually zmud root)

4. Trying to retrieve a non existent file (buggiest)
#FTP get nofile.ext
Produces zmud parse error TProgressBar property out of range. (hourglass problem from above) From then on #FTP [commands] produces parse errors. opening the FTP window and clicking abort doesnt seem to work eventually after fiddling around with other #FTP [commands] it displays a transfer complete box and creates an empty nofile.ext file, Also you cannont connect disconnect etc as it produces TProgressBar errors and the only way to use #FTP again is to restart zmud Failure to restart zmud causes all kinds of funny errors when trying to use #FTP. Non existent files should be handled gracefully with no parse error popups and pref with an echo of file not found

5. #FTP various display bugs and or hard to reproduce bugs
when overwriting a file on local 0 byte text size is reported
occaisonally it doesnt display the connection line sometimes just not the addy using #ftp open; ftp connection to
doesn't always display close line when when using #FTP close (most notably when stacking ftp commands with ;) #ftp open;#ftp list;#ftp close
#FTP open with no other arguments creates a lastconnection and connects to my ftp server in zftp.ini with a blank addy Im not sure how this is supposed to work as I am using a local and not a remote ftp server but it would be nice if instead of creating a new last user it just used the current lastuser

6. #FTP Ideas!!!! this is the fun part :P
#FTP read file.ext
Similar to #READ but reads from the ftp file
more to come (I had more but I forgot them).....

Posted: Wed Oct 20, 2004 2:31 am

Thanks for the details on this. Definitely put each item into Mantis as a seperate item so I can track them. But in general, here are the development comments on the #FTP in zMUD:

Only relative paths are supported. This is a security addon in zMUD. The #FTP command is only meant for use for MUDs and for files relative to the zMUD directory. It is not meant as a replacement for a full-fledged FTP client. After all, I use FTP Voyager here and I paid something like $40 for it. For your $25 zMUD you shouldn't expect such a robust client.

As you found, there is little error support. There also isn't any proxy support. The main purpose of #FTP was for those MUD admins that need to read a file quickly, edit it, and return it to the server.

The "#FTP getedit" command seems to work here. It's possible that one of the other commands got it into a wierd state, so always try this from a fresh MUD window (press ESC to open a blank window) and test from there.

Also, if you can, test with more than one FTP server. There are lots of different types of FTP servers out there and zMUD just follows the strict FTP protocol and doesn't attempt to handle any server that might be a bit odd. I've only tested it against the standard FTP server on linux (Fedora).

But go ahead and put these into the tracking system so that when I have time in the future I can smooth some of the rough edges.

Wizard Joined: 15 Jan 2002 Posts: 1644 Location: USA

Bugs reported!