[wp-hackers] 1.2.2 Failing on fresh install.

[Kimmo Suominen]

On Sun, Dec 19, 2004 at 12:28:46AM -0700, Chris Coggburn wrote:
> Kimmo Suominen wrote:
> 
> >How would this work for "embedded" WordPress like I think a lot of
> >people are still doing, i.e. custom PHP files calling WP?
> >
> Your going to have to explain that one a little bit more, because I 
> don't know what your talking about.

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
-- 
<A HREF="http://kimmo.suominen.com/">Kimmo Suominen</A>