New Upgrade - 11/27/06 Issues

[nprodan]

Prior to the last two upgrades for this weekend, this producted worked like a charm! Fantastic product!

So now we need to work on the kinks. And then we all need to contribute to you for making such a lovely product and with upgrades!

After it uploads successfully I get an error!

FTP Error: Upload Failed
CHMOD not supported

Yet in the script window below it says:
220 ProFTPD 1.2.9 Server (Main FTP Server) [web126.opentransfer.com]
USER user1
331 Password required for xxxxxxxx.
PASS *************
230 User xxxxxxxx logged in.
SYST
215 UNIX Type: L8
NOOP
200 NOOP command successful
CWD (name) Going TO (name of folder)
250 CWD command successful.
PASV
227 Entering Passive Mode (71,18,159,41,207,98).
LIST -a
150 Opening ASCII mode data connection for file list
drwxr-xr-x 2 (name, name) 4096 Nov 27 13:15 .
drwxr-xr-x 13 (name, name) 4096 Nov 26 16:17 ..
-rw-r--r-- 1 (name, name) 8251168 Nov 25 21:29 (nameoffile.ai
-rw-r--r-- 1 (name, name) 1440 Nov 27 13:15 (nameoffile.ai
-rw-r--r-- 1 (name, name) 10844018 Nov 25 14:42 (nameoffile.psd
-rw-r--r-- 1 (name, name) 5124892 Nov 25 14:40 (nameoffile.tif
226 Transfer complete.
NOOP
200 NOOP command successful
TYPE I
200 Type set to I
PASV
227 Entering Passive Mode (71,18,159,41,207,100).
STOR /(pathname/filename)
150 Opening BINARY mode data connection for /(pathname/filename)
226 Transfer complete.
SITE CHMOD 644 /(pathname/filename)
200 SITE CHMOD command successful
QUIT
221 Goodbye.

[brfransen]

I am having the exact same problem. 2.6.2 worked correctly with no error. 2.7 is changing the permissions of the file but I get the error sheet saying that it has failed and CHMOD is not supported.

[revolution]

I'm getting the same thing here too! It seems to be partially working as my blog is getting errors on it.

[ericdfields]

Getting a similar issue. Whenever I try to directly edit a remote file, it opens it in TextMate, but upon saving i get an error in Cyberduck telling me that another process is utilizing the file.

I had to get one of our developers at work to unlock the file... said vshell had a lock on it.

Hope that helps with the bug squashing.

Thanks

[ribit]

Not only am I getting the same error message, when I try to do a bug report (open a trouble ticket) I get an error message! Luckily I save the old version and will continue to use it, this is very disappointing for a piece of software I have loved in the past....

[The_Tick]

Not only am I getting the same error message, when I try to do a bug report (open a trouble ticket) I get an error message! Luckily I save the old version and will continue to use it, this is very disappointing for a piece of software I have loved in the past....

You probably haven't registered and logged in.

[LonLonRanch]

So yea, I'm getting the same thing and cant upload anything to my folders, kind of a problem. Has anyone figured this out yet?

[ericdfields]

The revision I've rolled back to is 2396, in case anyone is interested; it's been safe up until the 2.7 update. I'm going to test 2.7.1 (today's bugfix) to see if these issues were resolved yet.

[Laerm]

First off, thanks for Cyberduck, use it daily and have converted many fellow mac users

My problem: I've had a look around the FAQ and message board, as well as the preferences to no avail. Since 2.7, when duplicating a file, the date is added rather the the ~copy suffixe. Problem is, the slashes in the date means I can't save the file. Anyway to change the date format or simply add an option so we can choose the suffixe added when duplicating the file?

[dkocher]

Since 2.7, when duplicating a file, the date is added rather the the ~copy suffixe. Problem is, the slashes in the date means I can't save the file. Anyway to change the date format or simply add an option so we can choose the suffixe added when duplicating the file?

It takes the format specified in System Preferences > International > Formats > Dates > Customize... > Short. I was unware of the issue as I use a date format using colons seperating the numbers. Will fix this in the next revision (e.g. automatically replace slashes by colons.)