Maintenance fixes only

Summary

Field UI Plus adds a modest amount of data to the administration configuration
page provided by the Field UI module. This helps to see the important field
instance configuration settings at a glance, without having to walk through
numerous subpages.

Cautions

This is intended for use with the default Drupal 7 administrative theme, and
will no doubt look terrible if used in other administrative themes.

Rationale

The Field UI module provides an administrative user interface to the Field
module functionality that works well for the basics, but any earnest use of
fields will quickly run into its limitations. Suppose, for example, that you
are working on a project wherein the node entity portion of the data model is
described by a few dozen content types, a hundred or so different field
definitions, and more than two hundred field instances spread across those
content types. This is not unreasonable once you start thinking about the sort
of Drupal site that supports the Economist, for example, or other similar
business initiatives. Your data model will invariably evolve as the project
progresses, and a great deal of the administrative work flow is defined, or at
least channeled, by the settings in those few hundred field instances: which
widget to use, the messages displayed to the user, which fields are required,

Motivation

Views offers a "CSS Class" setting that can get classes in the markup that wraps your view content, but themers often need these classes in the top level of the markup (the block container), not nested inside.

What it does

This module does some nifty logic that adds CSS classes configured in your view to the block container (with "-container" appended) to help with styling and re-usability for view blocks, potentially across many different views and displays.

Usage instructions

Just turn it on! The settings you have configured for your view's "CSS Class" will now be in the block container's classes. There is no configuration and no UI.

--

Why should I?

Check out WebbyKat's article under the section "Why You Want to Add Classes to Your Blocks"

What about the Block Class module?

Block Class is cool too - but this module relies on the settings already configured in views, so there is no additional database storage or configuration aside from what you already have in your view.

What if I don't want a whole module for this?

Project for storing (parts of) a legacy distribution used by Fedict.

This module adds a contextual link to every form that lets you easily find out form's ID and name of hook_form_FORM_ID_alter() hook.

Usage:

By hovering over any form you will see a contextual link available. By expanding the link you will see the form ID. Click on the link and you will see a modal window with copyable form id and hook_form_FORM_ID_alter() hook suggestion.

Video on how to use it: http://www.youtube.com/watch?v=WPMB8g-CHc4

Created and sponsored by Tim Kamanin (TimOnWeb Drupal development).

I couldn't find any decent modules for allowing you do do volume (bulk) pricing such as buy X amount of a product and price is Y.

I've also added a cart message to notify a consumer about the possible savings if they buy more of said product.

A hastily thrown together module for debugging Solr indexing of Durpal nodes.

Provides a tab on nodes for users with 'administer apachesolr' permission with 2 capabilities:

1. Enter a search phrase to view the scoring details for that phrase for the current node and the top ranked node.
2. A button to force the current node to be immediately re-indexed. (as opposed to putting it in a queue to be reindexed on some future cron run.)

This should be trivial to upgrade to Drupal 7. I'll probably do it at some point, but if someone beats me to it, please post a patch and I'll commit it & roll a release for everyone.