Actively maintained

The Facebook Share module enables Drupal site administrators to add a Facebook Share button to selected content type nodes in their website(s). The motivation behind this module was the TweetMeme module which allows users to retweet about a given website node.

The Facebook Share module gives Drupal site administrators the ability to choose the following settings:

• determine content types to display the Facebook Share button on
• whether to display the Facebook Share button on the teaser, full view, or both
• what button type to be displayed (box_count, button_count, button, icon_link, or icon)
• what share text to be displayed on the button (Share by default)

When the Facebook Share module is enabled for a content type, website viewers can click the Facebook Share button to share a link to that node in their Facebook stream.

Benefits of using the Facebook Share module instead of modules that allow users to select from a variety of social networks (ex: Add to Any Share/Bookmark Button, Service links, and FB Drupal):

You need this module if you have a node with taxonomy term reference and a nested menu tree with taxonomy terms. And you want to keep menu expanded up to the term referred by current node.

Module provides integration with Taxonomy Menu.

This small module is designed to help you performance-optimize your use of input filters and input formats.

D7 version now available.

Filter Check does the following:

• Shows which individual input filters cannot be cached by marking them with an asterisk on the format configuration page.
• Shows which input formats cannot be cached by appending an asterisk to their names.

How is this useful?

An input format consists of one or more input filters applied consecutively. The text you input (for example the body of a node) is usually processed by several input filters - those that are enabled in the format that you selected when you input the text. This processing may take significant time, which is why Drupal tries to cache the result so that the processing does not need to be repeated unnecessarily.

However, the output from some filters cannot be reliably cached (the PHP evaluator is an example.) Using such a non-cacheable filter prevents caching for all text which uses that format whether or not the functionality provided by the non-cacheable filter is actually needed. Clearly it makes good sense to avoid using a non-cacheable filter format unless it's really necessary.

This module provides a tree-based style plugin for Views. It is equivalent to the tree-based style template from Views 1.

It is based off of the list style. Although it generates a nested view, there is still only a single query run for the view making it quite performant.

The 1.x branch is compatible with Views 2. The 2.x branch is compatible with Views 3.

Usage

1. Create a new view using the Fields row style. Populate it with the appropriate fields you want.
2. Select the Tree (Adjacency model) style plugin.
3. Select the linking fields in the style configuration panel. Generally, you will want to link from a nodereference field to the nid on the same node type. That is, the nodereference field is used as a pointer to the "parent" node.
4. Save and enjoy.

Compatibility

This module has been tested and used with the following relationship-oriented modules:

• Taxonomy (in core) - parent/child relationships
• References - node and user references
• Relation - references between any entities (D7 only)
• Entity reference - references between any entities (D7 only)

• Have you ever wondered why, after defining an alias like about-us for, say, node/123, your pages are still riddled with those ugly machine-generated tabs and links like /node/123/edit, node/123/revisions etc.?
• Likewise for /taxonomy/term/% and /user/% links: did you expect to see /dries/track but got /user/5/track?
• Do you find that your browser address bar also shows those ugly numbers instead of your aliases?
• Have you ever been annoyed that upon clicking the Edit tab on, say, the about-us page, blocks that you configured to be visible on all about-us/* pages suddenly disappear?
• In short, would you like your human-readable, SEO-friendly aliases to be carried through on all your tabs, links, Views, and blocks, on all your pages, not just on that single aliased base path?

If so, then this little module is for you.

This module allows you to profile your Drupal application using the XHProf profiler, Tideways and uprofiler (PHP 5 only)

Use community documentation to install/enable required PHP extension

XHProf is a hierarchical profiler for PHP. It reports function-level call counts and inclusive and exclusive metrics such as wall (elapsed) time, CPU time and memory usage. A function's profile can be broken down by callers or callees. The raw data collection component is implemented in C as a PHP Zend extension called xhprof. XHProf has a simple HTML based user interface (written in PHP). The browser based UI for viewing profiler results makes it easy to view results or to share results with peers. A callgraph image view is also supported.

It also provides a native Drupal UI (as opposed to facebook's original php front end) to view the profiling data. Having this in Drupal provides several advantages:

• Simpler setup
• No need to setup extra vhosts
• Limit access via roles and permissions
• Use alternative storage backends such as MongoDb

D8+ version also supports:

• Profilers: XHProf, Tideways and uprofiler (PHP 5 only).
• Append --xh-link and Drush 8 will save a profile to the same directory that this module uses. Browse Drush 8 profile data with this module.