Extend and customize Drupal functionality with contributed modules. If a module doesn't quite do what you want it to do, if you find a bug or have a suggestion, then join forces and help the module maintainer. Or, share your own by starting a new module.
Shared Secret API provides a mechanism for verifying that a token was generated by a trusted partner using a simple shared secret method.
Generates and validates tokens based on a shared secret (that is, a secret string known by both the website with this module and whoever you trust). In many cases, the entity that you trust is the website with this module - or your site.
Most commonly, it will be used to verify that a link was generated by a trusted entity.
The only current built-in validation is via URL parameters. Given params "s" and "t" this module can verify that the generating party is privy of the shared secret.
Users must define how long each secret hash/timestamp combination is valid.
By default, the shared secret is the site's hash salt. If you are using this module with third parties or clients, you can opt to define a custom shared secret which is stored in the database. There is a plan and path to allow users to store the secret in a separate file outside of we docroot, but this has not yet been implemented.
Display webform results in charts intelligently.
Charts library planning:
Passwordless method of authentication for white-listed users.
Provides a method for owners of white-listed email accounts to authenticate and establish accounts without passwords.
Dependent on Shared Secret API module.
It provides a formatter for File Entities that uses the player from Dailymotion Cloud with the associated file, to stream from the cloud instead of your web server.
Restricted text format - allows core HTML nlock and inline elements. If applied to node content prevents local style attributes overriding the styles in the CSS.
Do you want to display a "HTML list" view as columns without using table or grid style?
This simple module will add the option (plugin style) "Number of columns" to have HTML lists rendered as columns grouped by the number of columns you entered.
It should work out of the box, but you need to create your own css to adjust the width, README.txt file will give you some important information.
Tables and grids views are not always the best way to have your data displayed as columns.
You will set the number of columns you want to display and "automatically" your rows will be grouped in columns.
This will be accomplished by setting an extra css class to the first and last row of each group.
All rows will have a float left property, and first row of each group will have a clear left property by default.
It pretty much imitate the HTML list style that comes with views by default.
There are other modules such as Views Column Class with more functionality than this one, check them out!
The ONKI service contains Finnish and international ontologies, vocabularies and thesauri needed to publishing your content with support for linked data. Ontologies are conceptual models identifying the concepts of a domain. They contain machine "understandable" descriptions of the relations between the concepts.
ONKI is published and currently maintained by Semantic Computing Research Group SeCo. The Finnish Government is also involved in the development and future proofing - press release in Swedish, Finnish and English (Google translate).
Onki Drupal module integrates Onki service with Drupal taxonomies. This way you can use Onki terms to describe (tag) desired content types.
Views Custom Style is targetted at themers. It allows you to limit the amount of custom template files for your Displays. It also adds more flexibility as all resulting rows and fields can be printed within one template file. Only 2 templates remain, the wrapper (views-view.tpl.php) and the custom style wrapper (views-view-custom.tpl.php). The default code of views-view-custom.tpl.php is as follows:
<?php foreach($rows as $index => $row): ?>
<?php foreach($row as $index => $field): ?>
<?php print $field . '<br />'; ?>
<?php endforeach; ?>
<?php print '<br />'; ?>
<?php endforeach; ?>
How to use this module
1 - enable it in admin/modules/list
2 - choose "Custom Style" in the format options of your View
3 - Use "Theming Information" to get template suggestions
For more information about Views, please visit the project page at http://drupal.org/project/views
Configuration UI for Leaflet.
This module adds additional acl entry for content. Other than the built-in view, update, delete ACLs comes with acl module, sometimes we want to have extra ones , ex. to allow download file node, etc.
The module currently allow acls to be set for any content node. For each node, either grant and block permission can be set to any user, or any user role type. Since this is a library similar as acl module, you can call functions to return permission status of any content node by permission type, and then implement the permission behavior in your custom module.
- grant user and deny user take precedence over grant user role and deny user role
- grant and deny are exclusive; i.e., a user or user role cannot be both granted and denied permission to access.
- grant user takes precedence over grant user role, deny user, and deny user role. For example, if a user is granted permission to access a file, this user may access the file even though s/he is denied due to his/her memberhip in a user role that is denied access
- deny user role takes precedence over grant user role; i.e., If a user is granted access by membership in role A, and is denied access by membership in role B, then the user is denied access.
Further improvement includes,
Extras for the party module
This is already accomplished by AGReservations but this module aims to be simpler and more flexible by accomplishing less. Essentially, this adds a "Payment status" field to your MERCI reservations and exposes an Add to Cart button to users looking at the MERCI reservation page.
Working off of the Commerce_Userpoints module I am developing a payment method based on userpoints that is not attached directly to a user, and allows users to have multiple point bases.
provides the payment method to drupal commerce
This is a module used for verifying age prior to site access. It's simply a yes/no answer to being over a certain age. You can set the age, destination URL, failure destination URL and a description in the settings.
If a site visitor is logged in, or trying to access /user, /admin or /age_verify they will not be affected by the modules redirect rules.
Please help by filing bugs, issues or feature requests.
The development of this module is being sponsored by SpireMedia
With this module, you can use menu translate which is created by Taxonomy menu form.
Shows latest tweets for any keyword, hashtag or, your handle along with sentiment analysis. It also starts to show trend lines if there is enough volume
Before you read on, please understand this is an API only module. In other words, it provides extra features for module developers. It does nothing by itself. If you're a module developer, read on.
Drupal's core Field API defines a hook for field access, hook_field_access, that is restrictive as all module developers are aware. In other words, given field F, if a single module implementing hook_field_access returns a Boolean false, thus denying access to the field, Drupal will deny access to the field even if there is another module that absolutely requires access to the field.
Normally, this is acceptable but sometimes a module might want to override the grants for a field denied access by another module. Or, a module might contain logic to grant access to a field but another completely independent module has denied access. Because of the restrictive nature of the field_access function, which internally invokes hook_field_access, access will be denied.
There are numerous scenarios that are similar in nature to hook_file_download_access and hook_file_download_access_alter. For a possible scenario, read on.
Proin augue libero, tristique at consectetur at, dapibus a metus. Nulla condimentum urna nec magna sagittis sed sagittis quam rhoncus? Aliquam erat volutpat. Class aptent taciti sociosqu ad litora torquent per conubia nostra, per inceptos himenaeos. Vivamus pretium libero ut velit dictum vitae convallis sapien venenatis. Donec bibendum ante vel ante aliquam ac dapibus nulla condimentum. Donec in neque vel sem feugiat faucibus ac a magna.
Mauris non leo suscipit est fringilla egestas quis quis erat. Integer dignissim, nisl sit amet venenatis blandit, turpis metus hendrerit nulla, in lacinia nibh orci eu nibh. Nulla facilisi. Pellentesque id ante vel dolor congue lobortis non non ante. Maecenas aliquet venenatis arcu id porta. Morbi at placerat orci. Mauris viverra risus eget leo congue cursus. Praesent lacus lacus, consequat quis lacinia sed, luctus et mi. Phasellus lobortis massa et nibh suscipit ut sagittis leo vehicula. Vivamus a odio nunc. Donec eu orci nunc. Suspendisse in est neque, ac sagittis orci. Curabitur eu sapien nisl, posuere vestibulum enim.
Mauris id congue risus. Sed nulla neque, dapibus ac feugiat sit amet, bibendum ac augue. Suspendisse purus libero, luctus ut amet.
Loyalty Management is a drupal module which basically involves user's points and rewards. This would be further enhanced with many features.
API for integration with the Ponoko making system.
Use Piazza through Drupal.
* Single sign on
* Automatically provision classes
Piazza is a free question and answer platform designed for university students and instructors. Learn more here: https://piazza.com
Email firstname.lastname@example.org with questions.
This is a D7 port of the webform_confirm_email module. It also includes a few fixes as well a little bit of inline documentation.