Developer tools

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.

This is a core set of modules used to power and customize the OpenPublish distribution.

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.

Provides an alternative to the core CSS preprocessor.

DrupalORM provides a programmatic ORM interface to nodes and their corresponding CCK fields.

Assume you have a content type called "page" with the following node and CCK fields...

• Node title
• Node body
• CCK Field "field_desc"
• CCK Node reference "field_ref" which points to content type "story"

You could query "page" content type in the following ways...

orm('Page')->find(array(
  'Page.nid' => 34
));

$nodes = orm('Page')->find(array(
  'Page.field_desc' => 'foobar',
  'Page.title' => 'hello world'
));
// $nodes will be an OrmNodeCollection object
print $nodes->{0}->title;
print $nodes->{1}->title;
// Or you can also do
foreach ($nodes as $node) {
  print $node->title;
}

Assuming the corresponding nodes exist, both of these will return an OrmNodeCollection object which contains a set of PageNode objects. Also, any story nodereferences will be populated recursively....

<?php
$nodes = orm('Page')->find(array(
'Page.title' => 'bup'
));
// Prints title of corresponding Story node which is defined via CCK nodereference.
print $nodes->{0}->FieldRef->{0}->title;
// You can also do this
$nodes->{0}->FieldRef->{0}->body = 'Hello World';
// Now save the changes. There are many ways to do it...
// Method 1
$nodes->saveAll();
// Method 2
$nodes->{0}->save();
// Method 3