The Book Copy module allows users to copy complete books or subtrees of books.
When books are copied the user initiating the copy will be the node author of all book sub-pages. This will allow the user to adjust content to their purpose while keeping the initial content unedited.
This module requires that Replicate module be installed and enabled. It provides an elegant API for cloning items successfully and the 6.x book_copy api has been dropped in favor of this one.
Integrations / support
Drush - Copy books via the command line with Drush. Outline Designer - duplicate parts of book outlines using the outline designer UI, powered by Book Copy. Book Delete - accounts for Book Delete module if it is installed so the two can coexist.
The modules list page can become quite big when dealing with a fairly large site or even just a dev site meant for testing new and various modules being considered.
The Glossify module provides filters that scan and parse content and adhance terms in the text with tooltips and optionally add links to their pages. Currently it consists of 2 filters:
The latest version of the module now has full Unicode support for terms and content.
Glossify with taxonomy
links taxonomy terms appearing in content to their taxonomy term page.
select which taxonomy vocabularies to use as the source for the terms.
indicate whether or not matching is case sensitive.
indicate whether or not every match should be linked or just the first occurrence.
display the term definition as a tooltip while hovering the glossified link.
Glossify with content
links node titles of content appearing in other content to their node page.
select which content types to use as the source for the terms.
indicate whether or not matching is case sensitive.
indicate whether or not every match should be linked or just the first occurrence.
display the text from a selected field on the linked node as a tooltip while hovering the glossified link.
This module allows you to write modules in pure OOP syntax. It becomes handy when you need some kind of "aspects" to inweave into the main functionality of your module. Moopapi does it by Decorator pattern. Currently we have these types of decorators implemented:
- Logger: allows to log every method calling together with all parameters passed. A mighty tool for development and debugging in some circumstances.
Used by: BOTCHA (spam protection without CAPTCHA) - its use case is that while developing Selenium-tests for its JavaScript there is no chance to use usual development tools such as XDebug, because Selenium-tests are intended to be launched via command-line interface. Moopapi logger helps BOTCHA to keep debugged.
- Cacher(planned, see #1870060: Create new decorator: Cacher): The idea is to separate a logic of an application and tricks to make it work faster. It could be done by Cacher "aspect" which includes all speed optimizations while your application contains pure business logic.
- Adapter: Abstraction layer for Drupal major version. The concept is thoroughly described here: #1932290: Forwardport doctrine - a proposed solution for Drupal major version migration problem. See 4.x branches of BOTCHA project (D6 & D7) together with common part x.x-1.x as an implementation of such audacious approach.
Most PDF modules generate PDFs from scratch; FillPDF is not one of those modules. Instead, it lets you fill in existing editable PDFs with data from your Drupal site. Editable PDFs are those forms that let you type into them.