Prior to the latest patch, I had a few interruptions during upload, but since its installation they appear to be worse. It's taken me about 2 hours to upload some relatively small galleries - it will do between 5 and 20 files and I then get the above error message. Additionally, a particular html file would not upload at all - I tried about 5 times, each time being told that the file had been uploaded successfully (not that it hadn't been necessary to upload). Looked at 'Site Maintenance' - wasn't there. Tried to upload the file through Filezilla, uploaded first time.
I've spoken to my webhost to try to determine why this was happening, but let's say I didn't have much success, and have also done a web search from which I gleaned that some who are affected by this error have discovered that a file is being deleted on upload (I thought it was a 'permission' thing, but that's about as far as my knowledge in that area extends!).
Does anyone know how to resolve this issue, please, as it's too time-consuming for words at the moment!
The FTP error code you have submitted has got me a little baffled at the moment but I will try and find the solution for you.
Normally the 200 series means the requested action has been successfully completed, its the set to I which i havent come across before, i've seen the set to A mode which ended up being a passive mode port configuration issue, but leave it with me half an hour or so and I'll liase with my networking guy who may have a better answer than me (that's unless someone else beats me to it in the meantime)
I noticed this today with an .swf file. It uploaded on the second attempt, despite WP saying it had the first time. Not seen this before. There was no error message and it didn't take any longer than usual, though.
Had no problem with .swfs, mainly just .jpgs, but obviously the same issue. Did experience it before, but far worse since latest patch. The actual uploading speed was no different - it was all the pauses for the server to resume at best, and at worst for WP to restart after crashing! No issues at all through Filezilla. Hey ho!
Well at least it's what I thought it maybe, the set to I mode means set to Binary Mode, Binary Mode is used when the server or clients ftp program see's files that can't be translated to text-files (at least not in a safe manner), so if downloading the client program switch's to binary mode (TYPE I) from text mode and if uploading the server does the same thing, because they both know the rules of ASCII (text) transfer its safer to let them do the conversion from ASCII to Binary automatically. What I still can't fathom out is why you cant upload if the server has been working fine previously.
As a stupid question, what did you ask your hoster and what was his response because as far as I can see from the information we have already, its certainly looking more like server side than client side to me.
Damn it, didnt see that part of your post, if no issues with FileZilla then it can only be the FTP program within WPX2 not doing the switch correctly, drop support a line Vicky and give them an ear bashing, maybe something they have done in the last patch has screwed this part of the program up even more. I personally never use it at all no matter what sites I build, I'll stick to my old faithful of FlashFXP.
Thank you for both your responses. Yes, I am confident it's the FTP within WP, particularly now you've explained the error message. With other programmes, I can happily watch it changing from binary to ASCII automatically and there has never been an issue. The person I spoke to at the web host didn't have it on his list of answers. Went through all the normal patter about had I a firewall and anti-virus installed, to which I answered yes, but it had not previously been an issue. I will report it to Serif tech support, but, on past experience, they'll only tell me to uninstall the programme, clean the registry and reinstall it, or similar procedure! WP would be a great programme if all the integral bells and whistles worked satisfactorily!
I've been reading a lot of techie web sites and concluded...
This is actually two separate mesages that look like one.
FTP error means that the server experienced or received an error of some kind in the previous file/data transfer from your computer going to the server. Maybe corrupt data, maybe incorrect file type as related to a previous TYPE command...
Whatever the cause, the server wasn't happy with the previous TYPE command from your computer, and the subsequently received data file.
Type 200 set to I means the server has changed the "type" of file transfer from whatever mode it was in (binary or ASCII) to Image (probably in binary). The 200 means the "type" change was successful.
OK, make that three messages FTP error and type set to I and 200
Because it has been reported that using FileZilla apparently successfully uploads the same web site to the same server after doing a local publish, but using WP X2 to upload occasionally fails, I'm speculating that WP is occasionally either:
1. sending the incorrect "type" command prior to sending a certain file, or...
2. sending a malformed file which the server then interprets to be a image (binary) file, and therefore the server changes the type.
Solution #1 seems to be... try using WP again.
Solution #2 seems to be... publish to disk if #1 (still) doesn't work, then use some FTP client like FileZilla to upload.
Solution #3 seems to be... file a bug report with Serif, and have available a WPP and supporting asset files that results in the error during uploading.
OR... I could also be sooo waaaaaaaaay wrong with the above that the best thing to do is ignore this entire post.
Jim B. :> )
There was a time when I thought I knew it all. Now, I'm lucky if I can remember some of it.
Many thanks for the time and trouble you've gone to, both in exploring the problem and giving a clear explanation. I'd have done more reading up on it myself if I felt that (a) I would fully understand what I was reading - a little knowledge is a dangerous thing! - and (b) I hadn't wasted so much time on an already urgent job!
The conclusions you've drawn are entirely logical and confirm my suspicions. I will just have to go with the external FTP solution for the time being, as it's certainly quicker on the long run!
Thanks Ali. If you notice, I didn't say it was a new problem to me, just that it had become worse since the latest patch. I know it might appear that I set out to find problems with the patches, but I do install each one with renewed optimism, only to find that either a fresh problem has been introduced or a previously existing one exacerbated.