« upgrades! | Main | Old knowledge makes for bad articles »
Minor suexec issues. So we'll see how great 4.2 is I suppose.
Posted by John C. Welch at 20:57 | Permalink
Comments
Sorry for all the frustration with the upgrade, and I know the suexec stuff didn't make it any better. It *should* just be a case of dropping the new files on top of the old ones -- was there something that made that more complicated than usual?
Posted by:
Anil Dash 
|
August 14, 2008 10:37 PM
The problem is, you can't just drop root-level folders on things, so you end up having to verify every folder, and then drop them individually, or just their contents. It's astoundingly tedious.
I've yet to understand why that hasn't been automated. I mean, it's de riguer for almost every application you use. I don't see why Movable Type can't have an "upgrade" button that looks at the config file to get the blog root(s) and handles this more elegantly.
Yes, highly customized setups would still require a lot of manual work, but at least there'd be the OPTION of having it be easy.
Posted by:
John C. Welch 
|
August 14, 2008 11:20 PM
Oh, and for some reason, the only blog settings I can use are "general". If I try to hit any of the others, it goes to "General".
Posted by:
John C. Welch |
August 14, 2008 11:21 PM
Hmm. I'm not sure I follow "you can't just drop root-level folders on things". What are you using to copy over your files? Most of my updates, I just, well, drag the new version on top of where the old one was. If it were a manual thing like you're saying, yeah, that'd be hellish -- maybe we can help troubleshoot! :)
The reason it's not automated is, basically, security. If MT could write over its own files, then others on your server (assuming you're on shared hosting) could do so, too. It's wildly insecure, and it's the kind of thing that's the reason MT doesn't get hacked and other blogging tools literally get exploited every other week. (No exaggeration.)
That being said, if we can find a better tradeoff of security-vs-convenience, we'll definitely keep plugging away at it.
The settings thing is completely baffling. I haven't heard of any issues like that, but it makes me wonder if a CSS file or some individual script didn't get copied over correctly. Which, you know, would be quite possible with the awful one-folder-at-a-time thing you were describing. Drop me a line either way if we can give you a hand.
Posted by:
Anil Dash |
August 15, 2008 3:17 AM
The problem is, there's no way I can see to say, set up plugins and other things outside of the main MT hierarchy. So if you start adding custom bits, that upgrade goes from D&D to D&D&D&D&D&D&D&D&D
As well, there are ways of dealing with the security issue. SSL, etc. Besides, um...prior to forcing MySQL, your own support was telling people that huge chunks of the MT Hierarchy had to either be world-writable, or set the group to WWW. That was so not fun from a security POV.
The pointis, I know people back on early verions of 3.x not because 4.x has no compelling upgrade reasons, but because the upgrade is just so damned tedious.
As far as the settings thing goes, I don't even begin to know where to look in the heirarchy for it. I'll google it a bit, and see if anyone in the .org forums has a hint.
Posted by:
bynkii |
August 15, 2008 9:55 AM
