Integrations

The original purpose of this module became obsolete. Use the FillPDF 1.x series instead.

This is an API module. Only install it if another module tells you to or if you are a developer and want to use its functions.

The goal of this module is to take the pain out of some aspects of dealing with PDFs so that module authors can focus on their specific applications.

The initial goal of this module is to provide parsing and merging (filling) support for Certify and FillPDF.

Having a unified module will also make it easier to support new PDF-related functions and to fix bugs related to the current ones in one place.

Working with PDFs can also be a bit annoying, and implementing modules can avoid dealing with that annoyance alone. Ideally, all maintainers of implementing modules will be co-maintainers on this one, at least where it makes sense.

The following parse and fill methods will be supported:

• pdftk (from Certify and FillPDF)
• Custom JavaBridge servlet (from FillPDF)
• Fill PDF Service (from FillPDF)

The following additional methods are under consideration:

• pdfformfiller2 #1860474: Investigate integrating PDFFormFillerUTF-8
• Pseudo-filling (via PDF generation) such as the idea in #1593928-6: Support other PDF generation methods

This module informs the visitors of your site with the currency exchange rates.

This module provides a formatter for the entity reference field that displays MailChimp sign-up forms.

Add integration and settings for Add To Home Screen in the form of a module.

Webform GA Tokens provides Google Analytics related tokens for use in Webform results. In Drupal 6, webform.module defines its own tokens, so tokens added via token.module are not available.

A little Features-based module that kludges the Date project's Date Repeat field to schedule email notifications on a per-user basis. Developers can implement one or more of this module's hooks to specify what is sent. See the included pester_watchdog.module for an example.

Basic usage:

We assume all views take a user ID as their first argument, or accept no arguments. Arrays returned from hook implementations are keyed by user permission; If a user hasn't been granted that permission they won't be sent the output of the corresponding view.

/**
 * Implements hook_pester_views().
 */
function mymodule_pester_views() {
  return array(
    'access content' =>  array(
      array(
        'view' => 'myview',
        'display' => 'block', // Defaults to 'default', rather sensibly.
        'weight' => 0, // To order output of multiple views.
      ),
    ),
  );
}

This module is intended to be as lightweight as possible (i.e. I'm lazy). If you want to do anything fancy with the output, you'll have to implement one or more Views hooks, eg.:

<?php
/**
* Implements hook_views_pre_build().
*/
function mymodule_views_pre_build(&$view) {
if ($view->name == 'myview' && $view->current_display == 'block' && ($user = user_load($view->args[0]))) {