Home > Articles > Web Development > Content Management Systems

Exploring Drupal

  • Print
  • + Share This
This chapter is from the book

How Drupal Works

One of the great features of Drupal is that you do not need to write code to use it. However, it is useful to have a basic understanding of how Drupal manages its content, and that understanding can come from a superficial look at some of its code. Do not worry: There is little code in this section, and the most important message to take away is that Drupal's architecture is a sturdy one; it can be extended and modified by developers who have already been given specific places to customize Drupal. By using these customization structures, you can add significant new features to Drupal without jeopardizing the overall stability of its operations. You need have no fears about downloading additional modules from the Drupal website and installing them in your copy of Drupal.

When you download Drupal, you get a folder that you place on your web server. The most basic installation is to place its contents in the appropriate location—either the site's root or a subfolder. Note that it is the contents of the folder, not the folder itself, that you should place on your site. A subfolder can be used in the URL, as in www.northcountryconsulting.com/drupal1; alternatively, you can point a domain or subdomain to that folder.

Drupal's Bootstraps and Bottlenecks

The .htaccess file is located at the root level of the Drupal file structure. It is a simple set of Apache settings, the key one of which is that all requests coming into the directory in which Drupal is located are redirected to the index.php file in that directory. By the time they get to index.php, they have been reformatted, but all that is done behind the scenes by Drupal, so you do not have to worry about it.

The request is then routed into bootstrap.inc, a file in the includes folder of the working directory, as you can see in the following code. This means that every page request goes through the same logic that can check for various conditions.

define('DRUPAL_ROOT', getcwd());

require_once DRUPAL_ROOT . '/includes/bootstrap.inc';
drupal_bootstrap(DRUPAL_BOOTSTRAP_FULL);
$return = menu_execute_active_handler();

The $return variable contains the main section of the Drupal page to be returned to the user. After some error checking in index.php, the page is rendered with

print drupal_render_page($return);

Within that function, the page is rendered with this code:

function drupal_render_page($page) {
  // Allow menu callbacks to return strings, or bare content arrays.
  if (is_string($page) || empty($page['content'])){
    $page = drupal_get_page($page);
  }
  // Modules alter the $page as needed. Blocks are populated into regions like
  // 'left', 'footer', etc.
  drupal_alter('page', $page);

  return drupal_render($page);
}

This means that every request for a Drupal page goes through the same bottleneck where additional processing (such as modifying URLs) can take place, and every request to render a page goes through a similar bottleneck where different types of additional processing (such as placing blocks in regions of the page next to the main content) can be performed.

This is a common structure for modern web applications. Facebook applications, for example, consist of a Facebook frame that is created by Facebook independently of the app. The app is called by Facebook to return the center portion of the frame, and Facebook merges them together.

Using Hooks

Drupal's hooks are somewhat similar to bottlenecks. At specific moments, such as when content is about to be viewed, stored, or deleted, or when a user has just logged in or logged out, Drupal checks the modules (including ones you have downloaded and installed yourself) in case one wants to be involved. Thus, a module can modify the data to be displayed or it can do something to reflect the user's log in or log out. The implementation of these hooks is provided in the code for each module. (Not all hooks are implemented in all modules.) Each hook has its own syntax, and it is named with the module's name.

For example, the hook that is called when a node is about to be viewed is defined as shown in Table 2.1.

Table 2.1. Node View Hooks

Version

Syntax

Return Value

6

hook_view($node, $teaser = FALSE, $page = FALSE)

$node (possibly with changes)

7

hook_node_view($node, $teaser)

$node (possibly with changes)

For a module called mymodule, the actual implementation in the module file would be mymodule_view or mymodule_node_view.

Unless you are writing your own module, do not worry about this, but it is useful to understand how Drupal manages its operations. If, for some reason, you are tempted to bypass Drupal's event-dispatching mechanism, you will break the hook structure. (Fortunately, it is not easy to bypass the event-dispatching mechanism.)

Drupal's File Structure

The whole functioning of Drupal depends on this combination of .htaccess and index.php. For it to function properly, the files must be in the right place. If you start to move them to improve on the file structure, you will break this robust structure.

The file structure does allow for several types of optimization within this structure, and you should consider them before you start your installation. Figure 2.9 shows the basic structure of a Drupal folder. You can see the index.php file; .htaccess is hidden. Two folders should draw your attention: modules and themes. These contain the files for modules and themes that either ship with Drupal or that you can download.

Figure 2.9

Figure 2.9 Review the Drupal file structure.

The temptation for many is to download modules and themes into the relevant folders. However, notice the sites folder in Figure 2.10; within it is an all folder, containing its own modules and themes folders. Those are the folders into which you should place your downloaded modules. That means that the main modules folder contains only the modules that were downloaded with Drupal itself. The ones you have added are in their own folder. This can make maintenance and updating much easier.

Figure 2.10

Figure 2.10 Use site-specific folders for modules and themes inside the sites folder.

Furthermore, you can add additional folders within the sites folder, each with its own modules and themes folders. That way, a single Drupal installation can serve several sites with several sets of themes and modules. All this works because of Drupal's runtime structure.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020