Seeking co-maintainer(s)

Features Extra provides faux exportables (via Features) of several site-building components.

Taxonomy

Drupal 6: Supports exporting taxonomy vocabularies. To export a vocabulary, install FE taxonomy, go to vocabulary edit page, assign it a "machine name," then export it with Features as usual. As a bonus, this allows you to edit the "module" property of a vocabulary. Views support (by machine name) is also provided.

Drupal 7: Exporting vocabularies is supported natively by Features in Drupal 7 so it has been removed from this module. If you need to export taxonomy terms in addition to the vocabularies, you can do this with the UUID Features Integration module.

Nodequeue

Only nodequeue definitions are supported. To export a queue, install FE Nodequeue, edit your nodequeue, assign it a "machine name," then export it with Features.

Block

To export a block, install FE Block, edit your block, give it a "machine name," export it with Features. You can export block settings (region settings, visibility settings, ...) of any block, and the content of blocks created with the Block module from Drupal core.

Menu Editor enhances the menu editing form with inline text fields for title, path and description, and provides placeholders for new items.

This way, it reduces the number of page visits needed to create a site's menu structure, and eliminates the need for dummy nodes.

Menu editor attempts to unify content creation and menu editing, solving the same problem as

Features

Inline text fields for title, path and description: In each row you get inline text fields for title and link path. This means, you don't need to go to a new page any more to edit the title or destination of a menu item!

Tabindex: The tab index is modified to skip the annoying checkbox fields ("Enabled", "Expanded", "Delete").

The MongoDB module suite for Drupal 10 stores data in MongoDB instead of the default Drupal SQL database.

For Drupal 11/10 site administrators

It means a faster Drupal and better logs, without a line of code.

• it provides a more usable user interface to access logs, and a faster database logging than core, without the complexities associated with external logging mechanisms like the Elastic Stack (BELK).
• it provides a faster implementation of the Drupal Key-Value store and Queue API
• overall, it provides a simple way to reduce the load on your SQL database server, without needing complex configuration or having to write a single line of code.

For Drupal 11/10 project developers

It means easy project development using MongoDB.

We need to have one good module. Not a lot of half good.
#894680: Merge similar "node repeat" module

This module allows creating multiple repeats/duplicates/clones of nodes based on date sequences. The date sequences are created with the Date Repeat module (part of Date). The nodes must have a CCK Date field, which in the new nodes created by Node Repeat are populated with dates from the sequence. A typical use case might be for creating an event that repeats regularly and for which your users need to Signup.

Node types that have one or more Date field(s) can be set to allow repetition by selecting the Date field to use. If a node type is set to allow repetition then a Repeat tab will appear on nodes of that type to allow creating/editing repeats for that node. Under the Repeat tab if the node is already part a sequence then options for editing that sequence are displayed, otherwise options for creating a sequence from the node are displayed.

Documentation

Usage and Features for 6.x-1.1

For unstable versions please take a look at the release notes.

Known issues

#927452: DST problems

Roadmap

#894680: Merge similar "node repeat" module