This is a list of the standard stuff I do when I initiate a new site.
Install drupal with drupalCVSDeploy.sh
This sets everything else up for ease of future maintenance, etc.
Install standard contributed modules.
I need to create an image gallery for the new Logan Square Walks website. I surfed around and this page seemed like the easiest approach for what I wanted -- a simple non-nested gallery composed of images that used a neato javascript-powered viewer.
I followed all the steps:
Yet another follow-up post to my post re upgrading from Drupal-5 to Drupal-6. This is a note about upgrading the CCK module. The module page has a very through discussion on need to update the CCK module before other modules. The easiest way to do this is to
Another follow-up to my post about upgrading from Drupal-5 to Drupal-6. This note is about the image module.
If upgrading a Drupal-5 site that utilizes the image module, and you follow my directions explicitly, you'll get an error when trying to update the image module.
Call to undefined function image_get_sizes()
See more about this issue here (there are several other duplicate issues linked from that one).
In my post about upgrading from Drupal-5 to Drupal-6, I said I'd post further updates about issues encountered while upgrading certain contrib modules.
Well, I had an issue upgrading the fckeditor module. I didn't write down the actual error message, but on the update, I received notice of an SQL error that mods to a table couldn't be made. Turns out some of the tables required by fckeditor never had been created.
I undertook the upgrade of this site, toddgee.com from Drupal-5 to Drupal-6. This assumes that a site was deployed using my Drupal Scripts Library (which makes the process MUCH easier.) In preparing this, I did a lot of surfing around to see others' instructions. I hit too many sites to link to them all, you can do the same Google search I did. Below is a list of instructions based on how I accomplished the task.
I just wrote a small script called 'bash_completion' that facilitates bash filename completion. It works with the Drupal Scripts Library to allow library scripts to use filename completion over installed sites.
Talks about Drupal's use w/in the 'lefty' political movement from the Dean-for-president campaign. Discusses about the origins of CiviCRM.
http://www.digidave.org/adventures_in_freelancing/2008/12/drupal-nation-...
At some point, I'd like to investigate setting up a full-bore web-fronted mailing list. Initially with the bikegeeks list, we discussed fronting the mailman list with a site so that users could sign up for the mailing list directly on the website. This (I guess) could be done with the 'Mailman Register' and 'User Mailman Register' modules (see refs #1 and #2) below. This would remove the necessity of sending the users off the site to sign up for the list and remove the necessity to interact with the primitive-looking mailman interface.
As a follow up to my posting about the my Drupal script library, I thought I'd write a bit about the installation techniques I've been using for Drupal installs.
As described in the script README file (and practiced by the drupalCVSDeploy.sh script), I create and maintain a particular installation system w/ all my Drupal site installations.