Skip to Content

New Drupal Modules

Syndicate content
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.
Updated: 26 weeks 2 days ago

Dynamic Nodes

16 October 2013 - 7:30am

This is a sandbox project.
with dynamic nodes, the author should be able to attach exisiting fields to content by himself. The author can drag and drop the display order of the attached fields, meaning that at the full view mode the fields are being rendered in the order the author has defined. Basic fields which are always to be filled up (like the classic nodes) can be defined by the admin.
This is just an idea. Suggestions / discussions are welcome.

Categories: Drupal

Serialized field

16 October 2013 - 7:27am

This is a helper module which declares a 'Serialized data' field type. This is designed to make it easy for modules to store arbitrary data on an entity.

No widgets or formatters are included for this field type - the assumption is that its value is usually updated programatically.

Categories: Drupal

SIF for Drupal

16 October 2013 - 7:20am

This module suite allows interaction between a SIF 3.0 server and a Drupal site. SIF stands for Schools Interoperability Framework. For more information read http://en.wikipedia.org/wiki/Schools_Interoperability_Framework

This module can work with the the SIF REST Sandbox (a.k.a. SIF-RS) located at http://rest3api.sifassociation.org/jsp/index.jsp

See https://www.sifassociation.org for more information.

This module is in development. More info coming soon.

Requirements

Entity API

Architecture

This suite of Drupal modules is provided as a framework for Drupal sites to build their own integrations with SIF Service Providers. It does not make any assumptions as to how you wish to build your application, it simply provides the tools needed to do so.

SIF Data Objects

sif_data_object.module
"SIF Data Object" is a provided as an Entity Type. Each Data Object Type is defined as a Drupal entity bundle. The sif_data_object.module defines the entities and the bundles for all SIF Data Objects that are supported by the SIF-RS: Environments, Zones, Queues, Subscriptions, Alerts, and Students.

Other SIF data objects may be defined by implementing

<?php
function hook_sif_data_object_types(){ }
?>.

The SIF Data Objects are stored as ID/Raw XML pairs. Each SIF Data Object Type obviously has its own properties, but as a baseline, this module just stores the raw object data. The Entity API may be used to extend these entities to fit specific use cases.

SIF Callback

Coming Soon

Will provide a REST endpoint for SIF to callback to.

SIF Rules

Coming Soon

Will provide Rules.module integration allowing complex interactions to happen on SIF message receipt or Drupal entity modification.

Categories: Drupal

Simple Objects

16 October 2013 - 6:19am

This is a sandbox project.
The idea of Simple Objects is to provide a unified way to handle simple business objects in Drupal you also also like to store in database.
Simple objects are objects which are not worth to be handled as entities but are needed for referencing informations. Every simple object can have its own data structure. To store a simple object it should be attached with an identifier. This API provides CRUD for your simple objects, like simple_object_load($id) and simple_object_save($object, $id). Furthermore, you can serialize your object for exporting with simple_object_serialize($object).

You may find this API useful if you

* Have a class / anonymous object where are only about 1 or 5 total objects of it.
* Your object doesn't need any access control, menu items, view modes, you just need the object itself
* You don't want to use variable_get() and variable_set() to store your objects, because you don't want to have them stored in the variable table besides configuration variables and be accessible through the global $conf variable.
* You'd like to get a unique id for your object and load/store it by this id, and to use this id for references.

This is the basic idea. More suggestions or discussions are welcome.

Categories: Drupal

HTTPRL Spider

16 October 2013 - 6:14am

HTTPRL Spider uses the excellent HTTP Parallel Request & Threading Library to perform an internal cache seeding spider via Drush. This is not a module, it's a command line call that can be used to effectively rebuild all Entity Cache and Boost cache files for an entire site. By default it will spider all known, front-facing entities in a site with a single call. It also has some hooks to allow for adding additional non entity paths to target (such as views and other menu paths).

Installation

Just run drush dl httprl_spider to get the latest version; it's a drush plugin.

Simplest example

drush cc all
drush hss --nonblocking
This will clear all caches and then issue nonblocking requests for all front-facing entity paths. This has performance implications so make sure that you run this as part of a nightly job and not all the time (especially on larger sites) as this is effectively a self-imposed denial of service attack. A bit safer call is drush hss which issues the calls but sequentially and yet more reasonable is drush hss node to have it only spider nodes on the site. Another common call

Say you want to request just a single path as to rebuild the cached version of it (like the front page or another critical page). drush hsr node would issue a call against the path "/node" and rebuild it in this example.

History

This project draws on concepts originally pioneered by Drush Entity Cache Loader with the main difference being that while it seems entity cache tables it then makes a http request for the url to the object it just cached. This causes not only the entity cache to be populated but css/js aggregated files, boost static html copies, menu and any other cache system to be populated. This is effectively the same thing as an anonymous user going to the page except they won't have to take the performance hit to be delivered the content.

This project is a spin off of #2087955: Add Drush support for command line HTTPRL calls which provides the same functionality but will be managed in this place as agreed upon by the maintainer.

ELMS

This project has been created as part of the ELMS initiative at Pennsylvania State University.

Categories: Drupal

Locale Hide

16 October 2013 - 5:37am

Description:
This module allows you to manipulate the links that are shown in the language switcher block (as provided by the Locale module) and hide specified locales from the switcher block.

Use case:
You want to activate a new language on your website, but not advertise it yet (e.g. you are still finishing up the translations). If you would leave the new language totally disabled, you wouldn't be able to see the translated content in the proper interface.

Warning: This module just obfuscates the hidden languages.
Anyone who knows or finds the URL or language prefix, can still browse that part of the site. So it should only be used for temporary workarounds. To have proper language access control, there are probably better modules out there.

Installation:

  • Enable the module
  • Go to admin/config/regional/language/locale_hide
  • Select the languages you wish to hide from the language switcher block
Categories: Drupal

Total Subscription

16 October 2013 - 5:31am

This is for the subscription of node and its related taxonomy terms for both: anonymous and logged-in user also.

Categories: Drupal

mailredirect7

16 October 2013 - 4:42am

With this module drupal redirects mails.
In the admin interface the authenticated user can choose which modules, who implements hook_mail, will be redirected. Also the emailaddress where to the mails will be redirected can be set. Also can a subject prefix be set.

Categories: Drupal

BannerX

16 October 2013 - 2:48am

asdf

Categories: Drupal

Opigno Video App

16 October 2013 - 2:29am

This module uses the Video module and integrates it with the Opigno module. Creates Video content type, a view and sets default permissions if using the Opigno distribution. Og module is required and the content type is set as an Organic Group content.

Categories: Drupal

Field collection plus

16 October 2013 - 1:46am

Provides additional settings for field collection fields. You can now set the path and the label for field collection entities in the field settings form. The label supports tokens.

Categories: Drupal

Views User Login Link

15 October 2013 - 9:19pm

This module provides a Views plugin to display a one-time-login URL or link for a user in the context of a View.

Together with Views Data Export, this module can help a site owner to export and mail out welcome messages to the user base of a new/migrated Drupal web site.

Categories: Drupal

Hosting Auto Git Pull

15 October 2013 - 6:45pm

This module extends Aegir and Hosting site Git by automatically creating a pull task based on a post hook.

Categories: Drupal

Node View Mode Field

15 October 2013 - 6:12pm

Provides a field that can be used to select a view mode on each node.

Categories: Drupal

modbootcamp sample module

15 October 2013 - 3:51pm

This is a sample module for modbootcamp

Categories: Drupal

Profile2 Complete Percent

15 October 2013 - 1:45pm

calculates percentage for all profile2 types in one single block.

Dependencies:
https://drupal.org/project/pcp

Categories: Drupal

Taskit

15 October 2013 - 1:43pm

Taskit ("Task It") is a Notifications-style framework API meant to assign actionable tasks to users & roles.

Placeholder project page until code is ready to be released.

Categories: Drupal

grande.js

27 September 2013 - 8:35pm

This module is a simple field widget that bridges grande.js with Drupal. Grande.js is a simple WYSIWYG editor that provides content creating/editing experience similar that of Medium.

Categories: Drupal

Views Usage Audit

27 September 2013 - 3:02pm

This module can help you refactor a Drupal codebase by locating redundant views and displays or simply improving your understanding of what views are used where.

It achieves this by logging where views get executed. You can then run reports from drush or through the UI (admin/reports/views-usage-audit-reports) that tell you what menu paths individual displays got execute on or simply provide you with a list of displays were never executed.

It is designed to be highly performant and safe to be run on production but can also be used in development environments provided you exercise all parts of your site.

Categories: Drupal

Commerce Lot

27 September 2013 - 1:52pm

About this Module

Using Commerce Lot, you can create flexible solutions for when you need to sell multiple products together.

Module Dependencies

* Commerce
* Relation
* Relation Add

Commerce Contrib Support

Currently, this module has not been tested to work with any other module outside of its dependencies. See ROADMAP in README.txt.

Alternatives

This module is a Relation module based alternative to
* Commerce Product Add-On, and
* Commerce Product Bundle

What Does Commerce Lot Do?

When you create a Commerce Lot enabled product and add other products to the lot, a relation is automatically generated between the two entities. Since Relation module stores relations as entities, we can add extra fields to affect how each product in the lot is processed by Commerce, e.g., products can be optional upsells or required purchases if a customer buys a Commerce Lot product. In the future, the module will include features for price calculation, combining items to a single line item, and more.

For example, say you have an mp3 store and want to sell a compilation of individual songs (a Commerce Lot) which already exist as product entities your store, and also give customers an option in the album's Add To Cart form to buy a t-shirt at a reduced price if they purchase the album. (This example isn't possible yet with Commerce Lot, but this is one of the goals of the module.)

Differences between other modules

The main difference between this and Commerce Product Lot/Commerce PADO is that it relies on Relation module entities to define relationships between products rather than using a simple product reference or entity reference. Since we can have extra fields on relation entities, we can use these to extend how Commerce processes ordering multiple products together. This saves us from having to add unnecessary fields to product entities.

Note: Since the module must check for Relation entities, this adds overhead to the Drupal engine. If you do not need the kind of extra features enabled by Relation entities, the above-mentioned modules may fit your needs better. Commerce Product Bundle is a mature project and already contains many features planned for this module.

Status

Last updated: 08/27/2013

This module is being worked on regularly. Currently, the module can create Commerce Lots on a product type, and require products in the lot to be added to the cart from the Lot's add to cart form. Next update will address what happens when "required" Lot products are removed from the cart.

For planned bugfixes/features, see ROADMAP in README.txt

Feedback, suggestions, and bug reports are extremely welcome!

Note from the Author

This is my first Drupal module ever! \(^_^)/

Categories: Drupal


about seo