Once defined a user role and grouping the users in this role, the module will intercept user login and check if the user account belongs this group. If so, the reset password e-mail is sent and a warning message is showed.
This verification is done only by username or e-mail, the password will be disconsidered in this flow.
Provides a XML abstraction layer for Drupal Form API arrays.
With this module, you can create and edit XML forms from admin interface (it creates a new block type). It is also possible to use the module as a helper to integrate with some external XML form generators.
XML form also integrates with Codemirror to make easier for editing the XML estruture.
This module allows to use single SOLR core from multiple sites independently.
Useful for Acquia Cloud sites and other hosting providers with single SOLR core available.
Please check readme.txt to setup.
A 2-factor admin authentication method via jabber
It requires http://code.google.com/p/xmpphp/ as library
I did a video in spanish explaining it www.youtube.com/embed/OEECgKVc8fI
This is an commerce payment Integration with PaytoStudy service.
This module ads chronological three level sitemap for nodes. All created nodes links will be in ordered list. We can found it using path yoursite.com/static/sitemap/%year/%month. This sitemap is for SEO purposes. There are some settings at this page http://yoursite.com/admin/config/search/chronological-sitemap.
1) This module support custom caching scheme;
2) User can change path to see the sitemap and change date from which nodes will be added.
Commerce Live Stock manages stock fields in realtime with Node JS and Rules.
CLS displays the quantity of product still in stock in realtime.
CLS extends the module Commerce Stock.
This module just might be a single replacement for all these modules:
Provides a sequential id column for entity types.
Body Field Definition is a very simple utility features module. It provides a field base definition for a body field, which can then be used by one or more content types and allows the user to avoid any confusion over which content type should have the field base for the body field. This is particularly relevant for any site or group of sites being built with multiple features based content types to avoid any conflicts with each content type trying to declare it's own field base for the body field.
