Content display

The BeautyTips Form Errors is a simple integration with popular BeautyTips module, that provides you "Tooltip-like" form error mess

We all need a privacy policy on our sites, but on the list of things we want to tackle, it ranks near the bottom.

Our clients don't know what to put in there, either. As developers, we create a Privacy Policy page node and then tell the client to go figure out privacy themselves.

Services are starting to require mention in privacy policies as part of their terms of service.

Users, when they bother to read it at all, have to read and understand a new policy for every site they use.

Wouldn't it be nice if there were a better way to set up and manage a privacy policy? Wouldn't it be nice if there were some default policy snippets we could string together to form our policy? We didn't invent cookies, and 99% of the time we're not doing anything new or interesting with analytics or comments or anti-spam services, but their use should be disclosed.

Meet the Privacy Policy module.

This module creates a default page with a list of privacy policy bullet points that are grouped in sections like "General" or "Analytics" or "Marketing." In addition to the policy text, each item can include a icon and a name. Other modules can add items to the list via hook_privacy_policy.

This module extends the Wysiwyg module and provides a new button for adding source code to be highlighted with the

Integration with Views Slideshow and FlexSlider

INTRODUCTION
-----------------

Current Maintainer: Scot Hubbard - http://drupal.org/user/868214

This module allows content creators/maintainers to add maps to content via the TinyMCE & CKEditor WYSIWYG editors (it has been tested against these two editors, it may also work with others).

A WYSIWYG toolbar button can be enabled under the WYSIWYG profiles setup to allow the user to open a dialog that will enabled them to find a point on a map, set the width, height and zoom factor and map type, and insert a token directly into the filtered content. The map will then display
when the content is viewed normally.

It is also necessary to enable to filter under Text Formats (this will convert the token into the corresponding map when the content is veiwed normally). Make sure the WYSIWYG Map Filter is one of the last to run.

INSTALLATION
----------------

Install as usual...
see http://drupal.org/documentation/install/modules-themes/modules-7

CONFIGURATION
-------------------

There are no specific config options for this module other than enabling the filter and the WYSIWYG button as described above.

NOTES
-------

As an attempt to provide a solution to:

How do I format a multi value field as a grid?

the Grid Field Formatter module provides a simple way to overridde the display of multi-value fields to show as a grid/table with a certain number of columns.

This module has no pretention of implementing any field: it is not a Table field, such as TableField, or CCK Table Field.
It's just a formatter (display) to render multi-value fields with a grid/table layout instead of a list of items.

The idea behind this is to provide a simple solution, easy to use, setup, with few dependencies and trying to leverage the formatter hooks provided by #945524: Field formatter settings hooks in core to extend existing field formatters.

Implementation:

The code is very similar to other modules built on top of Field formatter settings, such as Linked field or Field formatter class, and it implements hook_field_formatter_settings_form_alter to add configuration options to existing formatter settings forms.