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.
Updating Drupal Core
Primary tabs
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 6.14 to Drupal 6.15.
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:
- 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 6.15 upgrade" - 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
). - Switch your theme back to the default theme (''Garland' in 6.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/htdocs
svn export http://<your_svn_server>/svn/drupal/6.x/core/current drupal-6.15
svn commit -m "Drupal-6.15 core added." - Copy the following files from the old site into the new Drupal directory:
.htaccess
cp -p drupal-6.14/.htaccess drupal-6.15/
- Symbolic link the the
sites
directory into the new Drupal core:
cd drupal-6.15
rm -rf sites
ln -s ../sites sites
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.conf
and changing theDocumentRoot
and<Directory>
directives to the new Drupal 6.15 folder. Remember to restart Apache after you make the changes. - Run
update.php
by going to http://www.example.com/update.php with 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:
- 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.php
by going to http://www.example.com/update.php with 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