Download - Drupal

seaurchininterpreterInternet και Εφαρμογές Web

7 Δεκ 2013 (πριν από 3 χρόνια και 10 μήνες)

212 εμφανίσεις

ii
Table of Contents
Preface

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

iv
1. Acquia Drupal and the Acquia Network

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

1
2. System Requirements

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

3
3. Acquia Network Accounts and Subscriptions

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

6
4. Setting Up Acquia Drupal

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

7
Installing Acquia Drupal

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

7
Create Database

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

8
Download, Extract, Move to Server

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

14
Install Website

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

15
Advanced Installation on the Command Line

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

18
Migrating and Upgrading

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

21
Prepare + Download

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

21
Prepare Modules for Update

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

22
Update to Acquia Drupal

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

25
Configure Site

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

26
Advanced Migration with the Command Line

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

28
5. Acquia Network Services

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

32
Acquia Network Overview

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

32
Cron Service

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

33
Heartbeat Service

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

35
Mollom - Content Protection

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

36
6. Subscriber Forums and Technical Support

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

38
Support FAQs

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

38
Long-Term and Interim Support Releases

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

39
7. Appendices

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

41
PHP Settings + Extensions

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

41
Acquia-Supported Modules

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

43
Acquia Network Modules

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

44
Backing up Acquia Drupal

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

44
Drupal Paths and Clean URLs

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

49
A. Glossary

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

51
Index

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

66
iv
Preface
What is Acquia Drupal?
Acquia Drupal is a commercially supported distribution of the open source
Drupal
[
http://acquia.com/what-is-drupal
]
social publishing system. A packaged collection of the best software from the
Drupal community
[
http://drupal.org/
]
,
Acquia Drupal offers you an advanced starting point to quickly begin building Drupal websites.
What is this document?
This guide will help you get your Acquia Drupal site up and running, connect your site to the
Acquia Network
, and
show you how to use Acquia Network services.
Here's how to get started with Acquia Drupal:
1.
Install or upgrade to Acquia Drupal
:

Installing Acquia Drupal
to make a new website.

Migrating and Upgrading
covers:

Converting an existing Drupal 6.x site to Acquia Drupal

Upgrading an existing Acquia Drupal site to the latest version of Acquia Drupal
Please read Acquia's recommended migration procedure, under
Migrating and Updating
, before attempting to
update an existing Acquia Drupal website or convert an existing Drupal 6.x site to the latest version of Acquia
Drupal.
2.
Create an Acquia Network subscription
- Get access to essential site services and technical support:

Network Services
: Subscribers to the Acquia Network benefit from a range of information and network services.
See more in the
Acquia Drupal and the Acquia Network
section of this guide. For a detailed description of the
Acquia Network and its subscriber services, go to the
network information page
[
http://acquia.com/products-
services/acquia-network
]
on the Acquia Network.

Acquia Drupal
Technical Support
: As a subscriber to the Acquia Network, there are various information and
support channels available to you, ranging from online subscriber forums to live telephone support, depending
on your subscription level. See the
Subscriber Forums and Technical Support
of this guide for details.
Important Concepts and Naming Conventions in this
Guide

System Messages
When you need help or technical support for your Acquia Drupal site, go to the Acquia Network subscriber forums
or contact the support channels available to your subscription level. However, while managing your site you may
also see messages that refer you to resources on
http://drupal.org
. The Drupal website is a great resource, especially
for community modules not included in Acquia Drupal. Acquia actively participates in the drupal.org community.

Drupal URLs: Understanding the Drupal
Path
Throughout this document, "
click paths
", or instructions telling you what links to click, are shown like this:
Preface
v

Administer
> Site building > Modules
This means, "Please click the links:
Administer
,
Site building
, and then
Modules
".
Additionally, the
Drupal path
to the same page or screen is shown like this:

?q=admin/build/modules
This means, "Add
?q=admin/build/modules
to the base URL of your site, in your browser, and you'll go directly to
the right page or screen." For example, given the site example.com, adding the Drupal path above would result in a
URL
http://example.com/?q=admin/build/modules
. This is given as a shortcut for people who are more comfortable
typing web addresses straight into the browser's address bar.

Document Root Directory: [docroot]
The location in a server's file system that contains a website's code base. These files are addressed when serving
web pages to a browser. Hosting providers may call this directory htodcs, public_html or www; users know it as
the
home directory
, web root or the document root. This guide refers to it as [docroot] from here on in.
Instructions containing directory and file locations start with
[docroot]
, meaning: "you have to know how to get
to the document_root directory yourself (and know its name on your server), then follow the rest of the path as
written here".

Acquia Drupal Tarball Filenames
The Acquia Drupal files available for download on the Acquia Network are called something similar to
acquia-
drupal-1.0.0.
ISR
.tar.gz
or
acquia-drupal-1.0.0.1234.
LTS
-update.tar.gz
. These files names change over time to
reflect updates to the Acquia Drupal code base.
In this guide, these files have generic names, such as
acquia-drupal-a.b.c-YYY.dddd-update.tar.gz
, where the letters
stand for:

a - major version number

b - feature set improvement

c - bugfixes and minor module feature update

YYY -
IS
or LTS release (explained further in the
support section
of this guide)

dddd - build number
You will need to replace the generic name in these instructions with the exact name of the files you download from
the Acquia Network at
http://acquia.com/downloads
.
1
Chapter 1. Acquia Drupal and the
Acquia Network
What is Acquia Drupal?
Acquia Drupal is a commercially supported distribution of the open source
Drupal
[
http://acquia.com/what-is-drupal
]
social publishing system. A packaged collection of the best software from the
Drupal community
[
http://drupal.org/
]
,
Acquia Drupal offers you an advanced starting point to quickly begin building Drupal websites.
Acquia Drupal simplifies the development of social publishing applications - interactive, community-based publishing
websites that combine both editorial and user-generated content. Whether building a public facing website or an intranet
application, the goal is to engage visitors and encourage participation. Acquia Drupal allows you to mix and match
proven social publishing patterns that transform spectators into active contributors, including:

Single and multi-user blogs

Community forums and threaded discussions

Social networks

Ratings and voting

Mashups

Wikis

Web content

and much more

Acquia Drupal is
GPL
licensed - freely available for
download
[
http://acquia.com/downloads
]
and use. Acquia Drupal
includes modules from a number of sources: Drupal community contributed modules, Drupal 6.x core and Acquia.
More information on Acquia Drupal:

Modules
[
http://acquia.com/products-services/acquia-drupal-modules
]

Features
[
http://acquia.com/products-services/acquia-drupal-features
]

Acquia Drupal FAQ
[
http://acquia.com/products-services/acquia-frequently-asked-questions
]

Supported Platforms
[
http://acquia.com/products-services/acquia-drupal-supported-platforms
]
A full overview of the current state of Acquia Drupal can be downloaded as a pdf from
the Acquia Drupal information
page
[
http://acquia.com/products-services/acquia-drupal
]
on the
Acquia Network
.
What is the Acquia Network?
The Acquia Network completes the Drupal experience by providing the support and network services to operate a
trouble-free Drupal website. Subscribers to the Acquia Network gain access to remote network services, Acquia Drupal
documentation and the Acquia Network’s subscriber forums. Premium subscriptions, depending on subscription
level, provide web-based ticket management, as well as email and telephone support. The Acquia Network is
Acquia Drupal and the Acquia
Network
2
your operations portal for managing
Acquia Drupal
[
http://acquia.com/products-services/acquia-drupal
]
sites and
connecting to Acquia’s support channels.
Acquia Network annual subscription packages are available for sites of every size, from global-scale multi-site
deployments to local community sites.
Acquia Network Services
By subscribing to the Acquia Network, you gain access to a suite of remote site management services that simplify
and automate the operation of your Acquia Drupal sites. Services include:

Software update management

System profile management

Automated spam blocking with Mollom

Heartbeat uptime monitoring

Code modification detection

Remote cron activation

Online documentation

Site usage statistics
More information can be found in the
Acquia Network Services
chapter of this guide and on the
Acquia Network
[
http://acquia.com/products-services/acquia-network
]
.
Technical Assistance Center
Acquia Network subscribers obtain access to Acquia's Technical Assistance Center, according to their chosen service
level. Premium subscription levels include email and phone support for issue resolution and advisory services.
Additionally, the Acquia Network provides an interface for both subscriber forums and web-based case management
to ensure that technical issues are resolved in a timely, efficient manner.
Administrative Task Management
In addition to remote services and technical support, the Acquia Network provides administrators with task
management capabilities directly within the dashboard. Administrators can convert notification messages into tasks,
assign owners, and collaborate to complete tasks - all from within the Acquia Network.
More information on the Acquia Network
More information on the Acquia Network can be found on the
network information page
[
http://acquia.com/products-
services/acquia-network
]
.
3
Chapter 2. System Requirements
This section provides information on system requirements you must meet before installing Acquia
Drupal
.
Hardware requirements
Requirement
Description
Memory
512 MB of RAM (recommended minimum). More
memory generally leads to better performance.
Disk space
1 GB of hard disk space. As the Acquia Drupal database
increases in size, more space will be required. Extra space
should also be allocated for files that get uploaded to the
Acquia Drupal site.
Software requirements
Requirement
Description
Operating Systems
Note
This list may change over time. The
current official list of supported operating
systems can always be found on
the
Acquia Network.
[
http://acquia.com/
products-services/acquia-drupal-
supported-platforms
]

Linux

CentOS 5

Debian 4.0 "etch"

Novell SuSE Enterprise Linux 9

Red Hat Enterprise Linux 5

Ubuntu Linux, Desktop Edition 8.04
LTS

Ubuntu Linux, Server Edition 8.04 LTS

Solaris

Solaris 10

Mac

Mac OS X Desktop 10.5x

Mac OS X Server 10.5x

Windows

Windows XP Professional or Home Edition

Windows Server 2003 with Service Pack 1 + R2

Windows Server 2008

Windows Vista Service Pack 1
Server Connections
Various Acquia Drupal features - Acquia Network site-
health monitoring, update status notification, aggregator
System Requirements
4
Requirement
Description
feeds, and others require the web server process be able to
initiate outbound HTTP connections. Be sure to check that
your hosting provider and/or server configuration allows
this.
Web Server
Web Server: Choose a web server to suit your needs.
Acquia Drupal supports both Apache and Windows IIS.

Apache
Apache web server
[
http://httpd.apache.org/
]
version
1.3.x or later. To use Drupal's Clean URLs feature,
enable the mod_rewrite module and the ability to use
local .
htaccess
files.

Windows IIS 6, 7
The
Windows IIS web server
[
http://
www.microsoft.com/WindowsServer2003/IIS/
Default.mspx
]
can run Acquia Drupal. More
information about clean URLs and IIS can be
found on
Drupal.org
[
http://drupal.org/node/3854
]
.
PHP
Version
If using
Red Hat Enterprise Linux 5
, please read
this
important information
before continuing.
PHP 5.2.x
PHP Extensions and Settings
Please see the
PHP Setting + Extensions
appendix for
these settings and requirements, including how to set
the PHP memory_limit parameter to the 32M minimum
required to run Acquia Drupal (64M is recommended for
certain operations).
Database
MySQL 5.x
The following mySQL settings are recommended:

For best performance enable
MySql query cache
[
http:/
/dev.mysql.com/doc/refman/5.0/en/query-cache.html
]
.

max_allowed_packet = 16M # This is often 1M by
default. Increasing to 16M may be necessary for some
modules.
For Red Hat Enterprise Linux 5: PHP 5.1.
Acquia recommends using PHP 5.2.x to achieve the fullest results out of your Acquia Drupal website.
Red Hat Enterprise Linux 5 is distributed with PHP 5.1 and some issues exist between some Drupal
modules and earlier PHP versions.
Specifically, on PHP versions prior to 5.2, the Date module is unable to use native date handling.
For PHP4, PHP 5.0.x, and PHP 5.1.x, enabling the Date PHP 4 module provides substitutions for
some missing date handling. This means core date handling is available, but some issues do exist
such as Daylight Savings time and time zones not properly being adjusted. The Date module is not
System Requirements
5
currently shipped with Acquia Drupal but it is commonly downloaded from drupal.org and installed
to provide certain date handling functions. Be cautioned that some date handling functions may not
work as expected when using PHP 5.1.
6
Chapter 3. Acquia Network Accounts
and Subscriptions
The Acquia
Drupal
software is licensed under the
GPL
and is freely available to download at
http://acquia.com/
downloads
.
Acquia Network Membership
Members of the Acquia Network can participate in discussions, comment on content in the
Acquia Network
Community
[
http://acquia.com/community
]
, and will have access to Acquia white papers and other community
materials.
To create a new user account, click the
Sign Up
link on the Acquia homepage at
http://acquia.com
and follow the
instructions.
Figure 3.1. Sign up link
Acquia Network Subscriptions
To take advantage of Acquia Network services and technical support options, you need an Acquia Network
subscription. See the
Acquia Network product matrix
[
http://acquia.com/product-matrix
]
for details.
Once you have successfully subscribed to the Acquia Network and Acquia Network Services, you will have a menu
block on your
Acquia Network dashboard
[
http://acquia.com/network/dashboard
]
called the
Site selector
.
Figure 3.2. Site Selector
7
Chapter 4. Setting Up Acquia Drupal
Overview:
Installing Acquia Drupal
explains how to install Acquia Drupal to make a new website.
Migrating and Upgrading
covers:

converting an existing Drupal 6.x site to Acquia Drupal

upgrading an existing Acquia Drupal site to the latest version of Acquia Drupal
Installing Acquia Drupal
This section covers installing a new Acquia
Drupal
website in an
AMP
(Apache + MySQL +
PHP
) development
environment in your computer's file system (localhost) or on an external server provided by a web-hosting company.
Overview
1.
Check your Tech
2.
Create Database
3.
Download, Extract, Move to Server
4.
Install Website
5.
Advanced Installation on the Command Line
Check Your Tech
These installation instructions are divided into three broad categories depending on your needs and the technologies
you use - two on external servers and one on your computer:
Installation on an External Webserver
Before you can install Acquia Drupal on an external server, you need a web hosting account, access to your server,
and a domain name for your new site. Check the
system requirements
and
PHP Settings + Extensions
sections of this
document before buying a web hosting package to make sure it meets Acquia Drupal's needs.

Hosting Service Interface:
You have a web server that you access with
FTP
and web based tools from your hosting
provider. Proceed the next section of this guide,
Create Database
.

Command Line Interface:
You have a web server that you access with a shell, working on the command line.
Proceed to the section
Advanced Installation on the Command Line
.
Installation on Your Computer

Localhost
:
You want to install Acquia Drupal on your personal computer. The instructions for you are basically
the same as when using a hosting service, except that you need an AMP stack installed, and there is no need for you
Setting Up Acquia Drupal
8
to use FTP to move files between your computer and the web server. Read the information below on AMP stacks,
then proceed to the next section of this guide,
Create Database
.
The
AMP Stack
Acquia Drupal can be installed on your personal computer or laptop for the purpose of testing and development.
This is called a
localhost installation
. You need to install software to run the database and web server that Acquia
Drupal depends on. This software is called an AMP stack:

A
pache +
M
ySQL +
P
HP
You may download one of the following AMP stacks suitable for your operating system and follow its installation
and configuration instructions.

Apple Mac
:

MAMP
-
http://www.mamp.info

Linux
: An AMP stack is usually installed using a package manager specific to a given distribution of Linux. Here
are instruction for Ubuntu and Fedora Linux:

Ubuntu LAMP for Newbies
[
http://www.howtoforge.com/ubuntu_lamp_for_newbies
]

Perfect Server: Fedora 7
[
http://www.howtoforge.com/perfect_server_fedora7
]

Windows XP/Vista
:

WAMP
:
http://www.wampserver.com

XAMPP:
http://www.apachefriends.org
Create Database
Acquia
Drupal
requires access to a database for installation and operation. These instructions cover the creation of a
MySQL database user and database:
Overview
1.
Create a new, empty database.
2.
Create a database user account with the necessary privileges.
3.
Tell Drupal about the database connection details. This is covered in the
Install Website
section.
Database Checklist
Keep a checklist of the things you need to know!
1.
Database name
2.
Database username
3.
Database password
4.
Database host
Setting Up Acquia Drupal
9
5.
Database port
You'll need these details in the next step, so it helps to write these details down as you work through
the rest of these instructions.
Note
The
database username
- not to be confused with any other user identity - is the identity that your
Acquia Drupal site uses to access MySQL.
Using phpMyAdmin
PhpMyAdmin is a popular tool for managing MySQL databases. You can find a link to phpMyAdmin in your hosting
service interface (or in some cases, to alternative database management tools) or your
AMP
stack interface. These
instructions show how to set up your database using phpMyAdmin.
Create a new database
1.
Follow your AMP stack's instructions to open "phpMyAdmin" in the browser. Look for the link that says
Databases
.
Figure 4.1. phpMyAdmin Databases
2.
In the
Create new database
field, type the database name of your choice. In the
Collation
dropdown, select
"utf8_unicode_ci". Click
Create
and you have completed the first step. Write down the database name on your
checklist because you'll need it later.
Setting Up Acquia Drupal
10
Figure 4.2. phpMyAdmin New Database
3.
If your database has been created successfully, phpMyAdmin will present you with the following message:
Database databasename has been created.
Create a database user account
Now that you've set up a new database, you need to create a user account that is allowed to access that database. This
user account is independent from all other logins or accounts that you use to access your computer, your web hosting
account, your Drupal site, or anything else. Its sole purpose is to give you (and Drupal) a secure way to interact with
the new database you've created.
1.
To start, navigate back to the homepage for phpMyAdmin, and click the
Privileges
link.
Setting Up Acquia Drupal
11
Figure 4.3. phpMyAdmin Privileges
2.
Figure 4.4. phpMyAdmin new user
Click the
Add a new
User
link:
3.
Fill out the
User name
,
Host
and
Password
fields. The host field should read
Local
in the dropdown and
localhost
in the textfield. Make sure you add the user name, host and password to your Database Checklist because you'll
need to know these later when configuring Drupal. Finally, click
Go
at the bottom of the page:
Setting Up Acquia Drupal
12
Figure 4.5. phpMyAdmin Go
Success!
Figure 4.6. phpMyAdmin Success!
Setting Up Acquia Drupal
13
4.
With the database and the database user both created, the last step is to grant privileges to the new user on the
new database. On the same success screen that is shown after creating a new database user is the form for granting
privileges. Find the
Database-specific privileges
section and select the database that you just created:
Figure 4.7.
5.
You will then be taken to your new database user's
grant privileges
form for the new database that you created.
Click the check boxes for the following privileges: SELECT, INSERT, UPDATE, DELETE, CREATE, ALTER,
INDEX, DROP, CREATE TEMPORARY TABLES, and LOCK TABLES. Click
Go
to submit the form:
Figure 4.8. phpMyAdmin Grant Privileges
Congratulations! You've finished setting up a database for Acquia Drupal to use. You can now move on to the
instructions for installing and configuring Acquia Drupal. Make sure to keep your Database Checklist handy.
Setting Up Acquia Drupal
14
Download, Extract, Move to Server
Download + Extract
When creating a new Acquia
Drupal
site, download the latest Acquia Drupal "full version" release from
http://
acquia.com/downloads
and save the tarball archive, called something like
acquia-drupal-a.b.c-YYY.dddd.tar.gz
on
your computer.
Downloading using Safari + Mac OS X
By default, the Safari 3 browser in Mac OS X uncompresses zipped files as part of its download process.
Don't be surprised if you find a .tar file rather than a compressed .tar.gz file.
To stop Safari unzipping downloaded archives by default, go to Safari's Preferences > General tab and
uncheck 'Open "safe" files after downloading'.
Move to Server
You now need to move your Acquia Drupal files to the your server's document root.
Localhost Installation
1.
Unzip/extract the Acquia Drupal tarball with any compression/extraction tools you are familiar with. A new
directory, called acquia-drupal-a.b.c-YYY (or similar), will be created.
2.
Move the contents of the acquia-drupal-a.b.c-YYY directory to the [docroot] directory of your
AMP
stack.
3.
Proceed to the
Install Website
section of this guide.
External Server Installation
File Transfer via FTP
If you are moving Acquia Drupal files to a web server, you need an
FTP client
, a program for
transferring data between your computer and a remote server via FTP (
File Transfer Protocol
).
The free
FireFTP
plug-in for the Firefox browser is a good choice of FTP client for anyone using
FireFox on any operating system.
http://fireftp.mozdev.org/
1.
Start your FTP client and enter the connection parameters for your server. These are:

Host: Your site's URL without the http header (example.com)

User
: The FTP username set by you or provided to you by your hosting provider

Password: The FTP password set by you or provided to you by your hosting provider
2.
With FTP access, you can't usually unzip compressed archives on your server, so you'll have to do that on your
local machine and then transfer the files to your server.
Unzip/extract the Acquia Drupal tarball with any compression/extraction tools you are familiar with. A new
directory, called acquia-drupal-a.b.c-YYY (or similar), will be created.
Setting Up Acquia Drupal
15
3.
Connect your FTP client to your server. Most FTP clients have a "local" window (your computer) and a "remote"
window (your server). Navigate in your local window to your extracted Acquia Drupal code-base. In the remote
window, navigate to the [docroot] directory on your server - see the introduction to the
Setting up Acquia Drupal
section of this document for more information on the [docroot] directory.
It is common for hosting providers to leave a placeholder "index.html" file (or similar) in the [docroot] directory
on the server. Delete any such placeholders.
4.
Transfer the Acquia Drupal files (NOT the directory containing them) into document_root. In some FTP clients
this means dragging them from the local to the target window (select all of them and drag them over); in others,
you should highlight one or more files to be transferred and then click on a transfer button.
Figure 4.9. transfer to server
Don't forget .htaccess!
Some FTP clients ignore files that begin with a dot (.) and Drupal's .htaccess file gets left behind.
Double check that .htaccess has made it to your server.
Install Website
Run the Installation Script
Navigate in the browser to
http://example.com/install.php
- this runs the Acquia
Drupal
installation script, kicking off
the installation process.
Database Configuration Screen
Enter the database parameters from the
Database Checklist
into your new Acquia Drupal installation at this point
(username, password, and database name). The form fields for
Database host
,
Database port
, and
Table prefix
are
found in the
Advanced options section
.
Press
Save and continue
. If the installation completes successfully, your site will give you confirmation messages in
green at the top of Acquia Drupal's configuration screen.
Setting Up Acquia Drupal
16
Figure 4.10. Database Configuration
Database host name
In most standard hosting situations, your database server and your web-server are one and the same
machine. In this case, your database host name is "localhost" because from the web server's perspective,
the database is local. If your database is hosted on a separate database server, you will need to ask your
provider for its host name.
Note
The database connection details are not always easy to find in some hosting interfaces. If you are having
trouble, contact your web hosting provider explaining that you need the database connection details
for installing a Drupal website (a php-based CMS).
Configuration Screen
You need to fill in the following sections on the configuration screen:
Site information

Site name
- this will be displayed in email and other messages that your site generates. It will also be the name
visible to search engines.
Setting Up Acquia Drupal
17

Site email address
- this will be the "from" address of your site when it sends notifications, registration
confirmations and other messages via email. (Your hosting provider may provide you with free email addresses
as part of your hosting package. Make sure you set up an email address - like "info@example.com" and webmail
access or forwarding to suit your needs.)

Acquia subscription identifier and Acquia subscription key
: These keys give your site access to the Acquia
network and its services like cron and heartbeat. You can add them to your site later if you don't have them yet.
If you already have a subscription, go to
http://acquia.com/network/dashboard/subscription
to find your keys. If
you do not have an
Acquia Network
subscription, register with Acquia at
http://acquia.com/sign-up
- once you are
registered on the Acquia Network, you can add a subscription at
http://acquia.com/network/dashboard/subscription
.
Administrator account (aka "USER 1")

Username
:
User
1 on any Drupal site always has all administrative privileges. It is important to keep your user 1
login information for future reference.
Important
There are certain tasks that only User 1 can carry out and Acquia's support staff might need you to
be logged in as User 1 to resolve support issues on your site.

E-mail address
: enter an active email address here - if you forget your password, you can have a login/reset link
sent to this address.

Password
: Please be sensible about the passwords you choose and how you chose to store them. There are many
resources on the internet regarding bast practices for password choice, storage and retrieval.
Server settings

Default time zone
: usually set according to where you or your target audience is located.

Clean URLs
: Most website owners prefer not to have page URLs like "http://example.com/?q=node/1234" - they are
neither easily remembered by visitors, nor are they particularly search engine friendly. "Clean URLs" allows Drupal
to rewrite the same URL without the "?q=" as "http://example.com/node/1234" instead. Combining Clean URLs
with the functionality of the Path module included in the Acquia Drupal core allows you to assign memorable, search-
engine-friendly URLs to nodes like "http://example.com/my_great_blog_post" and set automatic URL creation
patterns with the Pathauto module, also included in Acquia Drupal.
For more information, read the
Drupal path and clean URLs
appendix of this document.
If your server can generate Clean URLs, there will be a green confirmation notice under "Clean URLs," if not, it
will refer you to further documentation on the subject.
Clean URLS's in XAMPP
To have "Clean URLs" on XAMPP, edit httpd.conf (located at path-to\apache\conf\httpd.conf) -
uncomment the line (remove the "#"at the beginning):
LoadModule rewrite_module modules/mod_rewrite
Update notifications:
Check for updates automatically
: Provided you have set up cron, either your own or the Acquia Network cron service,
(more on Acquia's cron service in the
Cron Service
section of this guide), this option allows your site to periodically
Setting Up Acquia Drupal
18
send information to the Acquia Network. The information enables the network to notify you when new releases of
its components are available.
With this option selected, non-Acquia components (contributed modules) will also periodically send anonymous
information to drupal.org.
Notifications for all non-Acquia components will come directly from Drupal.org as they are generated. Acquia's release
and update recommendations are specific to Acquia-supported components and modules are are sent out following
technical, security and compatibility testing by Acquia.
Enabling this feature significantly enhances your site's security and is highly recommended.
Advanced Installation on the Command Line
Before you can install Acquia
Drupal
on an external server, you need a web hosting account, access to your server,
and a domain name for your new site. Check the
system requirements
and
PHP Settings + Extensions
sections of this
document before buying a web hosting package to make sure it meets Acquia Drupal's needs.
These instructions include all the commands you need to know to install Acquia Drupal via command line access, also
known as the "command line" or "the terminal". Many hosting providers include
FTP
access as standard, but will add
command line access if you ask for it.
Where is my command line?

Mac OS X
: A full Unix command line is built into the operating system. In Mac OS X it is located
under Applications > Utilities > Terminal.app

Linux
: Linux operating systems also have a command line application built in, called the "terminal".
Its location varies according to the flavor of Linux.

Windows XP/Vista
: Windows is unable to open a command line on a remote computer. It needs
the help of a program like PuTTY, a free and open source remote command line client. You can
find it at
http://www.putty.org
.
Login to Your Server
Use the credentials provided by your hosting provider.
ssh -l username example.com
Create Database
In the following command,
[username]
is a MySQL user (root, for example) that has the CREATE and GRANT
privileges in MySQL. [databasename] it the name of the database you want to create.
mysqladmin -u [username] -p create [databasename]
Create Database User
Login to MySQL:
Setting Up Acquia Drupal
19
mysql -u [username] -p [databasename]
Enter your password when asked. You will then see the mysql prompt:
mysql>
Create a user with the following command where "databasename" is your database, "newusername" is the new database
user you are creating and "password" is its password:
GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, ALTER, INDEX,
DROP, CREATE TEMPORARY TABLES, LOCK TABLES
ON databasename.*
TO 'newusername'@'localhost' IDENTIFIED BY 'password';
FLUSH PRIVILEGES;
If successful, MySQL will reply with:
Query OK, 0 rows affected
To leave MySQL and return to your server, type
exit
Download Acquia Drupal to Server
When creating a new Acquia Drupal site, use the latest Acquia Drupal "full version" release. Check its exact URL
http://acquia.com/downloads
.
Still logged in to your server, navigate to your [docroot] directory:
cd path/to/[docroot]
Download the Acquia Drupal tarball:
wget
Setting Up Acquia Drupal
20
http://acquia.com/files/downloads/acquia-drupal-a.b.c-YYY.dddd.tar.gz
Unpack the Tarball
Unpacking the tarball with the command:
tar -zxvf ./acquia-drupal-a.b.c-YYY.dddd.tar.gz
You will now have a directory named acquia-drupal-a.b.c-YYY containing Acquia Drupal's code base.
If you've followed the instructions so far, you'll have a directory structure like this:
/path/to/[docroot]/acquia-drupal-a.b.c-YYY
The problem with this is that acquia-drupal-a.b.c-YYY will be in your site's URL. To avoid this, all of the files in
acquia-drupal-a.b.c-YYY have to be moved up one directory level so that they are all in [docroot] directly.
1.
Move into acquia-drupal-a.b.c-YYY
cd acquia-drupal-a.b.c-YYY
2.
Move contents up a level
mv * ..
mv .htaccess ..
It is necessary to move .htaccess explicitly.
3.
Move up to the [docroot]
cd ..
4.
Remove empty acquia-drupal-a.b.c-YYY directory
rm -fd acquia-drupal-a.b.c-YYY
Setting Up Acquia Drupal
21
Advanced Tar Usage
A variant on the untarring instructions from above is to put the tarball somewhere outside of the [docroot]
directory and then to run a command similar to this:
tar -zxvf acquia-drupal-a.b.c-YYY.dddd.tar.gz \
-C /path/to/[docroot] \
--strip-components 1
The
-C
flag lets you specify the path to [docroot] while the
--strip-components 1
strips the leading directory
from the tarball, placing all of the files directly into [docroot] where they belong.
Migrating and Upgrading
Read Before Updating
Read these instructions carefully before attempting to update an existing Acquia
Drupal
website or convert an existing
Drupal 6.x site to the latest version of Acquia Drupal.
The update procedure described here is designed to avoid code version conflicts during update or migration. In it, you
will leave a copy of your entire site intact on your server, as is (as a backup), and copy only site configuration and
data files into a new Acquia Drupal code base.
It is essential to keep a back up of all old site code until you are certain the new, updated version of your site is
functioning perfectly. Keeping the older code base gives you a fallback position if you encounter any unexpected
problems with the newer version.
Check Your Tech

Updating or migrating
using GUI tools and
FTP
server access (or localhost)
, proceed to the next section of this
guide,
Prepare + Download
.

Updating or migrating
using command line access
, skip to the
Advanced Migration with the Command Line
section
of this guide.
Prepare + Download
1. Backup
Backup all your existing files and all database tables, using phpMyAdmin or a similar tool. Before proceeding, test
your backups to be sure you can restore your site if necessary.
Important
For the next steps, it is essential that you are logged in to your site as
User
1.
User 1 - the user whose profile path is
http://example.com/user/1
- is the first user created on any
Drupal
site and always has all administrative privileges.
Setting Up Acquia Drupal
22
There are certain tasks that only User 1 can carry out and Acquia's support staff might need you to be
logged in as User 1 to resolve support issues on your site.
2. Internal Housekeeping
Ensure all pending database- and configuration updates and clean-up tasks have run. Check whether you need to run
the update script by visiting
Administer
> Reports > Status report
(?q=admin/reports/status). If needed, run the update
script, "update.php" (navigate to
example.com/update.php
in the browser).
3. Check PHP Memory
Acquia recommends that PHP's memory limit be set to 32M or greater in order to take full advantage of Acquia Drupal
and prevent unexpected crashes. See the
PHP Settings + Extensions
section for information on how to find and change
your PHP memory limit.
4. Take Site Offline
Make sure you are still logged in as User 1. Navigate to
Administer > Site configuration > Site maintenance
(?q=admin/
settings/site-maintenance) and take your site offline.
5. Download Update Archive
Download the latest update version from the
downloads page
[
http://acquia.com/downloads
]
, a "tarball" file called
something similar to:
acquia-drupal-a.b.c-YYY.dddd-update.tar.gz
. It contains the full Acquia
module distribution, but excludes the files and directories where your site's content and configurations are stored: the
[docroot]/sites
directory, .htaccess, and robots.txt.
Prepare Modules for Update
Note
The following steps are to avoid conflict between Acquia
Drupal
and any contributed modules you
may have installed.
1. Find All Contributed Modules
Drupal's recommended best-practice is to keep all contributed modules in the
[docroot]/sites/all/modules
directory
and only Drupal's core modules in the
[docroot]/modules
directory.
Other non-standard, non-recommended places where contributed modules might have landed are in
[docroot]/sites/
default/modules
,
[docroot]/sites/[sitename]/modules
, or
[docroot]/profiles/[profilename]/modules
.
Find all of the contributed modules on your site. In practice, this means
any module not in the list of core modules
below
. Move them all to the
[docroot]/sites/all/modules
directory.
Now test your site to make sure it is working as expected.
What are core modules? What are contributed modules?
Or, "How do I know what to move and what to leave where it is?"
A module is a collection of code that enables specific Drupal functionality.
Setting Up Acquia Drupal
23
Acquia Drupal's core modules are all found in the
[docroot]/modules
directory.
Never add to, move,
remove or change the contents of the
[docroot]/modules
directory
:

acquia (Acquia Drupal installs its suite of vetted, contributed modules in this directory. No other
(contributed) modules should be placed here.)

aggregator

block

blog

blogapi

book

color

comment

contact

dblog

filter

forum

help

locale

menu

node

openid

path

php

ping

poll

profile

search

statistics

syslog

system

taxonomy

throttle

tracker
Setting Up Acquia Drupal
24

translation

trigger

update

upload

user
Contributed modules
add still more functionality to your site, but do not come with the standard
Drupal download. You can choose from thousands of modules for Drupal in the Drupal contributed
modules repository at
http://drupal.org/project/modules
.
See the glossary entry on
modules
for more information.
2. Remove non-Acquia Versions of the Following Modules
Since new, Acquia-tested versions of the following modules are included in Acquia Drupal, other versions need
to be removed from your installation. If two different versions are on your server (Acquia and non-Acquia in this
case), Drupal might not end up using the intended version and this could also have unexpected, potentially negative
consequences. All modules of the same name (to be precise: all modules with the same directory names) as those listed
below found outside of
[docroot]/modules
should be removed.
Protect your changes
If you have altered any of the modules that you are removing you may want to make a backup copy
for archival purposes.

admin_menu

advanced_help

cck

filefield

fivestar

google_analytics

image

imageapi

imagecache

imagefield

markdown

mollom

pathauto

print
Setting Up Acquia Drupal
25

tagadelic

token

views

votingapi
3. Move non-Acquia, Contributed Modules to [docroot]/sites/all
Move any other contributed modules to
[docroot]/sites/all/modules
if they are not already there. Keeping these in this
standard location will make it easier for Acquia's support engineers to help you if the need arises.
Update to Acquia Drupal
Update your
Drupal
6.x core to Acquia Drupal and add the Acquia
Module
Suite:
1.
Extract the update tarball,
acquia-drupal-a.b.c-YYY.dddd-update.tar.gz
, to a directory on your server. You may
use a GUI extraction tool +
FTP
, or any combination of tools you are familiar with. This will create a directory
called
acquia-drupal-a.b.c-YYY-update
.
FTP Client
Use an FTP client that can upload complete directories.
2.
Copy the following from your current document_root directory into the
acquia-drupal-a.b.c-YYY-update
directory:

.htacess (file)

robots.txt (file)

sites (directory)

anything else you customized not contained in the [docroot]/sites directory
Tip
For sites with very large quantities of uploaded files, consider keeping the file storage directory
normally kept at
[docroot]sites/default/files
outside of the [docroot] directory. You can then add a
symlink from [docroot]/sites/default/files to the file storage directory. This will save considerable
time during migration and future updates.
3.
Rename your
[docroot]
directory
docroot_old
- this is now a backup of your site's code.
4.
Rename the
acquia-drupal-a.b.c-YYY-update
directory
[docroot]
.
Note
The update tarball does not contain a
[docroot]/files
or a
[docroot]/sites
directory. As long as you
have not:

modified any core Drupal files in your existing site

renamed core Drupal directories
Setting Up Acquia Drupal
26

duplicated core Drupal directory names

left any customized code or content outside of the
[docroot]/files
or
[docroot]/sites
directories
in your installation, your core code will now be updated to Acquia Drupal and Acquia's module
suite will now be installed on the server.
5.
If all is well, proceed to the
Configure Site
section.
Configure Site
1. Run the Update Script
Since you are possibly upgrading to newer versions of some modules, run update.php again (navigate to
http://
example.com/update.php
in your browser). This script updates any new or changed functions and makes any necessary
updates to your database structure, so that any new functionality is available and that you receive the full benefit of
Acquia's tested code.
Tip
Make sure you are logged in as
User
1 before running the update.php script.
2. Rebuild Module Directory
Login to your site as User 1.
Acquia
Drupal
checks and rebuilds its module directory every time you visit the modules administration page at
Administer
> Site building > Modules
(?q=admin/build/modules). Go there and check that you see the following
modules:

admin_menu

Acquia agent

Acquia site information

advanced_help

cck

filefield

fivestar

google_analytics

image

imageapi

imagecache

imagefield

markdown
Setting Up Acquia Drupal
27

mollom

pathauto

print

tagadelic

token

views

votingapi
3. Put Your Site Back Online
Put your site back online at
Administer > Site configuration > Site maintenance
(?q=admin/settings/site-maintenance).
4. Connect to the Acquia Network
1.
Activate Acquia Modules
Enable the
Acquia agent
and
Acquia site profile information
modules on the module administration page at
Administer > Site building > Modules
(?q=admin/build/modules). These are listed on the page in the
Acquia
network
group as shown below:
Figure 4.11. Acquia modules
2.
Obtain Network Keys
Obtain your Acquia Network Keys by logging in to the Acquia Network from the subscription tab on the Acquia
Network (
http://acquia.com/network/dashboard/subscription
).
3.
Enter Network Keys
Click the link at the top of the message from your Drupal installation that appears on your screen, or navigate
directly to the page at
Administer > Site configuration > Acquia settings
(?q=admin/settings/acquia-agent) and
enter your Acquia Network keys.
5. Confirm Acquia Network Status
Back on the Acquia Network page, click the
Health
tab. Check that a heartbeat from your site has been received, then
click the
Site profile
sub-tab to confirm that your site has communicated its current platform and module list to the
Setting Up Acquia Drupal
28
Acquia Network. If both of these appear on your Acquia Network health page, you have successfully Acquified your
Drupal installation. Congratulations!
6. Activate Administration Menu Module
Acquia encourages you to take advantage of the Administration Menu module. It not only renders all administrative
menu items in a clean, purely CSS-based menu at the top of every page of your website. It also displays your Acquia
Network subscription status and expiration date, how many users are online, and provides you a direct log out link.
Figure 4.12. Activate Administration Menu Module
Figure 4.13. Administration Menu Open
Advanced Migration with the Command Line
Migrating or Updating Acquia
Drupal
on the command line using
SSH
and SCP.
1. Backup + Prepare
1.
Login to your site as
User
1. Run the update script (navigate to
example.com/update.php
in the browser). This
ensures that all pending database, configuration updates, and clean-up tasks have run.
2.
Check
PHP
's memory limit is 32M or greater. See the
PHP Settings + Extensions
section for information on how
to find and change your PHP memory limit.
Setting Up Acquia Drupal
29
3.
Backup all your database tables, using mysqldump:
mysqldump -u username -p password \
databasename > filename.sql
Compress the .sql file with gzip:
gzip filename.sql

Before proceeding, test your backups to be sure you can restore your site if necessary.
4.
Still logged in as User 1, go to
Administer
> Site configuration > Site maintenance
(?q=admin/settings/site-
maintenance) and take your site offline.
2. Prepare Modules
Move any contributed modules you may have installed to the
[docroot]/sites/all/modules
directory. This is to avoid
conflict between Acquia Drupal's modules and any other versions of those modules.
Acquia Drupal installs its suite of contributed modules in the
[docroot]/modules/acquia
directory. No other
(contributed) modules should ever be placed here and the Acquia Drupal core modules should never be moved. Doing
so could lead to unexpected, negative consequences.
Remove non-Acquia contributed modules of the same name as those listed below from
[docroot]/sites/all/modules
:

admin_menu

advanced_help

cck

filefield

fivestar

google_analytics

image

imageapi

imagecache

imagefield

markdown

mollom

pathauto

print
Setting Up Acquia Drupal
30

tagadelic

token

views

votingapi
3. Download Acquia Drupal Update Tarball
Login to your server. Download the latest update version of Acquia Drupal. It will be a tarball called something similar
to:
acquia-drupal-a.b.c-YYY.dddd-update.tar.gz
. Check the
Acquia Network

downloads page
[
http://acquia.com/
downloads
]
for the exact URL.
wget \
http://acquia.com/files/downloads/acquia-drupal-a.b.c-YYY.dddd.tar.gz
4. Extract the Tarball
This will make a directory called
acquia-drupal-a.b.c-YYY-update
:
tar -zxvf acquia-drupal-a.b.c-YYY.dddd-update.tar.gz
Copy your configuration files and content to new code base with these three commands
(use the same commands to
copy any other customized files (cp) or directories (cp -R) to your new code base)
:
cp path/to/[docroot]/.htaccess \
acquia-drupal-a.b.c-YYY-update /.htaccess
cp path/to/[docroot]/robots.txt \
acquia-drupal-a.b.c-YYY-update /robots.txt
cp -R path/to/[docroot]/sites \
acquia-drupal-a.b.c-YYY-update /sites
Tip
For sites with very large quantities of uploaded files, consider keeping the file storage directory
normally kept at
[docroot]sites/default/files
outside of the [docroot] directory. You can then add a
symlink from
[docroot]/sites/default/files
to the file storage directory. This will save considerable time
during migration and future updates.
Setting Up Acquia Drupal
31
These two commands rename your
document_root
directory
"document_root_old"
and rename
acquia-drupal-a.b.c-
YYY-update

"document_root"
:
mv document_root document_root_old
mv acquia-drupal-a.b.c-YYY-update document_root
The directory
"document_root_old"
is now a complete backup of your site's code and the new Acquia Drupal code
base has become your document root directory.
5. Configure Site
Now configure your newly updated site from the browser as described in the
Configure Site
section.
32
Chapter 5. Acquia Network Services
This chapter covers the various services available to you as a subscriber to the
Acquia Network
. These services are
designed to help you manage your Acquia
Drupal
website.
The Acquia Network's current services include a
cron service
, site health monitoring known as the
heartbeat service
,
and spam protection from the
Mollom content protection
service.
Acquia Network Overview
Once an Acquia
Drupal
site is activated and connected to the Acquia Network, its subscription owner and registered
contacts can review its status and profile information on the network.
This information is also available to Acquia support personnel to help them resolve any issues on the site as efficiently
as possible.
The
Acquia Network
(
http://acquia.com/network/dashboard
) offers you an overview of the status of your
subscription(s) through the tabs across the page:
Health
The Health tab (
http://acquia.com/network/dashboard/health
) shows the current online status, subscription status,
support status and unfinished tasks of each of your subscribed sites. Clicking on the "View health details" link of any
site takes you to a detailed overview, including its general condition, Mollom spam-protection statistics, heartbeat log,
code modification warnings, and detailed technical profile.
Messages
All relevant messages - announcements from Acquia services, error messages pertaining to individual sites, and so on
- can be found on the Messages tab (
http://acquia.com/network/dashboard/messages
).
Tasks
Tasks track what needs to be done next for your Acquia Drupal subscriptions. Here, owners can be assigned to tasks,
and the tasks tracked, commented on and marked as completed.
Tickets
If your subscription entitles you to support tickets, this page provides an overview your subscription's support tickets
at Acquia.
Settings
The sub-tabs let you control the following subscription settings:
Site

Site name - for use in overviews and summaries

Site URL - the site URL associated with your subscription
Acquia Network Services
33
Contacts
Add technical and billing contacts to your subscription.
Note
Depending on the service level of a subscription, it may have various, multiple contacts - people
responsible for different aspects of the subscription, including the primary contact (the subscription
owner), administrative- and technical-contacts. The primary contact can add other contacts on a
subscription's
Contacts
tab, who will be notified by email.
Subscription
owners can also resend and
cancel invitations.
Message rules
Granular control of which contacts receive your subscription's
error
,
warning
, and
information
messages.
Cron
If you want to take advantage of the Acquia Network's cron service, set its interval and path here.
Subscription
The messages, current state and other information regarding any individual subscription can be found by clicking on
the subscription's name on the subscriptions page at
http://acquia.com/network/dashboard/subscription
.
Cron Service
Your Acquia
Drupal
site needs to perform certain self maintenance tasks on a regular basis to run well. These "cron
tasks" are run in a batch called a "cron job" and include exchanging information and heartbeat signals with the
Acquia
Network
, removing expired session information, updating database tables and the search index, and so on, depending
on your site's exact configuration and traffic.
Cron
jobs cannot be initiated from within an Acquia Drupal installation. A cron signal - from "chronos", Greek for
"time" - is needed at regular intervals to initiate these tasks. You can follow the
instructions on Drupal.org
[
http://
drupal.org/cron
]
on how to set up your cron jobs with command line tools. The Acquia Network's remote cron service
is, however, an easier solution for utilizing Drupal cron, especially if you are uncomfortable directly manipulating
Unix cron functionality from the command line. It can also be a lifesaver (or at least a "site-saver") in a number of
other situations:

Managing Acquia Drupal sites in shared hosting environments, you might not be granted sufficient access to the
server's operating system to set up cron jobs directly.

Running on a system that does not provide a cron function (Windows is one good example of this).

You do not have access to the Unix command line or other interface for setting up cron jobs.

You notice that the Acquia Network has a simple, effective and intuitive way of taking care of this for you!
The Acquia Network remote cron service is part of all subscription packages. Your Acquia Drupal installation must
be visible from the internet - that is, not behind a firewall or inside a closed intranet.
If you provide your site's URL during the subscription process, the remote cron service should begin immediately. If
you did not provide your URL during registration, you can enter it in the field provided on the
Site
tab of the
Settings
page on the Acquia Network.
Acquia Network Services
34
Figure 5.1. Site URL
You may configure or deactivate the Acquia Network remote cron service at any time on the
Cron
tab of the
Settings
page on the Acquia Network.
Figure 5.2. Cron Settings Page
Here, you can set the following options:
Acquia Network Services
35

How often do you want cron to run on your site?
This depends on the complexity of your site. For most sites, every 5 minutes will be the best choice, but for a less
active site, every hour might be sufficient.

Do you want Acquia to run cron for you?
Select "No" to turn off the remote cron service. In that case, you will need to set up a cron job on your server yourself.
Important
If you have already configured cron to run on your server and choose not to take advantage of the
Acquia Network's cron service, you will still need to tell us how often you will run cron on your
own in the form shown above. This allows the Acquia Network
heartbeat service
to synchronize
correctly with your Acquia Drupal installation.

Cron action path
This is the path to your Acquia Drupal installation's cron.php file. Leave the default "/cron.php" unless you have
changed this in your installation.
After configuring the remote cron service, cron jobs should start to appear in your Acquia Drupal installation's logs:
Administer
> Reports > Recent log entries
(?q=admin/reports/dblog).
Heartbeat Service
Each time it runs its cron jobs, your Acquia
Drupal
site sends a signal to the
Acquia Network
to let the network know
that the site is alive and well - the Acquia Network Heartbeat signal. The
Heartbeats
tab of your subscription's
Health
page shows how long your site has been online.
If the Acquia Network doesn't receive a Heartbeat from your site for more than ten minutes after it expects one (depends
on your
cron signal frequency setting
), it will show your site as offline on your subscriptions pages until it receives
another heartbeat. Whenever your website goes offline or comes back online, you will also receive a notification.
Acquia Network Services
36
Figure 5.3. Heartbeat Status
In order for the heartbeat service to function correctly, the Acquia Network needs to know how often to expect a
heartbeat from your site. If you are using the
Acquia Network cron service
, this process is taken care of automatically.
However, if you are running cron yourself on your own server, you need to tell the Acquia Network how often you are
running cron so it knows when to expect a heartbeat. You can configure this on the
Cron
tab of the
Settings
page of
your subscription, the same place where you can disable access to the cron service. See also:
Acquia Network remote
cron service
Mollom - Content Protection
Acquia
Drupal
includes the Mollom module, which takes advantage of the
Mollom
[
http://mollom.com/
]
web service to
help prevent unwanted and abusive content from being posted on your Acquia Drupal web site without inconveniencing
your legitimate users. Mollom works by analyzing content submitted to your site then automatically classifying it as
"spam" (bad) or "ham" (good). Mollom blocks content that it is certain is spam, and lets content be published that
it is certain is legitimate. The small percentage of content in between (when Mollom is not certain whether a piece
of content is legitimate or not) passes through an extra layer of protection before being published to your website:
The user submitting the content is presented with a simple visual or audio CAPTCHA challenge - a "
C
ompletely
A
utomated
P
ublic
T
uring test to tell
C
omputers and
H
umans
A
part" - that humans can easily solve, but generally
stops automated "spambot" contributions dead in their tracks.
Activate the Mollom module at
Administer
> Site building > Modules
(?q=admin/build/modules).
To allow your site to communicate with Mollom's servers, you need your subscription's public and private Mollom
access keys as listed on your
Acquia Network
subscription page. You can find your keys by navigating to
your
Acquia Network subscription page
[
http://acquia.com/network/dashboard/subscription
]
and clicking on the name of
the subscription in question. Enter them in the fields provided at
Administer > Site configuration > Mollom
(?q=admin/
settings/mollom).
Acquia Network Services
37
Once you have successfully connected to the Mollom servers, you will be able to edit the
Spam protection settings
and
enable Mollom for various types of content and user interaction on your site. In the basic, out-of-the-box configuration
of Acquia Drupal, the five forms shown below can be protected.
As you add and activate modules on your site that allow user input - the contact form, for example - their input forms
are added to this list and can be protected by Mollom. Every custom content type added to your installation can also
be protected.
Figure 5.4. Mollom Protection Configuration
Important
User
registration and password request forms
- When Mollom protection is enabled for these user
interaction forms, Mollom will
always present a CAPTCHA challenge
before submission.
Mollom provides a
"post with no checking"
permission which allows you to give trusted user roles the privilege of
posting directly, bypassing Mollom's anti-spam measures. You should limit giving roles with this permission to friends,
editorial staff, collaborators or other user groups you trust. Mollom also allows site administrators to report content as
spam when deleting it from the site, and it provides a link for users to report emails they receive through their personal
contact forms as spam, too. This information is communicated back to the Mollom servers and is used to improve the
accuracy of Mollom's spam fighting algorithms.
Warning
Legal Issues: Privacy
- Mollom stores data from your site's visitors on its own web servers. It is your
responsibility to make sure that using Mollom does not violate any privacy policies your site may have,
or any laws or regulations that apply. You should obtain appropriate consent from your users before
enabling Mollom on your site. Please read
Mollom's terms of service
[
http://mollom.com/terms-of-
service
]
for more information on these issues.
38
Chapter 6. Subscriber Forums and
Technical Support
Acquia Network Subscriber Forums
The
subscriber forums
[
http://acquia.com/network/forum
]
are the place to go for help, discussion and information from
your fellow subscribers on non time-sensitive issues. For time-sensitive issues, submit a support ticket.
Before posting, it's always a good idea to search the forums to find threads where others may already be discussing
what you are looking for.
Scope of Support Coverage
Acquia provides technical support on Acquia
Drupal
and the Acquia Network for Acquia subscribers. Support
channel access and response times are determined by the subscription and any additional services purchased. See the
Subscription