On Wed, Nov 25, 2009 at 8:33 PM, Velda <[email protected]> wrote: > http://codex.wordpress.org/Writing_a_Plugin > > If you use the plugin route rather than manual code edits, the automated > update tool works quite well and can save you oodles of time. At worst, > you may have to temporarily disable a plugin after an upgrade until you > can figure out a fix, but at least you /can/ do that quite easily.
Agreed, don't hack core WP files. WP has a huge list of actions and filters that allow plugins and themes to modify data without touching the core code. The other thing to keep in mind when writing PHP for plugins/themes is to stick with WP APIs as much as possible (there are APIs for all sorts of things so this isn't hard), quite a bit of effort is made to make APIs compatible between versions. There are lots of examples in the WP Showcase of sites using it more as a CMS - http://wordpress.org/showcase/tag/cms/ -- Joseph Scott [email protected] http://josephscott.org/ _______________________________________________ UPHPU mailing list [email protected] http://uphpu.org/mailman/listinfo/uphpu IRC: #uphpu on irc.freenode.net
