Developer tools

Description

The Mobile Tools module provides Drupal developers with some tools to assist in making adjustments to your site based on the visitor's device.

• Contextual switching of content and layout
• Exportable configurations using Spaces and Features
• Define your sites via domain, sub domain, path, path pairs and query string
• Server side feature detection using Browscap
• Automatic redirection to a site based on device group
• Mobile bookmark popup/Add to home screen notification
• Media Query builder
• anything else we can think of!

Mobile Tools integrates with the following modules to enable the described functionality

• PURL
• CTools
• Context
• ThemeKey
• Browscap
• Spaces
• Panels
• Features
• Context HTTP Headers

Mobile Tools 3.x

Updates:

• #1717242: Add support for browser parent detection in mobile_tools_browscap
• #1713558: Add support for "Chosen" to select user agents in mobile_tools_browscap
• #1687834: Remove strict dependency on Spaces

Converts form-item help text into JavaScript tooltips. The dev version now features form-id based tool tip activation (for any tag with class "description").

Introduction

Uploaded-Files-Mover moves uploaded files to user-defined directories.

When uploading files with the FileField (CCK) or Upload (Core) module, Uploaded-Files-Mover will kick in and move the files to the specified directory. The paths can be set for each content type and may contain placeholders (Token support planned).
Fields and uploads can be enabled separately.

A cleanup routine will clean the filesystem from empty directories. This can be started manually or by running cron.
After changing path settings, the files can be moved to their new directories using a batch process.

Errors are tracked in the watchdog.

Current development release needs testing, but is considered stable.

Features

• Moves files uploaded with Filefield (ImageField) or Core's Upload module to directories specified with placeholders
• Destination directory per content type and field
• Move files in batch process after changing destination directories
• Cleanup and restructuring as cron task
• Error tracking in the watchdog

Alternative modules

FileField Paths

http://drupal.org/project/filefield_paths
Pros: Uses Token and Transliteration. Supports restructuring after rule change to a certain point. Supports Core's Upload module.

This project aims to take advantages of the Ubiquity addon for Mozilla Firefox. The module provides a web-based interface for authoring Ubiquity commands that can then be automatically shared as well as some pre-packaged Drupal-related commands available from the project page.

This module provides a simple interface for controlling your bot through your website. It uses a javascript/ajax-based IRC widget to send and receive your bot's messages. The bot must already be running on your website in order for the interface to work.

This module depends on the bot module.

Pretty much every import/export module for Drupal (and there are some) has a tendency to implement their own hooks for retrieving information about node fields, and the CCK support that comes with them. Also, pretty much all of these solutions have a tendency to tie their hooks and field discovery to their module in some kind of way.

If you are a module developer and want to retrieve information about which kinds of stuff exists in a node, and what you can do with it... where do you get that information? Drupal core does not provide a registry for all node properties, let alone additional information like schema information or a standardized way to retrieve or set that data. CCK covers only a part of the whole node, disregarding the more fundamental properties like node author or creation date.