Utility

The spaces_node module builds on top of the Spaces module by turning nodes into spaces. Included with spaces is spaces_og (which turns an organic group into a space), spaces_user (which turns a user into a space), and spaces_taxonomy (which turns taxonomy terms into a space). The major piece that was missing was turning a node into a space. That is where spaces_node comes in.

Watch the spaces_node screencast demo

Macro Code extends the Macro module to provide automatic exporting of macros to "component" files. A component file is simply a .macro file with one or more macros. Component files should be used to group form submissions whenever it makes sense.

The purpose of keeping form macros (form submissions) in files is to provide an easy way of duplicating settings (database) changes between multiple copies of the same project (such as development, staging & production environments).

Fieldgroup will, as the name implies, group fields together. All fieldable entities will have the possibility to add groups to wrap their fields together. Fieldgroup comes with default HTML wrappers like vertical tabs, horizontal tabs, accordions, fieldsets or div wrappers.

Overview

ZipCart provides a means to download many files at once. Users may select multiple files for download (adding files to a "cart"), then fetch them all as a single bundled Zip archive.

dblogsave helps you hold onto transaction data in a simple way, by leaving it in core's watchdog table.

Provides a helper to clear the watchdog database table.

The module implements an back port of the same functionality of Drupal 7.

Displays all nodes are not represented in the node access database table and
provides a function to repair the table.

Summary

This small module helps theme-developers to deal with cross-browser compatibility. It makes easier to handle different types of non-widespread browsers just as much as it helps with using different versions of Internet Explorer.
The module extends the $body_classes variable in page.tpl.php based on the enduser's browser, and platform.

The module also makes a $browser_classes variable available in page.tpl.php, which stores the data in an array, this way the developer can make use of it as needed, if he does not wish to use the $body_classes variable.

Supported browsers

• ie
• opera
• safari
• chrome
• netscape
• ff
• konqueror
• dillo
• chimera
• beonex
• aweb
• amaya
• icab
• lynx
• galeon
• operamini

Browser version checking

The module creates version classes.

• ie[version]
• opera[version]
• chrome[version]
• safari[version]
• netscape[version]
• ff[version]
• konqueror[version]
• operamini[version]

Supported platforms

• win
• ipad
• ipod
• iphone
• mac
• android
• linux
• nokia
• blackberry
• NetBSD
• FreeBSD
• OpenBSD

Mobile detecting

The module checks if the device is mobile and adds "mobile" or "desktop" class.

Creates a block with a search box that allows you to find/go to a Drupal Node by NID. I use this on a documentation site -> where I used the NID to track specific solutions. I wanted an easy way to be forwarded to a specific node ny using a Node ID.

Response to the practicality of this module

When I wrote this module I thought that this seems really, really dumb -> but within a certain context, this little module makes sense:

This is a helper module to prepopulate newly created webforms and to export / import webforms between sites.

Only tested on Webform 6.x-3.x and 7.x-4.x / Exports between different versions (6.x to 7.x or 3.x to 4.x) will probably not work.

Example usage 1: Prepopulated webforms

1. Create a webform with the required components.
2. Export the webform
3. Edit the webform content type and paste in the content from the export (under Publishing options)
4. Use the standard node add content links and each new content item created should be prepopulated with the exported webform.