Comments on: WuhWuh 0.1 Demo http://weblogtoolscollection.com/archives/2004/02/29/wuhwuh-01-demo/ Weblog Tools Blogging Tools Blog Tue, 06 Jan 2009 12:38:32 +0000 http://wordpress.org/?v=2.6.5 By: Mark http://weblogtoolscollection.com/archives/2004/02/29/wuhwuh-01-demo/#comment-175 Mark Sun, 29 Feb 2004 21:17:22 +0000 http://weblogtoolscollection.com/archives/2004/02/29/wuhwuh-01-demo/#comment-175 Matt (and everyone else), WuhWuh consists of the WordPress core and IS NOT a fork. It is an extension to make WP hacks more within the reach of some people. It is a "fully hacked" version of Wordpress. The database presently contains a few extra tables and entries for various hacks. There are three directions that I could take with it. I could try to either import those changes into an existing WP database (as one big chunk, one step in the install process, a bit of extra time coding those changes as an SQL import). My second option is to provide an "import" script from an existing WP database into the WW database, which would retain those extra options. Lastly, I could offer this ONLY as a new install (which I am leaning towards for the first version). Once the database is populated with entries and the changes from the hacks are in place, any upgrade of the database would retain those changes and WordPress will be intact. The goal of this mess is that in case of any upgrade being performed, either through a direct WordPress upgrade, or through a WW upgrade, the process is seamless and does not break anything. Any suggestions in this regard will be very appreciated. Matt (and everyone else),
WuhWuh consists of the WordPress core and IS NOT a fork. It is an extension to make WP hacks more within the reach of some people. It is a “fully hacked” version of Wordpress.

The database presently contains a few extra tables and entries for various hacks. There are three directions that I could take with it. I could try to either import those changes into an existing WP database (as one big chunk, one step in the install process, a bit of extra time coding those changes as an SQL import).

My second option is to provide an “import” script from an existing WP database into the WW database, which would retain those extra options.

Lastly, I could offer this ONLY as a new install (which I am leaning towards for the first version). Once the database is populated with entries and the changes from the hacks are in place, any upgrade of the database would retain those changes and WordPress will be intact.

The goal of this mess is that in case of any upgrade being performed, either through a direct WordPress upgrade, or through a WW upgrade, the process is seamless and does not break anything.

Any suggestions in this regard will be very appreciated.

]]> By: Mark http://weblogtoolscollection.com/archives/2004/02/29/wuhwuh-01-demo/#comment-174 Mark Sun, 29 Feb 2004 21:03:59 +0000 http://weblogtoolscollection.com/archives/2004/02/29/wuhwuh-01-demo/#comment-174 Actually, that is something that completely slipped my mind. I should have done it that way and will change it to the wp-style switcher directory structure before release. Actually, that is something that completely slipped my mind. I should have done it that way and will change it to the wp-style switcher directory structure before release.

]]> By: Matt http://weblogtoolscollection.com/archives/2004/02/29/wuhwuh-01-demo/#comment-173 Matt Sun, 29 Feb 2004 19:25:18 +0000 http://weblogtoolscollection.com/archives/2004/02/29/wuhwuh-01-demo/#comment-173 Does an "importer" mean that a WW database is not compatible with WP? Are you planning for this to be a fork or more like WP-enhanced? Does an “importer” mean that a WW database is not compatible with WP? Are you planning for this to be a fork or more like WP-enhanced?

]]> By: Alex http://weblogtoolscollection.com/archives/2004/02/29/wuhwuh-01-demo/#comment-171 Alex Sun, 29 Feb 2004 18:16:59 +0000 http://weblogtoolscollection.com/archives/2004/02/29/wuhwuh-01-demo/#comment-171 Any reason you're not using the wp-style directory name like I did with my style switcher? It would be nice (for the users) to have one standard... Any reason you’re not using the wp-style directory name like I did with my style switcher? It would be nice (for the users) to have one standard…

]]>