Content display

Warning: This project has been abandoned. Its functionality can be found in other modules and via tweaks in the theming layer.

Block Party is an aggregation of block module tweaks.

• Admin designates if block visibility is controlled by block module or context module.
• Show Only One Allow blocks to be configured to "show only one" block instance per region. When a block provider module (block, menu, etc.) for a given region is configured to "Show Only One", only one block of that type will appear in that region. This is handy when you have cascading menus or sidebars that you want to replace one another; but you don't want authors to have to tweak visibility through the block or contexts interface.
• Allow block headers to be tagged as h3. This adds an attribute to blocks that theme templates can use to determine if h3 is suggested.
• Allow block headers to be tagged invisible. This is done with a css class "element-invisible" which allows the headers to be accessible without them being visible.

While Drupal provides capabilities for commentng for both anonymous and authenicated users, it provides no easy way for authenticated users to post comments anonymously without having to manually l

This simple module allows you to set a book depth limit per content-type.

Intro

This Drupal 6 module effectively creates a site-wide Views exposed filter for taxonomy terms. It creates an "exposed" View term filter displayed in a block as a <select>. One block can be created per vocabulary, then the filter used on multiple Views.

It was created in the Summer of 2010 for a client project. It has been tested and is currently running in a high traffic environment. I'll continue development if it is found useful for other sites. Let me know. Note: There are todo comments at the top of the module file.

Description

Each enabled taxonomy creates a block containing a
field listing the terms and a submit button. A View is created using a filter titled "Term default" and optionally a cache titled "Time-based Per Term".

When the form submitted, the selected term is saved as their default. When they access a View, their default term for the selected vocabulary is used to filter the View. Any number of Views can use the same filter.

Example use

Allow the user to select their current location, and filter to only show content related to that location.

Dependencies

1. Taxonomy
2. Views

Recommended

1. Session API: http://drupal.org/project/session_api

Concerns

Intended to expose various Drupal Commerce administrative tasks and functionality to the context_admin module.

Slate is a nodequeue add-on created to manage daily queues of nodes with fine-grained control over elements of both chronological placement and absolute positioning.

For instance, imagine you have a busy site homepage and want to schedule out a day of stories. With Slate you can map out the day by adding Story A at 08:00, Story B at 09:00, and Story C at 10:00. Additionally, perhaps you want Story A to be the top story for most of day after it is published. You would insert it at 08:00 and Position 1. Thus, at 10:00 you would see the following node order:

Story A
Story C
Story B

Then, at 13:00 you want New Story to be the top story, so, you would insert it at 13:00 Position 1. This displaces Story A in the top slot, and forces it back into chronological rotation. At 13:00 you would see:

New Story
Story C
Story B
Story A

You can perform the following with an arbitrary number of positions, enabling you to, say, keep a node in position 3 all day long, even well positions 1 & 2 are always the latest.

Slate allows you to create an arbitrary number of queues and subqueues are generated on a daily basis (options to schedule on other intervals might be forthcoming if there is demand).

Slate provides a node edit form group for creating insertions, and several admin features on Slate owned nodequeues.