Site structure

Gives content access permissions to users if they have access to content that is referenced with Node reference or Entity reference.

An API for browsing next/previous nodes without overloading your database server.

Description

This module allows you to know the previous or next nodes for any given node. This is very useful for providing navigational links to the user without the expensive queries required to dynamically deduce such information on the fly.

The use case is two fold:

Usability/Navigation

For example, on a site with a gallery of images, you want to show a next/previous link with a thumbnail under each image. Your site's visitor click on the link to show new content or browse it.

Scalability

Although the previous and next nodes can be deduced with some SQL work, the queries to do so are very heavy on the database, and can bring a site to its knees. This module solves this problem by storing the previous/next node in a table so lookups are fast. Once the module is installed, it will build this index backwards via cron until all nodes have been indexed. See the "More Info" section below for a detailed post on the positive scalability impacts of implementing this module.

Configuration

The module can be restricted to certain content types to be included in the previous/next indexing. For example, you want the site's visitors to browse through video and image nodes only, but not blogs and regular pages.

You shouldn't use this module unless you're willing to maintain it. Please let me know if you're interested.

This module will *not* be ported to D7 and will not have further development. I will only maintain security fixes. Please use one of the following options:

• Total Admin Control - allows creating multiple dashboards, with a set of conditions and content/blocks/views/cck fields/widgets. very complex because it's based on Chaos Tools
• Homebox - allows creating multiple dashboards with blocks and views blocks
• Dashboard allows creating multiple dashboards (but not per account) for admins to use, containing blocks (very buggy)
• Dashboard for users - allows creating dashboards per user, using blocks (couldn't get it to work)

User Dashboard (udashboard) creates a pseudo administration interface for users who are not administrators. This module it's trying to solve a common problem when you give control of the site to users who aren´t drupal experts. From a single UI it's possible to administer the most common tasks of the site like having a tracker page, administer comments, administer users and creating content.

Currently, it's possible to define 4 pages inside the UI, all of them with custom help messages.

1. Tracker and Welcome Page
2. Comments page

IP to Locale provides IP lookup and redirection services for Drupal sites.

Drupal 6.x

Drupal is set up fairly well for multilingual sites. However, it does make the assumption that each site version will be written in a different language. It is quite feasible however, that there be two versions of a site in the same language. For example, A site which has a UK version, and a version for the Republic of Ireland. Both sites are written in English, but the content varies for each. Drupal's multilingual features provide the perfect tools to allow 'translation' of content from one version of the site to another, but In a setup like this, it may also be desirable to automatically redirect users to a particular version of the site based on their IP address. Drupal's built in Language negotiation does not cater for this...

IP 2 Locale is able to redirect users to a specific site version based on the originating country of their IP address. It can use one or more IP lookup modules to translate the users IP address into a country code. Mappings can then be provided from country code to language code, and these mappings will be used to determine which version of the site to redirect to. Redirections can be configured to happen for the initial page request of a 'session' only (where 'session' is, a user coming from external site), or for every single page request.

Callouts creates a way to display multiple blocks that are related by taxonomy terms. After you place the module into a region on your site, when a user goes to a page any callout blocks (callout is a new content type) with the same taxonomy terms as that page will be displayed in the region.

This Module is great if your looking to show related products in an e-commerence enviroment, or announcments depending on what page of the site your users are on.

In the Admin section (at Admin > callouts) gives you the ability to choose the max number of callout blocks to display, as well as the option to turn on 'random' callouts. When random is enabled, if no callout nodes are found with related taxonomy terms as the page (or if the page does not have taxonomy terms) then the module will display random callout nodes (up to the set max).

NOTE: The way this module retrieves the taxonomy terms is based on the address (a.k.a 'node/%' , where % is the node id 'nid'). If someone knows a better way to retrieve the nid for a node, please contact me and I'll update this module.

Installation

This module, when enabled, creates a new content type 'callout' and also gives that content type access to all existing Taxonomy vocabularies. you will need to display this block in one of the themes regions (at Admin > Site Building > Blocks).

New development is done in the http://drupal.org/project/cer module. This expands the corresponding node reference functionality to enitities. Please focus all attention on getting a stable release of cer as soon as possible.

Cnr is looking for a comaintainer to resolve the remaining bugs. No new features will be handled.

Screenshots

Description

It syncs the node reference between two node types which have a nodereference to each other, so double editing nodes is no more needed. If one node has a reference the other node receives also a reference to the saved node if it is referenced in that node.

Updates

Release 6.x-4.0 doesnt require setting the options to unlimited, all is handled by cck now. The old setting to allow setting to single is no longer present since it is obsolete. To upgrade, run update.php and manualy set the allowed references on each nodereference instance. The older branches are not supported anymore so you should upgrade.

Dependencies

6.x : CCK
Node reference (comes with cck)
7.x: Node reference (included in References)

Example