Minimally maintained

Overview

The Reverse Node Reference module enhances Views with reverse relationships for node reference fields.

Drupal 7 status: This feature is provided by References and Views 3. See these threads: #1083902: Backreferencing (listing nodes that reference the target node) and #1188500: Provide a reverse taxonomy field relationship.

Description

Node Reference fields in CCK for Drupal 6 provide relationships to Views that allow you to access fields from the referred nodes of a particular node reference field. These kind of relationships allow you to travel from the child node (the one that has the node reference field) to the parent node (the referred node).

For certain applications, we may also need to do the opposite, travel from the parent node (the referred node) to the child node (the one that has the node reference field). There was a request in the CCK to implement these kind of relationships, but it was basically discarded because the discussed approaches 1) had no support for node revisions, or 2) were going to require MySQL 5.1. See #241078: Reverse node-reference views relationship

This module implements the reverse relationships using the second option. It uses Nested Joins, that requires MySQL 5.1 (MySQL bug #1591) or PostgreSQL.

More information

• How is this different from nodereferrer?

This is a payment gateway module for eProcessingNetwork's Transparent Database Engine (TDBE) API.

A backport of the instant filtering feature added to various Drupal 8 administration pages.

Don't you think the modules administration page is way too long? Can't you find the module you want to enable?

On entering a search term, the filter will immediately hide page elements that do not contain this term. The result is a smaller page that only shows elements that are relevant to the search term.

Revision All allows for centralized management of content type revisioning. Revisioning can be turned on/off individually by type or enabled for all simultaneously.

This module provides an alternative cache.inc file to serve anonymous page requests from xCache. This module makes use of DRUPAL_BOOTSTRAP_EARLY_PAGE_CACHE and implements page_cache_fastpath().

For anonymous users I want to serve pages from XCache, but I didnt want to use memory caching as a replacement for every cache table, only serving cache_page content for anon users from XCache.

Some of the code and concept is inspired by Cache Router, Memcache and XCache however for most parts the code is something I wrote in collaboration with Nick Thompson

The concept

- set a cookie for logged in users (anon/auth flag)
- page_cache_fastpath() checks if cookie is not set
- if cookie is set(auth user): proceed as normal, standard drupal cache functions (no cache)

- if cookie is not set (anon):
-- check if cached page exists in XCache, if it does serve the page
-- if cache doesnt exist in xcache, check db, exists in DB? save it in XCache & serve page
-- page doesnt exist in XCache or DB? Generate page, cache it in DB and Xcache, serve page

This module allows users to set the ownership of a node to a role with full access (view, update, delete). By default the permission will be set to the role of the user.