Minimally maintained

Sandbox for todo.ly basic form conections.

The purpose of this module is to expose the top node type posters/contributors as blocks in a list format.

This is a light weight module. This is developed in consideration with adding vocabulary images. In some cases your project( E-commerce site) needs to display list of vocabularies with their images.
The vocabulary_image module allows site administrators to associate images with vocabularies. With the association created, an admin can then make a call to 'vocabulary_image_get_vocab_image_path($vid)' from their theme or other PHP code to get image path & display the appropriate image in their desired image format.
One of my project needs to same feature. I searched a lot but not found any solution. Then after all I decided to write their own module and also wants it to contribute. So it can provide some help to reach at appropriate solution for this type of listing.
An admin setting is also available to manage image resolutions, image sizes.
Admin can provide default image in case if no any image is uploaded with vocabulary.

Features :

• Image configuration happens within existing admin/structure/vocab-image menu structure.
• Admins can add default image in case if no any image is attached with existing vocabulary.
• Allows one-to-one vocabulary-to-image relationships.
• Administrators can force images to be a standard size.

The caching layer nor the database caching implementation respect https through the system. This is important because parts of Drupal (core included) generate absolute URLs. These URLs can be cached with a protocol of http:// and then embedded in a page (through nested caching) where the protocol should be https://.

This contains a Drupal database caching alternative that attempts to respect caching via https. The default Drupal database cache doesn't think about https (aside from the page cache). That means you could have html cached with absolute urls generated by Drupal using http in caches like the block or filter cache. This data can then bubble up into the https version of the page cache.

This cache is a small layer of logic on top of the current database cache. So, if changes happen there (non-API changes) they will be inherited in this as well.

How to use this cache

In your settings.php file include this cache backend:

$conf['cache_backends'][] = 'sites/all/modules/database-cache-respecting-https/db.cache.inc';

Then set the default caching class to the one included here.

$conf['cache_default_class'] = 'DrupalDatabaseCacheResepectHTTPS';

The cache includes a whitelist of cache bins (tables) that skip checking and
enforcing https. You can alter this list by adding a variable to your settings.php
file like:

<?php

This is a demo sandbox module

An alternate to vertical tabs/fieldsets to simplifying a form with a lot of fields -- hides a field behind a one time link.