Developer tools

A simple utility module which enables the use of "first logins".

This provides a user interface to a bitcoin daemons running on local or remote servers.

Provides an API to interact with Dreamhost via their Web Panel

Summary

This module provides an easy way to retrieve data in JSON format through a menu callback. Compared to Services this module focuses on JSON and doesn't need configuring of resources, endpoint or authentication.

It's low level and most easily used with AJAX to get data of the following content types:

• node
• menu
• comment
• taxonomy_term
• taxonomy_vocabulary
• custom_data

Each of these options provides a hook to alter the data-output, look at phpDocs for implementation examples. If no hook is provided, the default object will be returned (can be huge!)

A node hook example can look like this:

/**
 * Implementation of contentasjson_get_node() hook
 * @see _contentasjson_get_node();
 */
function mymodule_contentasjson_get_node($node) {
  $node_array = array();
  $node_array['id'] = $node->nid;
  $node_array['title'] = $node->title;
  
  return $node_array;
}

AJAX Example

To retrieve data with the contentasjson module you can use AJAX. The following example shows how to get the data with jQuery:

jQuery.ajax({
  type: "POST",
  url: "contentasjson/node/1",
  success: function(data)
  {
    console.log(data);
  }
});

Always fill in all values within the -url- parameter. There are 3:

Wysiwyg plugin to easily insert YouTube and Vimeo video's into content.

Purpose

This module adds a couple of admin reports to review the most common 404 errors on your site.

When a redirect module is available, these reports include the option of adding or updating a redirect for paths that have resulted in 404 errors in the past (thanks to benclark). For D6, this uses Path Redirect. For D7, this module was moved to Redirect.

Why?

By default, Drupal handles all requests coming into your website for files that don't exist on the disk. This means that Drupal runs every time someone tries to visit a page that doesn't exist, in order to show your custom 404 page.

More importantly, this also means that Drupal runs every time some other page or email tries to include a missing image, CSS, or other file from your site. And since it misses any caching you might be using, it can result in a high server load on popular sites. This tends to be a problem when moving an existing site into Drupal: it's not uncommon to overlook some directory of images that need to be migrated over because (for example) the existing mailing list templates use them.