Content editing experience

This module simply provides a formatter for image fields that prints the image encoded with base64.

This module is useful to attach a text based agreement as a form to nodes that require an agreement to be signed by each user. Examples of agreements include Content Acceptance Agreements, Non-Disclosure Agreements, End-User License Agreements, etc.

Agreements can be attached to Nodes of any type, and each node can have its own specific agreement for a specific year e.g. Node can have two different agreements for two different years, once the current year exceeds the agreement year that agreement will be replaced with the agreement of next year.

All data related to user signing an agreement are stored per agreement and these reports can be viewed for a certain no. of years (this feature will be implemented in next release). The reports are of two types listing users who have signed the agreement and users who have pending signature.

Further a dialog functionality from JQuery has been implemented to send popup to all users if the signing of agreement is pending. To achieve this a small piece of code has to be added at the end of page.tpl.php file of your theme (we are considering it to move this code to module level in next release)


<?php
if (module_exists('signed_nodes') && $user->uid >0) {
global $user;
$snode = array();
$popup = FALSE;

A text format filter that floats images automatically, alternating left and right. A time-saver when inserting images in the text.

It adds an odd/even class and uses CSS to float. No more inline styling is needed.

This module is an attempt to integration Drupal and Google Calendar.

Project plan:

SVG graphics are really powerful but not yet widely supported.

This module allows you to put any relative path you'd like for a menu entry, even if the path doesn't exist on your site.

You might need this module for two reasons.

1) You either need to create menu items before the pages/paths are created. Helpful when you are building out new sites for which you haven't actually created the secondary pages yet, or if you want your menu to point to some path that will actually be redirected somewhere else (for which you've already set up a redirect).

This actually isn't why this module was created, but it will work for this.

2) You have a distributed system, with some paths being on one (non-Drupal, or different Drupal install) server, and the other on your current Drupal system. It's assumed that you have some sort of path redirection mechanism in place such as Varnish, nginx or The Big IP to redirect your request to the proper path. But you need to serve your menu from Drupal.

Why not just put an absolute path, you ask? When you put absolute paths, not only does it make it a pain for moving your Drupal site to other environments - but it also doesn't keep the proper base url when your site is serving up translated content. Ideally, http://example.com/your_sneaky_path would change to http://example.co.uk/your_sneaky_path when you changed to UK English (as an example).