Thursday, 30 April 2009

Urgent Drupal Security Update

Ok, so after spending most of yesterday swearing under my breath at my Drupal test site trying to get the getID3() module to install properly I arrived at work today to discover it had fixed itself while I was away. Well, more likely is that my cache had cleared and my attempts to fix the problem were finally visible but it was annoying none-the-less.

So then I get told to run "Cron" (which is what searches for updates on your behalf I believe) and discovered an URGENT SECURITY UPDATE!!! needs to be made to my drupal site. I have to say, I am going through the instructions and it does seem rather labour intensive. So much so that I think I must be reading the instructions wrong. The go something like this :

Step 1. Make a back up of everything (common sense so far)
Step 2. Turn off all of the custom themes and modules that you spent hours, nay make that days of your life trying to get to work in the first place.
Step 3. Delete pretty much your entire site and upload the new version
Step 4. Re-Upload and turn back on all of the themes and modules that you spent hours, nay days, getting to work as mentioned grudgingly in step 2.

There must must be an easier way than this. I am making this hard work, surely?

Anyway ... I've just completed step 3. I'll keep you posted.

UPDATE: It worked, my drupal site didn't die and all is well in the world.

1 comment:

  1. It's easier if you follow the best practices, i.e. keep all contributed modules and sites files in the sites directory and core outside this directory.

    ReplyDelete