Known Issues

View known issues by version:

All versions

xmlsitemap_user module is borked
Ugh, there's lots of crappy stuff going on about when to save the XML sitemap data from the user account form and when to save it because the $account object changes. I'm looking into this right now, but currently the per-user settings are not working on 7.x-2.x or 6.x-2.x.

This means you should not enable xmlsitemap_users until this is resolved. See issue #708078: user submodule is borked for summary.

I get the following warning in my web browser when viewing my XML sitemaps:
This XML file does not appear to have any style information associated with it. The document tree is shown below.

This just means that you are viewing the raw XML page. There is nothing wrong and you can ignore this warning. If you would like to enable a nicer viewing style for your XML sitemaps, you can enable the "Include a stylesheet in the sitemaps." option in admin/settings/xmlsitemap.

If I don't have clean URLs enabled, can I still submit my sitemap to search engines?

RSS Feeder

This documentation page is about the unsupported and obsolete RSS Feeder module. Chances are you don't need to read any further.

RSS Feeder is a simple to use, highly customizable module to generate RSS feeds for your own website made in drupal.

Following are the instructions on the installation and usage of this module. Also read readme.txt once before using as that would be containing latest information.

Node reference views

The Node reference views module is a formatter for the CCK nodereference field. The default displays for node reference fields are just node titles, full nodes, or teaser. This module allows you to use the formatting power of Views module to display the node reference field: this means you can pick any fields on the referenced nodes, show them as a list, table, or grid, all in the place of the original node reference field.


Install the module as usual.

Go to the views admin and create your view. The view should have the same name as the field, including the automatic 'field_' prefix, eg 'field_my_noderef'.

To get started, you can clone the example view that comes with this module: it comes with the argument already set. You can add any fields and sorts and filters. One limitation however is that the order of items set in the CCK field isn't accessible to Views.

Go to the display settings for your field, and pick 'View' as the display option for your field.

Example & walkthrough

Suppose you want to make a music library with node types for albums and songs.

The song nodes have a node reference that points to the album the song is on. Album nodes have fields for artist and year.

Import / Export API QuickStart Guide

Import / Export API QuickStart Guide

The Drupal Import / Export API is a highly flexible framework for getting data into and out of Drupal. In actual fact, it's a framework for getting data out of any one source, and into any other source. However, the most common uses for the API involve having Drupal as one of these sources. So, to make life simpler, you should think of the API in terms of its more limited definition, unless (or until) you reach a point where you need to go beyond this.


Import / Export API


The Import / Export API allows for the definition of data entities within Drupal. The definition system lets data entities be related to each other, and it includes a number of different field types. It also supports a system of import (parsing) and export (rendering) engines, for formats such as XML and CSV. Data entities are able to be exported from, and imported into, a Drupal site, for purposes such as backup, offline editing, data migration, and data transfer between Drupal databases.

Using Argument Selector for selecting and comparing nodes

In a website for comparing products you typically want to show a general list of products that can be sorted. You also want the user to be able to select the most interesting rows for a more detailed comparison. VBO now includes an action that lets you do this - Argument Selector (added in the 6.x-1.8 version).

Argument Selector can be used for any kind of objects that VBO supports, but this example uses nodes. The arguments can be passed to any kind of page. In this example we pass them to another view.

Step 1: Create the target view

Create a new view for the detailed comparison. This should be an ordinary view without VBO. Add "Node: nid" as Argument. In the configuration for this argument, set Validator to Node, set Types to the node type you want to use, set Argument type to "Node IDs separated by , or +" and check "Allow multiple terms per argument".

Add a page display to the view and set an appropriate path for it, for instance "products/detailed". Click Save.

Step 2: Create the action

Go to admin/settings/actions. In the list of advanced actions you select "Pass objects as arguments to a page..." and click the Create button.

There are two fields to configure for the action.


Subscribe with RSS Subscribe to RSS - Site administrators