Developer tools

Overview

This project builds content objects from drupal and bundles them into an
EPUB 3.0 document. Currently it will export a rendered entity seperate of all
of the page markup and gather all the referenced resources within the content
and bundle those into one EPUB document.

That is, this module looks at the content and determines what should be included
in the EPUB document. The actual build process takes place during cron, make
sure to run cron as a user that has access to the content necessary otherwise
the build will fail.

Installation & Libraries

Modules

This project requires: entity, field and libraries API (2.x)

Libraries

This project requires the FunnyMonkey-EPUB-Package library which can be found
on github;

https://github.com/FunnyMonkey/FunnyMonkey-EPUB-Package

This should be extracted to your libraries directory with the name 'FunnyMonkey-EPUB-Package'.

Apache

To ensure proper handling by all browsers you may need to add the following to
your apache config. (httpd.conf, mime.conf, .htaccess, etc.). Otherwise
browsers may try to render the binary content rather than downloading and/or
displaying via an external application.

  AddType application/epub+zip .epub

Configuration

Add the EPUB field to any node content type. Then after editing a node of the

Summary

Use this module if you need to cherrypick on an entity type or individual entity level what fields should be output in what order in a Drupal service call. The Field Resource module uses tokens and the content edit interface so you don't need to be a developer to fine tune the content returned in a service call.

Description

The Field Resource Module is a plugin for the Services module. The module provides a new field type that you can add to any entities whose content you want to use as a resource in a Drupal service. In the field you can use a combination of text and tokens to finetune the output you will get for a service call for that entity.

The field widget has two parts:

• Text area where you define the service output:
  On an entity type level you can define a default for the service output for all the entities of a given type. You could for example concatenate the output for all the fields in reverse order e.g.
  "[field_C]; [field_B]; [field_A]"
  On individual entity pages you can change the content of the field to overwrite these default settings.
• a machine name form element for the unique resource id:
  By default this field will be derived from the title of the node, but it is again possible to overwrite this default setting. This unique id is needed for the service call.

A small module to add the server name (as in machine hostname, not the name of the website host) to administrator reports:

3th party widgets can cause a huge performance hit.

Integrates Tika (docs) to extract textual information from uploaded

A feature module providing content types and services to allow the fetcher drush extension to retrieve lists of sites that can