Actively maintained

phpBB Single Sign-On allows you to log into your phpBB site automatically after logging into Drupal.

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.

Vegas of the awesome Jay Salvat from the Coders in Black community, is one of the most used jQuery plugins to add beautiful fullscreen background images with slideshow-like transitions to your webpages, respecting the viewport and the image ratio with maths to keep up the fullsize effect without skewing and with supporting fades, overlays and many more. The vegas (Vegas Background jQuery Plugin) Drupal contrib module enables the user to use the jQuery plugin for their Drupal project via admin UI.

Re-working of the phone & cck phone modules to be combined and use libphonenumber. See #1812184: [meta] Rewrite and merge phone and cck_phone for history.

This version of the phone module has the following features:

• Provides a Phone field type, Phone field widget, and several formatters.
• Provides a Phone FAPI element which can be used in custom modules.
• Backports the "tel" input element from D8 as "phone_tel", and allows this to be used for number input elements.
• One field instance can support every country.
• Limit allowable countries.
• Includes customisable comment/label support (Work, Home, Fax, etc..).
• Full region level validation for all phone numbers using libphonenumber. This supports most if not all known countries, and works for both the Phone field widget, and Phone FAPI element.
• Region specific output formatting using libphonenumber, supporting International, National, E.164, and RFC3966 output styles.
• tel: href support using RFC3966.
• Full token support.
• Feeds & Migrate integration.
• Microdata (itemprop=telephone), RDFa (foaf:phone), and microformats hcard (class="tel/type/value") support. Full type support can be enabled by customising the available comment options.
• Devel Generate support. Handy, if you need an Acquia sales office phone number.

Import Gmail contact list using oauth 2.0 and Google contacts data API.