Update: All of this configuration is now available with my Drupal Template installations.
This is a list of the standard stuff I do when I initiate a new site.
Install drupal with drupalDeploy.sh
This sets everything else up for ease of future maintenance, etc.
Install standard contributed modules.
for mod in admin_menu advanced_help ckeditor imce cck views pathauto token; do drupalGitDeploy.sh -noconfirm install module $mod <site> done
The CKEditor requries the library be installed:
I followed all the steps:
When backing up my laptop, the technique I use most often is to back it up to an encrypted disk partition. I do this because I don't have to control access to the backup media. Sometimes this takes the form of a USB hard drive I use for other things. Sometimes it's a remote file store not under my exclusive control (like the DreamHost 50G backup account). Using a large file holding an encrypted filesystem image, I can let my backups live anywhere.
I have come up with a standard, scripted method of using these encrypted filesystem files. See the comments in the script below for more information on how to initiate the filesystem and use the script. Note the script is attached below for your downloading convenience...
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
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.
Note: this was written before the upgrade of my Drupal Scripts Library to use Drush rather than CVS (or Git). See my post on this subject.
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. Some sites I found notable:
Note the following conventions used below:
Let's get started!
I looked into web log reporting on DreamHost the other day. DreamHost provides web log stats system called 'Analog'. It's a) not the nicest system out there (I think it's cruder looking that Webalizer) and b) it is only accessible via the url 'domain/stats'. Because of this, it requires munging (drupal specific) of a site's .htaccess file (if it exists) or creating on (if
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.