Under active development

Ubercart Payment Gateway for Sage Payment Solutions.

Drupal 8

Waarom alle bekendmakingen in het huis-aan-huis krantje doorspitten als je alleen maar wil weten of de buurvrouw die mooie boom in de straat mag kappen?

This module is a bridge to Planyo online reservation system.

PBCore is a metadata standard for audiovisual media maintained by the Corporation for Public Broadcasting. It provides a rich set of descriptors for radio and television programs, in both analog and digital formats. This module adds Language, Rating, and Genre vocabularies, populates the terms, and defines fields that can be used on any content type.

"Beardcast" #2: Adding Customized PBCore Field to Community Media Show w/ a REALLY Long Goatee

This project contains 2 modules:

• PBCore - Defines genre, rating, and language as Taxonomies and populates them with the official PBCore values. Defines a field for each Vocabulary. Includes a base PBCore XML template.
• PBCore Custom Names - Allows the enabling/disabling and altering the names of terms in the UI. A common use is to limit the languages so that users don't see options like English - Middle Ages... unless of course you are cataloging the library of a Tolken fan. In that case, you might change English - Middle Ages to appear as Lord of the Ringlish. A more practical example of using a customized name is changing gay/lesbian to GLBTQ.

Sudo module allows administrators to use the site primarily as a normal user but add permissions to their account as needed for the performance of administrative tasks. Unlike the many excellent user-switching modules often bent to this use (masquerade, impersonate user, devel's switch user), Sudo toggles a configurable set of permissions on the current user's account. This is useful not only for testing a site but also on production sites, in cases when it is desirable for administrators to use the site both as a normal user and as an administrator and yet all activity must come from the same account.

Caveats

Sudo functions by removing and adding user roles on the fly. Any functionality
that relies upon user roles will be affected if those roles are sudo roles for
any users; for example, an action that sends emails to all users with the
"administrator" role will fail if the administrator role is a sudo role for some
accounts that are not sudoing when the action is triggered. To get around this,
you may wish to add a role with no permissions for administrators, and key tasks
that would normally target the "administrator" role to that role instead.