Modern web site software - like Drupal - simply provides a web-based front end to a database. For a traditional web site, the front end retrieves articles and formats them on HTML pages. A more sophisticated web site allows more sophisticated access to the database.
If we embrace this vision, we build a new web site by importing databases. On Drupal, that means we use the Feed Importer. I have finally gotten the Feed Importer to work, after several hours of banging around.
A couple of months back I attended DrupalCamp Twin Cities, to try to improve my understanding of Drupal. It was a good event and, thanks to an enlightening talk by Tess Flynn, I now see how the incoming path is converted into code execution.
This week I took the next step: I wrote the simplest possible Drupal 7 module from scratch. Although I had several examples to work from, it took several attempts to get things right. And now, here it is: Rick's Testie Drupal 7 Module (zip file).
Drupal 7 was released for "production" a little over a year ago at the Drupalcon Chicago. Upon returning from that event, I put a week or so into trying to convert from Drupal 6 to Drupal 7. This produced a series of disappointed-sounding blog entries as my attempts failed. I kept trying every few months, hoping that a new D7 release, or an improvement in my Drupal skills, would yield success.
I've finally succeeded.
I implemented an AMP stack on my Mac. "AMP" means "Apache," "MySQL," and "PHP;" it required me to install MySQL and hook it all together. Then I moved the laborious conversion process to my desktop. My efforts succeeded a few weeks ago, but I was stymied when I tried to deploy the converted site onto my GoDaddy hosting. I finally tracked the problem down - where else - in the .htaccess file defaults.
I've migrated to the Danland Drupal theme. Danland is stable and it looks great right out of the box. Moreover, I find I have trouble with themes that use a dark-color background instead of a light or white one. The off-color looks fine when things work well, but fails miserably when anything goes wrong. I'm enough of a tinkerer to appreciate expressive error messages.
I took my site off line for roughly 24 hours as part of the Net-wide strike against impending US Congressional action. As a published author I applaud efforts made to protect my income from piracy. However, the current legislative efforts put the operation and culture of today's Internet at risk. They also undermine the concept of due process.
I've just spent an unsatisfying weekend with Drupal 7. I made several unsuccessful attempts to upgrade from Drupal 6.20 to Drupal 7. Although I had carefully built a copy of my active site, and tried to experiment only with that site, the side-effects managed to damage the live site as well.
Will Norris is working on a revision to OpenID for WordPress. This is good, and I have some observations and suggestions. At the moment the OpenID plugin works pretty well - I have separate logins delegated through domains I own. I routinely log in through OpenID for both routine and administrative activities.
This is more of a reminder to myself - you can enable SSL on WordPress, but it's essentially an undocumented feature. This afternoon all I could find was a forum posting on enabling SSL.
There doesn't seem to be genuine documentation on it in the Codex, at least, not documentation that pops out when you do a search.