Maintenance fixes only

Drupal 8 Version

The 8.x-dev version currently is undergoing a massive streamlining in the translations-export and translaions-import commands to eventually move this component to core (#1820542: Make customized translations deployable). Please check on updates for syntax changes. If you want to track this or help, see #2922656: Roadmap to stable D8 release.

Overview

Drush commands allowing languages to be added, switched, enabled, disabled, imported, exported and update prefix from the commandline. This module only provides drush commands, so you will see no functionality in the UI.

Atrium Leads is a simple Open Atrium feature that provides a "Business Lead" content type.

This can be used for keeping track of the status of any kind of business lead, ie. potential clients, RFPs, job offers, or even for tracking candidates for hire.

It offers a simple content type with fields for Description, Link, Contact Information, Keywords, and Status (New, Contacted, In progress, Closed, Abandoned).

It also provides views for navigating through leads by status and tag. Everything is based in Views and CCK so further customization is possible.

Overview

This module brings various improvements to the core Taxonomy module.

Features

• Adds a delete link in the vocabulary terms list
• Adds an option to not allow duplicate terms in a vocabulary
• Views integration - provides a Views argument handler which adds the capabality of showing the results of related terms' nodes (e.g. If you have a view list for the term "Drupal", and that term is related to "Drupal core", nodes that are tagged with "Drupal core" will also show up in that view)

API functions

• Provides an equivalent to taxonomy_get_term_by_name() which adds an extra parameter ($vid) for restricting the search to a specific vocabulary
• Provides an equivalent to taxonomy_node_get_terms_by_vocabulary() which saves a database query by searching for the terms directly in the $node object.
• Provides an equivalent to taxonomy_get_tree() which gets a more useful taxonomy tree, with "nesteds" terms in an array that you can access with $term->children

Todo

• Improve documentation and function signature for taxonomy_additions_get_nested_tree()
• Add code samples for the API functions provided by this module

Credits

An image diaporama (slideshow) using Dewslider flash player.

Provides CCK Image Field formatter for Dewslider.

Allows adding to/editing terms of/removing terms from vocabularies per role.

You have set up some vocabularies (with some terms) like Color (Red, Green, Blue) and Shape (Toroid, Cube, Sphere). Maybe you even have a vocabulary that controls who can view a specific node (with terms) like Access control (Editors, Colleagues, World). Here comes trouble: your precious editors want to add more Colors, or reorder the terms of the Shape vocabulary (probably they want to see Sphere before Cube, who knows,) and you do NOT want to grant your editors the administer taxonomy permission, as it grants too much power (and that implies too much sharing of responsibility). Without this permission they were NOT able to do the mentioned tricks: adding terms to a vocabulary but not to another, reordering/editing terms of a vocabulary but not another's, etc.

These problem of yours is the past--just download and install vppr.module, and set it up at Administration >> Site configuration >> Vocabulary permissions.

Exposes Drupal resources (e.g. entities) as RESTful web services.

The module makes use of the Entity API and the information about entity properties (provided via hook_entity_property_info()) to provide resource representations for all entity types (nodes, comments, users, taxonomy terms, ..). It aims to be fully compliant to the REST principles.

Developers can also implement custom resources that can be exposed via the same interface (example in restws.api.php). See the README.txt for further design goals and checkout the documentation page.

#D8CX: I pledge that RESTWS will be obsolete on the day that Drupal 8 is released, because we have REST module in D8 core now!

Features and differences to the Services module:

• Provides only RESTful services (no message-oriented or RPC-style web services like SOAP, XML-RPC etc.).
• Builds upon the Entity API, to provide support for all entity types out of the box.