Developer

Drake is a module for Drupal that lets you execute your CakePHP applications inside Drupal. It provides a bridge between Drupal and CakePHP, allowing your CakePHP applications to be run with or without Drupal, with no need to change your source code.

What is CakePHP?

CakePHP is a rapid development framework for PHP. It helps developers build robust applications, fast. Here’s what the CakePHP team says:

This module is a simple Second Life framework, allowing objects inside Second Life, written in LSL script, to interact with applications on your Drupal web site, and do neat things.

To discuss this module, and other aspects of Drupal and Second Life integration, you can subscribe to this group.

Requirements

This module requires Drupal 5.x, and PHP 5.1.x.

I have never had the time to develop this module as planned. I believe that other modules now available may do what it aimed to do. Please contact me if you can confirm this (or want to take this over).

RESTfulness lets you build and manage a REST API to a Drupal site via administrative pages on your Drupal site itself.

In the simplest use of RESTfulness, any functionality that is currently available via a menu hook can be exposed as a REST function. Using the full complement of the standard HTTP verbs (GET, POST, PUT and DELETE), you can provide, for example, a blog API that looks like this:

• GET /blog/entry/add (get "new blog entry" form)
• POST /blog/entry/add (post new blog entry)
• PUT /blog/entry/[nid] (edit blog entry)
• DELETE /blog/entry/[nid] (delete blog entry)

You use the Accept: header of the HTTP request to specify what kind of content you want to get back. This content type is mapped to a theme. So you might specify text/html or application/xhtml+xml to request a response in (X)HTML. Or you might ask for text/xml or application/xml to get an XML version of the same content. The content type - to - theme mapping you specify determines which theme gets used.

All of this configuration happens via administrative pages, and the REST functions and content type mappings you define are stored as Drupal nodes. Hence, your API itself becomes content that you can manage using the full gamut of Drupal capabilities. You have the ability to insert code as "glue" to connect your REST API to Drupal core functionality and modules, but RESTfulness aims to provide as much GUI-based configurability, and management of the API using Drupal's own and other APIs (such as Views), as possible.

The Translation template extractor provides a web based and a command line Gettext translation template extractor interface for Drupal as well as a reusable API to look for translatable strings and translatability errors. This tool is used under the hood at http://localize.drupal.org/ as well to serve as a parsing machine for Drupal.org project releases.

Note: I just transferred this project to dagmar. --Bdragon

A deceptively small plugin to return views data as JSON objects.

This module is meant for people doing heavy-duty JS work. Knowledge of JSON, jQuery, and a bit of Views internals is needed to fully utilize this module.

*HINT* I highly recommend using this in combination with the jQuery Forms plugin.

This module allows you to take snapshots of your site. It turns a Drupal installation into a sandbox that you can use to:

• Try out and test new modules, configuration, etc.
• Set up a public demonstration site for a contributed module or theme.
• Develop and test update and upgrade paths.

Whenever you need to reset your site to the state of a saved snapshot a click of your mouse will do so.

With cron enabled, a site can be automatically reset to a chosen snapshot in a definable interval.

Foreigner allows Drupal to maintain references to content items and users that are managed externally, and to treat these references like regular Drupal nodes/users.

The module supports a simple URI approach for identifying foreign items and users. Using a single delimiter that you configure, you may use identifiers of an arbitrary number of components to identify your items and users, in a hierarchical fashion. For instance, you might identify a content item as:

myworld:myapp:items:123

and a user as:

This module just provides a new form element, that can be used by other modules.

Only install it, if another module is instructing you to do so or if you are an interested developer.

This project has been renamed Transaction.