Drupal 6 only gives you one block for each of the menus. Here’s how you get another one for any of the menus.

1. Login with permission to use (or enable) PHP input filter & create blocks.
2. Go to Administer > Site building > Blocks.
3. Click Add.
4. Enter description and title as necessary.
5. For the Block body:
   1. Choose PHP Code Input Format.
   2. Enter this code:
      
      <?php
echo menu_tree('primary-links');
/*
* Other possible values for the parameter:
* 'navigation'
* 'secondary-links'
* 'admin_menu'
*
* See API function menu_tree() for details:
* http://api.drupal.org/api/function/menu_block/6
*/
?>
6. Save the block.
7. Apply CSS to theme as needed and enjoy.

1. Edit settings.php file
2. String Overrides module

Method 1: Edit settings.php file

Pros

• Quick method for small number of strings.
• Less accessible in cases where you want to retain some control even after granting administrator access.

Cons

• English only.
• No admin pages, requires access to files on server (FTP / SFTP / SSH). Difficult to delegate changes to non-developers.

Procedure

1. Edit settings.php for the site in question.
   • You’ll need to either download the file, edit it, and re-upload it, or edit it in place on the server. Of course, make a backup.
   • Either way, you’ll probably need to temporarily change the permissions of the file and its containing folder to to give you “write access”. When done, be sure to change them back to what they were.
   • The default settings file is in
     drupal_root_folder/sites/default/settings.php
2. Look for this code at the bottom:
   
   # $conf['locale_custom_strings_en'] = array(
# 'forum' => 'Discussion board',
# '@count min' => '@count minutes',
# );

3. Remove the comment marks (’#') and add string replacement assignments:
   
   $conf['locale_custom_strings_en'] = array(
'Old string 1' => 'New string 1',
'Old string 2' => 'New string 2',
);


Method 2: String Overrides module

(http://drupal.org/project/stringoverrides)

Pros

• Admin page for managing string replacements.
• Uses access permissions. Easier to delegate management of overrides.

Cons

• Yet another module to install, update, and administer.
• Possible performance hit. Stores replacements in the database.
• Uses access permissions. Harder to restrict changes when you have to give administrator access to others.

Procedure

1. Install and enable the module.
2. Follow the instructions / documentation for adding string overrides.

I’m assuming you already know why you want to run PHP as CGI, so I won’t go into the benefits.

First, make backups. I don’t work for Media Temple, and I’ve never used their snapshot backup system, but it sure looks like a fast and convenient way for making a full backup of the machine.

Now, here’s the blow-by-blow (adapted from this KB article). These instructions must be followed for each domain, though there’s probably a way to make it the default - perhaps by modifying httpd.conf.:

1. Enable root acccess, CGI, and FastCGI for the machine / domain in question.
2. On my machine, Safe Mode was on by default, so I’m skipping the Safe Mode step from the KB article.
3. Find out the FTP username for the domain. This is the username under which PHP will run (the point of this is so that PHP will have permission to access the files and folders that you uploaded via FTP, which will be owned by the FTP user).
4. Log in via SSH as root and navigate to the directory for the domain (/var/www/vhosts/yourdomain.com/).
5. Copy the CGI version of PHP to the bin directory and change ownership as so (replace “username” with the FTP username you found above) with these commands:
   
   cp /usr/bin/php-cgi bin/
chown -R username:psacln bin
6. Open / create vhost.conf for editing:
   
   cd conf
vi vhost.conf
7. Add the following lines to vhost.conf, replacing “yourdomain.com” with your actual domain name:
   
   AddHandler fcgid-script .php .php5
<Directory /var/www/vhosts/yourdomain.com/httpdocs>
FCGIWrapper /var/www/vhosts/yourdomain.com/bin/php-cgi .php
allow from all
</Directory>

   Notes:

   Adding “.php” to the AddHandler directive allows also files with “.php” extension to run as FastCGI.

   No ideas about the FCGIWrapper directive… Only 1-2 arguments are allowed, so I changed the second to “.php”

   I removed the Options line from the KB article code because ExecCGI and FollowSymlinks was enabled by default on my (dv) 3.5 server.

   Likewise, I left out the SuexecUserGroup line from the KB article code.

8. Save vhost.conf, quit vi, and restart the webserver:
   
   /usr/local/psa/admin/sbin/websrvmng -a -v

   I’m pretty sure you have to restart with this command rather than the manual restart command so that the new vhost.conf is recognized.

9. Test by creating a phpinfo() file in your web directory and visit it with the browser. You should see “CGI/FastCGI” on the Server API line (right after the configuration info):
   

The new system should still be using /etc/php.ini for configuration. Note that the default php.ini configuration is not considered to be secure and should be reviewed.

Update: This may interfere with your sessions. If you’re having login problems with a web app (or with webmail), then check the error log to see if the problem is unwritable session save path.

There a probably a couple of ways to fix this. The easiest is to change the owner:group of /var/lib/php/session to username:psaserver (where username is the FTP user used above). I imagine you don’t want to use this method if you’re running several domains as PHP/CGI.

First, creating a VPN:

It’s pretty straightforward to do via Internet Connect. Just enter the info your network admin gave you, and you should get a basic connection.

Now, the “DNS suffix”:

Here’s a little background:

Let’s say you’re given a URL for an intranet page like http://machine_name/the_file.html, and a DNS suffix of company_net.lan. In the URL, the “domain” is actually an abbreviation. The full domain can be interpolated by adding the DNS suffix to the end of the abbreviated domain, to give you http://machine_name.company_net.lan/the_file.html. You should be able to get to the page by using this URL with the full domain name (assuming you’re connected to the VPN).

If you just entered the URL into the browser as-is, you’d probably get an error, because the browser wouldn’t know what to do with http://machine_name as the domain name. It would probably either say something like Firefox can’t find the server at http://machine_name. or translate the URL to http://www.machine_name.com/the_file.html, which would also lead to undesired results.

Why not just use the real URL, then? While you could get to the page that way, the page might have links or images on it that use the abbreviated domain name. They wouldn’t work, because the browser wouldn’t know how to interpret the abbreviated domain name.

Enter the DNS suffix. Specifying the DNS suffix tells the system to automatically append the suffix to the abbreviated domain. So, whenever the browser transmits http://machine_name/, the suffix is added automatically as the query goes out through the connection, the machine gets found, and the correct information gets returned to the browser.

Now, where to put the DNS suffix. It’s easy, if not intuitive.

1. Make sure you’re connected to your VPN.
2. Open System Preferences -> Network.
3. For whatever location you’re using, open the second drop-down menu. You should see an entry for the VPN you’re using. Choose it.
4. Make sure you’re on the TCP/IP tab in the preference pane.
5. In the Search Domains field, enter the DNS suffix you were given and click Apply Now (the DNS suffix might look something like mycompanyintranet.lan).
6. Now go back to your browser and try the URL with the abbreviated domain (make sure you’re connected and the browser is talking to the VPN).

Here’s a little tidbit about Internet Connect: If you have unused connections you want to delete, just drag their icons out of the top of the window. This will delete the connection and all of it’s configurations.