Troubleshoot installation problems

Links to some of the more common installation issues are listed below. More troubleshooting information is available at the Troubleshooting FAQ.

Fatal error: Allowed memory size of n bytes exhausted

The error "Allowed memory size exhausted" indicates that Drupal needs more memory than has been allocated under current settings. This error can be resolved by adding an extra line to Drupal's configuration files.

Failed to connect to your MySQL database server

The installation script cannot connect to the database. Check if the username, password and hostname that you provided are correct.

Cannot create directories 'files' or 'private'

The installation script needs permissions to create these directories inside the sites/default folder.

Cannot write to configuration files settings.php

The installation script needs permissions to write to the configuration files settings.php.

Blank page (White Screen of Death)

Occasionally the page is completely blank (No content. No errors.) This is what is sometimes referred to as the "White Screen of Death". There are several reasons why this might occur.

Calendar Module How To

Here's a tutorial video with a detailed look at the Calendar module and how it interacts with the Date module, Views and CCK. Covers some of the differences between date field types and highlights the changes you need to make to feel comfortable using Calendar.

Drupal tutorial video about using the Calendar module. Running time is about 22 minutes.

Gigya (7.x-4.x) - Configuration & Customization

Settings

The module can be configured from the Configuration>>Web services>>Gigya settings menu.

Have content authors automatically vote

Here's a D6 version of this.

A very simple module to have a user vote for content automatically as they create it. Have called this module autovote (autovote.module).

1. Create a directory under modules named autovote.

2. Put the following in autovote.module:

HOWTO have the user login block in a consistent language at customizing the block title ?

This is the approach I have followed, there might be others :

This works with 2 languages and the principle is the same with more languages. The idea is to create one new block per language and to invoke some php code to insert the user login block content.

Hierarchical Select in a block as a taxonomy filter

I've created a sample module that creates a new block which allows you to filter by Taxonomy term. The code is very clearly documented, to make it easier for you to adapt it to your needs.

The block is defined by a hook_block() implementation:

/**
 * Implementation of hook_block().
 */
function hs_taxonomy_filter_block_block($op = 'list', $delta = 0, $edit = array()) {
  if ($op == 'list') {
    $blocks['hs-taxonomy-filter'] = array(
      'info'   => t('Hierarchical Select term filter'),
      'weight' => 0,
      'region' => 'left',
      'cache'  => BLOCK_NO_CACHE, // Drupal Forms may never be cached.
    );
    return $blocks;
  }
  else if ($op == 'view') {
    switch($delta) {
      case 'hs-taxonomy-filter':
        $block['subject'] = t('Filter by term');
        $block['content'] = drupal_get_form('hs_taxonomy_filter_block_form');
        return $block;
    }
  }
}

Besides that, there are a form definition function and a form submit callback:

<?php
/**
* Form definition function; Hierarchical Select Taxonomy Filter Block form.
*/
function hs_taxonomy_filter_block_form($form_state) {
$form['filter'] = array(
'#type' => 'hierarchical_select',
'#title' => t('Filter by term'),
'#description' => t('This is a pointless description.'),

Pages

Subscribe with RSS Subscribe to RSS - Site administrators