Ok maybe this is a known problem, or maybe I've got a setting wrong somewhere, but I have to say that using FileZilla to transfer my DNN files has completely screwed me up.
I downloaded the 4.4.1 upgrade thinking to myself, "this should be easy enough." Despite the fact that I had trouble finding a walkthrough to go from 4.3.4 to 4.4.1, I figured that so long as I backed everything up prior to messing around with stuff, I could at least go back if things didn't go right.
So that's what I did - just as I have countless times before, I logged in using Filezilla, this time dragging my entire file structure down to my local hard drive. It was huge--so I told it to open 10 consecutive connections.
After that, I FTP'd up the 4.4.1 files. What I didn't realize though, was that my backup was fatally flawed. About 75% of the files I transferred were bad. Something must have gone wrong with the multiple connections because file "a" had file "b"s contents in it, or vice versa, or both, it was completely random. And of course, when I uploaded the 4.4.1, it did the same thing (of course I didn't know that though).
Aaaaand of course when things didn't work and I wanted to restore, it did the same thing. So it compounded itself and I was left with a completely f'ed up system.
So I'm working it out with the folks at WH4L. I tried their web-based 4.4.1 install but I won't bore you with those issues - I'm just fed up at this point. They offered to upgrade me to 4.4.1 for $29.99 and I guess I should have taken them up on it! The only saving grace in this whole mess is that my database is still intact, but my \portals folder will probably need some love and attention. I can only hope at this point that they can do a fresh install and pour in my \portals folder and db.
This is a rant but also a warning to the community - verify your transfer if you're moving a mass amount of files with FileZilla and have the multiple connections setting turned on. I know from now on that if I'm moving > 1 file in my queue, to switch that bad boy off.