I became frustrated with WordPress about six months ago, while developing parts of Expecting Fan Web site. I cannot recall the problem, only that it annoyed me enough to spend two days learning about other Open Source content management systems.
First Drupal Site
I also studied Pro Drupal Development to understand how it all worked.
Everything improved eight days later:
starting 16 part Drupal/Eclipse tutorial
Because tutorial introduced me to Eclipse PDT, a wonderful integrated development environment for PHP programming language.
Problem Installing Eclipse
After a few crashes, I got Eclipse to work, by installing latest version of Java runtime. I did not want to replace my current version, but it was simple to point Eclipse to new version, starting it:
Eclipse has never crashed with newer Java.
Problem Installing Drupal Test Site
Before adding content, I wanted to be sure that my test site would not appear on search engines. Unfortunately, I could not find “privacy” among the dozens of Drupal administrative settings, or in “Database Table Reference” of Pro Drupal Development.
NOTE: Follow instructions on Disable RSS Feed? before adding content to a Drupal test site.
After 16 Days of Drupal
On April 5, 2009, I Tweeted:
My first Drupal site is up:
Unfortunately, my Tweet from the site did not work
I fixed the Tweet problem, by writing my own program to read and display my last Tweet, and added it to my Drupal and WordPress blogs.
My next Tweet was melancholy:
Trashed my Drupal database and test site is gone!
No, I have no idea what I did, but I knew I needed to learn more PHP. On April 10:
any suggestions for PHP book with function ref to replace php.net?
Nevertheless, I still liked Drupal, so I added “Convert blog to Drupal” to my lengthy “To Do” list.
Month of WordPress Updates
On July 13, I Tweeted:
only took 5 minutes to upgrade WordPress, but I am sick of it. Time to finish my Drupal book, and try something new
I have no idea how I did this, because it was never that fast again!
I am delighted to report that since Tweeting:
@wordpress please consider validating future releases with Eclipse so they load without errors http://tr.im/uOC5
Future releases have loaded without errors!
Unfortunately, updates introduced very annoying problem! “Screen options” on Administrative pages, stopped working. Tried Linux versions of Firefox 2 and 3, Opera 9 and 10.
I wish WordPress would offer an option for a simpler Administrative theme, where all options are visible. Has anybody besides the developers, ever used the Drag & Drop feature?
Anyway, these experiences induced me to tackle blog conversion.
My Last 29 Hours of Drupal
Notes and comments from my experience converting Where Did My Brain Go? from WordPress to Drupal:
- optimized WordPress database with disable revisions plugin before export
- installed Drupal, and followed instructions on Disable RSS Feed?
- selected WP2Drupal module to convert database to Drupal
- edited WP2Drupal to: connect nodes with taxonomy terms fails due to lack of $node->vid
- WP2Drupal ignored WordPress slugs, and created links from titles — most links worked
- Needed to:
- review 300 links to correct changes
- Learn how to filter content types, to maintain current structure
- Tried Blueprint CSS Framework, used by Blueprint Drupal Module. Even includes validator! But was hesitant about having to learn Ruby Programming Language to understand how it worked. Finally came to senses after reading “Help me!” messages in Blueprint CSS : Google Groups. I would not benefit enough from replacing:
How To Try WP2Drupal Now
I installed these Drupal modules before converting database:
- Advanced Help
- Content Management Filter
- Global Redirect
- Path Redirect
- Root Candy (great Administrative theme)
- Taxonomy Redirect
I recommend Drupal to anyone who wants to start a new blog, knows PHP programming language, and is willing to read Pro Drupal Development to understand how Drupal works, and to learn how to write Drupal modules.
Drupal should assign volunteer to update WP2Drupal module so it creates uses existing links in WordPress slugs, instead of creating new ones from titles. Drupal should make it easy to convert WordPress blog to Drupal, if it wants to become more popular.