[wp-hackers] 1.2.2 Failing on fresh install.

[Mark Jaquith]

When you upgrade to 
the-next-version-of-Wordpress-whose-name-is-still-undecided, you should 
move your setup to use themes.  That way NONE of the core files are 
modified. I can't tell you how great it is to just be able to select all 
the files in a new nightly and just drop them in FTP, letting them 
overwrite without worry.

Kimmo Suominen wrote:

>
>People like me take a look at the index.php that comes with WP and then
>plug in those functions into their own index.php (or some-other.php)
>files.  This allowed different looks and different mixed functionality
>on a page before templates, pages and plugins were there.
>
>So, if the WP code gets automatically updated, unless it stays very
>backward-compatible, it would easily break the custom PHP files.
>
>I'm not saying automatic updates are a bad thing -- actually, I think
>they are a good thing.  But I think I think that it needs to be an
>option, or maybe a plugin (if we are not to have new options).
>
>If I ever get all my stuff migrated to templates and/or plugins, I'd
>probably be very happy with automatic updates (although I see how it
>could also break plugins).
>
>Until then, I'd probably feel more comfortable running "cvs update"
>manually when I know I have time to deal with any fallout.
>
>Allowing both update methods would be great.
>
>Regards,
>+ Kim
>  
>