Developer tools

Handle duplicate entities well! Scan for duplicate entities, and merge them. Includes integration with Relations and Rules.

Integrates with the facebook API based upon the flux Services integration.

Integrates with the twitter API based upon the flux Services integration.

Extensions is an alternative method of pluggable object creation (ala Chaos Tools plugins).

The key features of Extensions are:

• Extensions are always namespaced objects
• Extensions always extend the base Extension class
• Unlike Chaos Tools, extensions can be declared dynamically, and at run-time
• It is not necessary to load the Extension file to get information about it
• Extensions use factory classes for creation
• Extensions are organised into Collections, which are nominally a set of plugins with similar behaviour, but dont have to be

Basic usage

Extensions are a type of reusable class, so there are two ways you might commonly want to use them. Firstly, in accessing an Extension Collection to use the objects in it, and secondly to declare new extensions (it's not necessary to ever declare a collection, these are created dynamically).

Accessing a collection

<?php
// Get a full collection containing fully loaded extensions, as an array.
// This will return only extensions already declared.
$extensions = extensions_get_extensions($collection_name);

// Get only the settings for the collection, without creating objects, as an array.
// Again, this will only return extensions already declared.

Simple Client is a developer tool for making simple HTTP GET and POST requests using Guzzle.

This is a simple HTTP client module, used primarily for fetching content from the internet.

If you are looking for additional normalisation, validation, URL parsing and construction functionality, you may like to use Link API in conjunction with this module.

Dependencies

Simple Client requires Guzzle to be present and autoloadable, which needs to be done via Composer. Two workable options for this are setting it up via Composer Vendor, or Composer Manager.

Why wrap Guzzle

Guzzle is a perfectly adept HTTP client, so why wrap it in another module? This is reasonably straightforward. Over several projects, I found that I needed to repeat the same wrapping code around Guzzle. Some of it is just request construction, but there is also error handling and other parts. The result is a "simple" client. Its not as powerful as a full Guzzle client implementaiotn, but its not as complicated to use either.

Usage

Overview

Display the host and database name of the default database on the status report, toolbar (Drupal 7) and/or on the admin_menu bar if enabled (either Drupal 6 or 7) and/or in a block (to use with the admin module).