Open Media Broadcast Schedule

Open Media Broadcast Schedule provides Drupal-side schedule integration for broadcast playback servers. It creates an airing content type, via features, that stores the current schedule. This module also provides bulk schedule update functionality that is used by OM Timeslot Scheduler as of the 7.x release.

This module is dependent on the 7.x branch of OM Playback Servers.

libcat_collection

A new collection entity meant to be used with Relation module.

View Mode Page

Create separate pages for different view modes for a given content type.

On the manage display page for a given content type, you can assign patterns for view modes so that they will become a page at the given path. For instance, if you want to show the teaser at a specific URL, you could do node/%/teaser. If you also use Display Suite or other modules that allow you to create new view modes, you can use these modes to display one or more fields from a node at a separate URL.

This module also includes basic Features module integration. This allows you to selectively export your settings in a feature.

Restrictions: currently, the node path must be contained in the URL. This means view mode pages must follow the form [node path/node alias]/[view mode url]. These pages are added via hook_menu. Multiple wildcard characters can be used.

How to add a view mode page

  1. Create a content type
  2. Configure a view mode. If you are using Display Suite, or another means of adding view modes, you may need to add a new one.
  3. Go to the "manage display" tab for your content type.
  4. In the "View mode pages" tab, enter your URL pattern for the view mode page.

Devel extended logging

If you're a "tail -f" kind of debugger, you may find this module useful. It adds a number of functions that write to the debug log file:

- ddi(): Indents debug messages based on the depth of the call stack
- dds(): Logs just the attribute/key names of an object/array.
- ddb(): Logs just the function names from the debug_backtrace() function call stack
- ddf(): Logs the name of the current function, indented with ddi()
- ddu(): Logs a message and moves cursor one line up
- ddt(): Writes debug messages with code execution timestamps included

GMap3 Tools

Summary

A collection of developer tools for quick Google map creation from Drupal code. Uses Google map API version 3.

This is utility module - you need this module only if some other module requires it.

Main goal of this module is to offer developers very light and easy PHP implementation of Google Map API version 3 for Drupal.

News

  • 2013-Apr-13 - new features: map geolocation, relative marker coordinates and draggable markers with dragging event that updates custom lat/lng value input form fields.

How to use it

Check example page (you need to enable module to load examples) for couple of short examples

http://your-site/gmap3_tools/example

. Note that you do not need to enable module to use it API calls, you just need to include gmap3_tools.inc file in your code.

Basically you need to do 3 things to get working gmap:

  1. Load gmap3_tools.inc file
    module_load_include('inc', 'gmap3_tools');
  2. Call gmap3_tools_add_map() function from API file with appropriate map configuration array
    <?php
    // Map example with some custom options and 2 markers.
    gmap3_tools_add_map(array(
    'mapId' => 'gmap-canvas',
    'mapOptions' => array(
    'zoom' => 8,
    ),
    'markers' => array(

HTML Extract

This module takes the content from the specified tag - HTML structure with the id or class and stores it temporarily into Database from which it can be reused on the page. Every time the content is changed in the Database, a notification can be send and also interval of actualization can be adjusted.

The entity contains basic page data and settings around it also as an array of multiple div chunks - children from the specified structure. With help of the Views integration the content can be accessed.

Pages

Subscribe with RSS Subscribe to RSS - Under active development