Unsupported

Drupal requires cookies for user login, but by default no error message is given when a user's browser is set not to accept cookies.

For background and to file new issues, please use the DrupalCI queue. We'll move it to other modules as necessary.

This is the module that takes patches posted in the Drupal.org issue queue and sends them off to dispatcher.drupalci for dispatch to aws testbots.

It provides Project module integration for DrupalCI. The integration serves to make automated testing and review part of the development workflow without requiring effort on behalf of the developer.

Information transfer

All requests are sent to the dispatcher using the Jenkins API. Cron is used to notifiy the dispatcher of a pending test request, which then may need a new aws instance to be provisioned and as such there is a short lag time between the event occurring and the time it has been completely processed.

Triggers

Projects can be configured per environment to test daily for a project, or ever time a commit happens, or each time a patch is submitted as well as per commit.

Displays post information as part of full node views. So far the options are to display created and updated time and author.

Look - this hasn't been touched for a while, and I've noticed now that jCarousel now includes views support, and uses the same jCarousel library that this module did. I suggest using that module instead of this one.

An easy-to-use method for displaying nodes using the jCarousel library for jQuery. Nodes can be chosen via Node Type/Taxonomy, by using a nodequeue, or else by using a hook to feed nodes to the display.

Term Display is a small helper module that provides display options for taxonomy terms on node pages. Options are:

• default (change nothing, and display the terms in the normal way)
• list (remove from the standard display and instead display as a list with the vocabulary name)
• custom (remove from the standard display and instead display as a comma-separated list with the vocabulary name)
• load (remove from standard display and store the term data for the vocabulary in the $node object so it can be processed in the theme: details of how this works are on the handbook page)
• none (do not display the term).

For example, say you have an "Author" vocabulary where you list one or more authors of a piece of content. By default, these author names will appear in the list of terms associated with a piece of content. But if you select "custom" as the display style, the author will appear at the top of your content like this:

If you're looking at using Term Display, please evaluate Content taxonomy, which offers most of what Term Display does plus many extras and so may suit your needs better than Term Display.

Drupal 7