[wp-hackers] 1.2.2 Failing on fresh install.

[Kimmo Suominen]

My custom index.php lives outside the WP directory, so I can update WP
anytime.  There are no relevant changes to the core files.  But if
a function that I use gets removed from the core, my index.php would
stop working.  I'd want to be around when this happens, as opposed to
having it automatically happen unattended.

Now, I do have some modifications to core files, such as the fixes
to page caching by proxies and browsers, that haven't made it into
the CVS repo.

    ftp://ftp.gw.com/pub/people/kim/patches/wordpress/no-cache.diff

I don't no if they ever will make it in, but I need to keep them to
avoid old information from showing up on pages that have forms with
changing data (such as when writing a new post).

It is pretty easy to run "cvs update" and resolve the conflicts, if
any.  The point is that "cvs update" runs when I want it to, not
automatically (and therefore possibly unexpectedly).

Regards,
+ Kim
-- 
<A HREF="http://kimmo.suominen.com/">Kimmo Suominen</A>

On Sun, Dec 19, 2004 at 03:02:30AM -0500, Mark Jaquith wrote:
> 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
> > 
> >
> 
> 
> _______________________________________________
> hackers mailing list
> hackers at wordpress.org
> http://wordpress.org/mailman/listinfo/hackers_wordpress.org
>