This module provides a graph where you can see the size of the cache tables and labels marking some of the events that may empty the cache.
You can see how much damage those events do to your cache size.
The events recorded are:
More to come...
The objective of this module is to provide a model entity and entity administration interface to kick-start your entity development.
While entities in Drupal 7 are a very useful abstraction and can be great tool for suitable projects there are some challenges facing developers wanting to use them:
A small module that allows you to add CSS code on your site from a web interface. A very simple way of letting designers and coders who don't have full access to the server do CSS-adjustments on a running site without direct access to any files.
The supplementary CSS is written to a small file in the theme folder and can later be implemented into the "real" CSS-file—or left as they are. That will work equally well, but not be quite as kosher.
You can add supplementary CSS-code for each theme individually.
The Bugtracker module is a simple tool to log issues during the developement process of a website. It has his own data scheme so it will not interfere with any other modules neither appear in node management or search engine.
drupal select two cascading menus, select a city under the province
[not a module] This is a script to run the database upgrade of a Drupal site from 6 to 7 while re-using an established codebase.
Update: This script is deprecated in favor of a two-command process:
Provides integration with Libraries API (2.x-dev) and a Drush Make script to download the google-checkout-php-sample-code.
This project is aimed at providing basic foundation for integrating your online store with the Google Checkout API using PHP.
placeholder text
This Module Processes Mass Operations in batches(batch_set()) and takes php code and executes it number of times you want it to.
I hope this module will help Develpoers in some or another way.
One can run similar code for multiple times without getting "memory limit exceeded" or "mysql server gone away" error.
Currently you can run cron for number of times you want by typing drupal_cron_run(); in Code to execute: field and putting number of times you want to run Cron.
Well, to make them play nice together anyway...
I was looking for a production/staging server build script or appliance that had LAMP, Webmin, Aegir, ISPConfig, and all the Drupal dependencies on top of a long term support (LTS) version of uBuntu.
On top of web and database services, I also wanted email and DNS, open source anti-spam and anti-virus, a firewall, and protection from DOS and other similar attacks. I also wanted all my admin interfaces to use SSL and I wanted secure SMTP enabled.
Basically, I wanted the offspring of a debaucherous affair between Webmin, Aegir, a slightly hardened LAMP, ISPConfig, and Drupal. I wanted - WALID.
Meet WALID. It's that genetically engineered super offspring.
WALID's the output of a build script that smaller-scale Drupal developers can use to quickly build a production server on a Cloud or Dedicated VPS (or download as an appliance). For Drupal developers that need more than shared hosting but aren't experienced in building or maintaining Linux servers, this will get you going. For developers who have reached a certain level in their Drupal-fu but who aren't experienced with Linux, WALID is a relatively secure and stable Drupal-centric production environment that can be managed via secure web interfaces by even non-Linux pros. [This is the goal anyway...]
