Actively maintained

DrupalPro Development Desktop is built on Ubuntu 12.04

DrupalPro is a downloadable pre-built machine image for Virtualbox; but may work equally well with VMware, QEMU, Parallels, or the like. It aims to be ready out-of-the-box for building websites, developing, theming, and contributing to Drupal. It's also useful for Trainers looking for a clean stable environment that can be setup in short-order.

Advantages

DrupalPro Development Desktop is easily backed up (even in real-time), easily cloned and customized for each individual project, doesn't require installing gobs of software on your computer in order to build websites, is easy to remove or migrate to another computer, is much more compatible with your production webserver than a WAMP or MAMP stack, and can even be run on a USB3 stick.

Limits how many comments a user may post per day for every 'n' hours, where 'n' can be specified in the settings page..
Adjustable on a per user-role basis.

Panel Variant Page Title allows you to set your page title directly from Panels configuration, and also allows you to take advantage from Panels Argumen

The Code Migrate module is designed to assist developers in migrating websites from Drupal 6 to Drupal 7. It carries out a detailed analysis of the code base of the D6 site and outputs several lists that help to plan a D6->D7 migration.

Introduction

There seems to be no unified library to simplify integrating with webserver softwares and their configuration files like .htaccess (Apache) web.config (IIS) etc. Which makes it almost impossible for Drupal developers to fully integrate with all the powerful features these webservers have to offer without having to be worried about differences, manually editing files, conflict with changes made by other modules and a safe way to keep these settings up-to-date with latest modules’ changes.

These module is an attempt to address all these issues and finally making proper integration with webservers possible.

Version 1

In first version there will be no unified syntax since it’s not an easy thing to implement and requires good understanding of difference between popular web servers. However it will come with some very useful features:

• Module hook to introduce supported webservers , require webserver configs and define some indicators so webserver integration can check whether their changes is applied or not
• Module hook to alter webservice configuration file in text format (For example using regular expression). The running webservice will be send in as a parameter
• Hook for defining new configuration files in different locations (by default root and sites are already defined)

Provides content administration & forms for entities defined in hook_entity_info