Developer tools

Provides an APC status and cache reporting page, accessible by a link on the status report page.

Installation

APC Status requires:

This is a companion piece to the Google Analytics module.

Google Analytics is a free service that tracks users, demographic, and statistical data. On a typical site it is easy to set up --especially in Drupal using the Google Analytics module. Under a typical set-up Google Analytics tracks a user as he/she navigates from page to page within a site. This is fine for a typical site where every action on a site requires a new page view. What if, however, the site owner wanted to track how a user is using the ajax form built into views or some other custom ajax event. Google Analytics has a control for this called Event Tracking.

Event Tracking is a way to track user interaction with out registering a page view. Using Google Maps as an example site, event tracking would allow the user to track Zoom, Drag, and View Change events without contaminating the page view statistic.

In the long ago days, I had a collection of shell scripts. They got bigger and wilder and more powerful.
But the helped me automatically sync Drupal 4 sites between dangerous places, places that sometimes didn't even have shell access, and occasionally not even FTP, just a web file manager...

Then a while later, along came drush, and a number of these scripts were replaced by it, yet a larger number lived on, and became drush-i-fied.
Automatic site cloning, FTP sync support via drush, databse conversions from prefixed to non-prefixed and back, on the fly, one-liners to do powerful things.
A small amount of those things tried to make it into drush proper, but most remained on the fringes.

Then later, drush introduced site aliases, which completely replaced my site sync 'site descriptions' with an array that did the same job, so I rewrote my sync scripts to use that method.

And later still, I added new tools to
- provide a wizard for first time setup of site aliases
- automatically generate patch files recording your local changes, before downloading code updates, upgrading, and re-applying your patches
- get the site status report to tell you about missing modules! Which no part of Drupal currently actually does.
- perform drush commands over the wire, through a WEB interface, even if you don't have ssh access !!
..
.

Overview

Code per Views Display (CPV) creates a display extender plugin for Views that allows Views administrators the ability to add custom CSS and Javascript into any display. The CSS and JS code is stored in the display and served as as either inline code or from a file.

CPV is intended for use by Views (i.e. site) administrators.

Features

• Add custom CSS or JS code to each display.
• Serve code either as inline or from file.

Use Cases

CPV is useful in cases where:

• you want to allow views admins to theme a particular display without granting them access to theme files;
• you want to apply CSS and JS code to a display across all themes;
• you want to apply CSS and JS code to a display without modifying an existing theme or creating a sub-theme.

Requirements

CPV requires Drupal 7 and Views 3. It also requires the Views UI module to be enabled, as CPV has no effect otherwise.

Usage

Install and enable the CPV module, then go to "admin/structure/views/settings/advanced" to enable the display extender, "Code per Display". In each views display, a "CSS" and "JS" field will allow custom code to be added under the "Advanced" fieldset in the display settings.

This is my first module i'm sharing with Drupal.org.
FICWR (Flag inappropriate content With Reason) Allows users to flag inappropriate content on specific content types.

Generic helper module to allow external resources such as CSS, JavaScript and images to be fetched and cached locally.