book.module: How to add "previous/up/next navigation" at the top


With book.module default, "previous/up/next navigation" is displayed only at the bottom.
Is it possible to add "previous/up/next navigation" at the top, too?
I would like to make it selectable;
- bottom only (current default)
- top only
- both (bottm & top)

thanks & regards,

User profile improvements

Earlier this week I committed a new profile module to the development branch. I just finished upgrading to take advantage of these new improvements. If you check your account settings (authentication required), you'll notice that I added quite a few fields that let you define your role within the Drupal community or the Drupal project.

Furthermore, updated profiles can be browsed (or filtered) using some of these new fields. For example, click here for a list of Belgian Drupal users, here for a list of female Drupal users or here for a list of documentation contributors.

(Update, March 21: I've made some more changes based on the feedback posted in the comments. The updates are outlined below. You might want to revisit your account settings.)

Template for MT entry and comment export and Drupal import

To do:

  • Automatically create accounts
  • Export MT categories and import to Drupal taxonomy


  • All comments are from the Anonymous user
  • All comments are unthreaded
  • The comment subject is made from the first five words of the comment
  • The import defaults to using uid 1, i.e. the site admin (change the $uid variable to import to another user)
  • All posts are promoted to the front page
  • All comments have a published status
  • MT categories (Drupal taxonomy terms) are not exported


  1. Create a new Movable Type Index template called Drupal Import with import.php specified as the Output File
  2. Cut and paste the following into the Template body textarea
  3. Set the variables below the //set variable defaults comment to the correct values
  4. Save and rebuild the template
  5. Load import.php in your web browser

If the import is successful, the output will be a single sentence listing the number of entries and comments imported.


//set variable defaults
$hostname = "";
$username = "";
$password = "";
$db = "";

Disabling clean URLs

It's possible that a Drupal site that was once configured to run with clean URLs later on stops doing so. After that, almost all content is inaccessible, because the paths being generated are not supported by the hosting platform.

This occasionally happens


This section explains how to help by finding issues to work on, creating and submitting patches.

Finding issues to work on

Most issues are solved by developers that have a need to have them solved, because they are affected by the issue or they are the maintainer and help to keep their module up to date.
Some developers also pick an issue of their liking and start developing and submitting a patch. The following links are collections of such issues to work on:

Novices can start by picking issues that are tagged for novices. You must be logged into in order to view this list:[]=Open&issue_tags=Novice


Patches are pieces of code that solve an existing issue. In fact, patches describe the changes between a before and after state of either a module or core. By applying the patch the issue should no longer exist.


Subscribe with RSS Subscribe to RSS - Drupal 4.5.x or older