Translate This Page
About the Author
- Mark Ghosh
An avid fan of business, education, technology and finance. I lead a lean, highly focussed and capable team of Java Back End developers and Front End developers through a maze of complex software wizardry to fulfill the web maintenance needs of a large chemical manufacturer. As per Myers-Briggs Personality Types, I am an ESTJ. I pride in a project completed on time and according to plan. My hobbies include all kinds of technology, anything that I can taste and anything that goes fast or flies in the air. I like to read business books and comics in my spare time.
Categories
- bbpress
- Best of WordPress
- Blog Templates Blog Skins Blog Themes
- Blogging
- Blogging Essays
- Blogging News
- brainstorming
- buddypress
- Business of Blogging
- CMS
- Code
- Cold Fusion
- Community Interviews
- Cool Scripts
- General
- HOW-TO
- LinkyLoo
- Movable Type Plugins
- Photolog Script
- Podcasting
- QuickLinking
- Spam
- SXSW
- TLA
- Tutorials
- User Reviews
- Web Design
- Web Ethics
- Weblog Add-Ons
- Weblog tools blog tools blogging tools
- Weekly Plugin Review
- WLTC Community
- wordcamp
- WordPress
- WordPress Discussions
- WordPress FAQs
- Wordpress for Beginners
- WordPress Hack
- WordPress News
- WordPress Plugin Competition
- WordPress Plugins
- WordPress Polls
- WordPress Security
- WordPress Templates WordPress Skins WordPress Themes
- WordPress Tips
- WordPress Tools
- WordPress Troubleshooting
- WordPress Weekly
- WordPress Widgets
- WordPress WishList
- XHTML Tips
Obviously Powered by WordPress. © 2003-2013
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…
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?
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.
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.