Drupal Core Upgrade – 7.26

This upgrade has come along pretty close to the heels of 7.25. But unless you want to see the warning message constantly, you’ll need to go ahead and put the upgrade in place.

I ran the usual procedure you can find by search for the word “upgrade” on this blog and experienced no issues at all.

Core Upgrade – 7.21 to 7.22 procedure for Centos 6.3

Looks like it is that time again. I’ll be upgrading the Core to 7.22 today. Sand first then prod.

This is the procedure that I am using. I have used it for three previous core upgrades and have never had a problem. Note that I am running Centos 6.3 on both core and sand. I have updated it for this post as well.

  1. Back up everything
  2. Download the new core file
  3. Put site into maintenance mode
  4. Place it on the server and extract all the contents to /var/www/upgrade/drupal-7.22
  5. In the newly extracted files delete the sites directory and all its subs. This is done because the upgrade is not going to replace anything in this directory
  6. From a terminal window type:          yes | cp -r /var/www/upgrade/drupal-7.22/* /var/www/html
  7. Note that the destination folder of html is my doc root and all the drupal folders/files are located right underneath this. the yes | cp…. prefix is to let the system know to overwrite everything in the destination. since sites is the only directory that we want to keep and we have removed it from the source, this will be fine.
  8. Run update.php by navigating to http://…yourdrupalsitename/update.php
  9. Follow the instructions for this closely
  10. Navigate to reports, available updates and check the version of your core
  11. Take the site off of maintenance mode
  12. Check different things on the site to ensure a smooth upgrade has occurred.
  13. That should just about do it.

The Sand upgrade is completed. No issues. Proceeding to Prod.

Prod upgrade is complete. No issues.

Production Change Request – Upgrade Drupal Core from 7.18 to 7.19

  1. Follow procedure outlined in the previous post. 
  2. Upgrade installed. Tested in Prod
  3. System is back online, available and healthy.

Procedure – Upgrade Drupal Core from 7.18 to 7.19

Please note that this procedure has been written for my specific situation. I believe that it is applicable to others and may provide insight to your situation but it will most likely not match what you have exactly so please be cautious. Back things up and test in a dev/qual environment first! I have just finished it in Quality and it works fine.

  1. Back up everything
  2. Download the new core file
  3. Put site into maintenance mode
  4. Place it on the server and extract all the contents to /var/www/719/drupal-7.19
  5. In the newly extracted files delete the sites directory and all its subs.This is done because the upgrade is not going to replace anything in this directory
  6. Rrom a terminal window type:          yes | cp -r /var/www/719/drupal-7.19/* /var/www/html
  7. Note that the destination folder of html is my doc root and all the drupal folders/files are located right underneath this. the yes | cp…. prefix is to let the system know to overwrite everything in the destination. since sites is the only directory that we want to keep and we have removed it from the source, this will be fine.
  8. Run update.php by navigating to http://…yourdrupalsitename/update.php
  9. Follow the instructions for this closely
  10. navigate to reports, available updates and check the version of your core
  11. take the site off of maintenance mode
  12. check different things on the site to ensure a smooth upgrade has occurred.
  13. that should just about do it.

Drupal core upgrade to 7.19

Today I’m going to upgrade core. qual first then prod. i don’t really think there is a compelling reason but i haven’t done a core update yet and i want to have it documented. plus, i want to get rid of the notice about a security update being available. it’s persistent. which is good.

here is a good link: http://drupal.org/node/1494290

since i have a great quality env (VMware) I am using sync toy to back up all the vmdk and related files from the windows host where the centos qual files live. i’ll then follow the instructions on how to upgrade core. should be fine but this way i don’t have to install in sand first. plus, i need to back up the vm files for qual; it hasn’t been done in 8 days.

i have two machines at home. a new windows 7 laptop which i like a lot and an old dell running xp which i honestly love. i have 2.5 gb of mem in the 3.0 ghz cpu and it runs everything i need. i have an external usb connected to that and i keep everything of value in the my docs folder. i use synctoy to sync the desk and laptop my docs and then backup the desk my docs to the external 1tb drive. the only hole in this approach is fire. i’m not worried about theft (for other reasons). i should think about some sort of off site storage. but if this place burns down i’ll have much bigger troubles.

my prod host is with Blackmesh.com hosting. a very excellent hosting company.

the laptop runs the VMs. i have them all on the same network so it is pretty easy to access files from the desk to a vm host. layer 1 is wireless. all in all a nice setup.

so sync toy is moving my vm to the desk from the laptop right now. will be about 30 more minutes.