SquidGuard is a URL redirector used to use blacklists with the proxysoftware Squid. There are two big advantages to squidguard: it is fast and it is free.
Upgrading Drupal Core
We've been recommending that you use Subversion to manage your Drupal site, so these instructions are geared towards using it to upgrade.
The instructions also presume that your site can be taken offline during the upgrading process. If you've have a site that you can't take offline while the process is completed, you've got a whole other set of complicated issues to deal with!
These instructions were written based on upgrading Drupal 5.7 to Drupal 5.10.
Prepare the current site
Before you proceed with upgrading the site, there's a few recommended steps to take to ready the live site for updating:
- Log into your site as USER 1 (the root user, created during initial install), and place the site in Offline mode (
/admin/settings/site-maintenance). - Backup your existing site and database
Using the Backup and Migrate module, make a backup of your database (/admin/content/backup_migrate).
IMPORTANT! Multi-site installs using a single Drupal core need to backup each site's database! - Commit the live site to the Subversion repository.
svn commit -m "Site prepped for Drupal core update." - Optionally, at this point you can create a tag of the site in your svn repo. Change the release number as necessary for your particular site.
svn copy http://svn.example.com/svn/projectname/trunk \
http://svn.example.com/svn/projectname/tags/release-1.0 \
-m "<projectname> prior to Drupal core 5.10 upgrade" - Switch your theme back to the default theme (''Garland' in 5.x) (
/admin/build/themes).
IMPORTANT! Multi-site installs need to do this for every site using the codebase! - Turn off all modules that are not Core Modules (
/admin/build/modules).
IMPORTANT! Multi-site installs need to do this for every site using the codebase!
Create the updated site copy
- Download the new Drupal core:
cd /var/websites/projectname
wget http://ftp.drupal.org/files/projects/drupal-5.10.tar.gz
tar zxvf drupal-5.10.tar.gz
rm drupal-5.10.tar.gz - Copy the following files from the backup directory into your Drupal site directory:
.htaccesscp -p htdocs/.htaccess drupal-5.10/sites/default/settings.php(but see section on older sites below)
cp -p htdocs/sites/default/settings.php drupal-5.10/sites/default/- the
filesdirectory
cp -pr htdocs/files drupal-5.10/ - any other files you need from the 'backup' directory, such as your cron scripts in scripts/ or subdomain folders. Ex:
cp -r htdocs/sites/all drupal-5.10/sites/
.svn from the folders you've copied into the new Drupal core:rm -rf `find drupal-5.10 -type d -name .svn`Activate the new Drupal core and upgrade your modules
- Adjust your Apache configuration to serve the new copy of the site. This likely means editing
/usr/local/apache2/conf/extra/httpd-vhosts.confand changing theDocumentRootand<Directory>directives to the new Drupal 5.10 folder. Remember to restart Apache after you make the changes. - Run
update.phpby going tohttp://www.example.com/update.phpwith your web browser. - Check the site status page (
/admin/logs/status) and confirm that things are working ok. - Delete any of your outdated modules and download the new versions for your Drupal core. Ex:
cd drupal-5.10/sites/all/modules
rm -rf date
wget http://ftp.drupal.org/files/projects/date-5.x-2.0-rc3.tar.gz
tar zxvf date-5.x-2.0-rc3.tar.gz
rm date-5.x-2.0-rc3.tar.gz - Activate the non-core modules that your site was using prior to the upgrade (
/admin/build/modules). - Download new versions of any custom themes that need upgrading.
- Run
update.phpby going tohttp://www.example.com/update.phpwith your web browser. - Check the site status page (
/admin/logs/status) and confirm that things are working ok. - Change your theme back if you weren't using Drupal's default theme.
- Put your site back online (
/admin/settings/site-maintenance).
- Log in to post comments