dezinedepot

This is a simple module to let users store their location on the edit account page. It uses HTML5’s geolocation API and stores latitude and longitude. How you use that data is up to other modules.

It will be used on Drupal.org

This is a Views summary style plugin. It allows you to embed the results of a View with each argument in the argument summary. You may use a different display; for example, you might build an archive View with a Year+Month argument, that lists the four most popular nodes for each month in the summary, but that lists nodes in date order when you click through to the argument.

Usage:

• Set the "argument summary" style -- to "Peek Summary"
• Configure the style -- choose a display plugin, set paging
• Example peek_summary output
• The same View, with an argument (not peek_summary output)

Caveats:

• You should limit the number of arguments displayed per page (in the argument summary). A View is executed for each argument that is rendered.
• You should use Views' caching, at least for the display you use for peek_summary.
• The peek_summary display must have the same arguments as the argument summary display--they may or may not be the same actual display.

You can see a new Drupal success story here at AIT Profiles:

http://aitprofiles.wordpress.com/2010/09/01/north-wind/

It's hard sometimes to find certain module if you're using a bunch of modules. This module helps you to find the module faster.

This module is an in-line editor used to edit the body field of specific content types and blocks using Mozilla's Mozile editor.

In essence, this editor should work on all browsers, but it's best used with Mozilla Firefox.

Please consider donating to further the development of this module.

Maintainer: Waleed Qadi from O-Minds.

O-Minds can be contacted for Drupal services via the contact form on our website.

This module provides Moodle SCORM (http://www.moodle.org) integration for Drupal using CCK functionality. It depends on the CCK and the FileField module. This first version focuses on displaying SCORM contents and logging events for each user. Analysis of all logged events will be part of a later release. The module enables the user to upload a SCORM compatible Zip file during node creation process. The user can decide if the SCORM content should be opened in a new window or if it should be embedded (width and height parameters are available).

The module is developed during the project “E-Learning 2.0 in craftsmanship trainings” funded by the Federal Ministry for Education and Research (http://www.bmbf.de/) and the European Social Fund (http://www.esf.de/). Project maintainer is the German Center for Aerospace (http://www.dlr.de/). The module is developed by Servit Open Source Solutions (www.servit.ch) and is adjusted by the project team (http://q-online.de/kontakt). The module is a part of the community portal which is currently in development.
Further documentation will be published soon.

Module maintainers are:

• University of Duisburg-Essen – Chair of educational media (http://www.mediendidaktik.de)
• Servit Open Source Solutions (www.servit.ch)

I get fed up with scrolling down the modules admin page looking for the right module to enable/disable. This module injects a tiny javascript into the page head that adds a drop down to local menus. This then allows a quick jump to sections in the page.

read more

Provides a shortcode API and basic shortcodes through Drupal filters.

Initial works based on the Wordpress Shortcode API but I rewrote it for Drupal and solved the nested tag problem. Now you can nest tags (same tags too) no need special recursion handling.

All tags are themeable and new tags can be provided by other modules.

This module's audience is developers who require machine names for taxonomy vocabularies, including views support. This module allows existing (and new) installations to continue using the Drupal 6 taxonomy API while gaining the benefits of vocabulary machine names.

As such, it should play nice with any taxonomy related modules (such as those that provide import / export features, etc...)

Taxonomies are a bit of an issue to deal with in Drupal, specifically in terms of using them in install profile or update hooks, team development, and deployment through environments.

There are a few modules out there which try to get around this issue. However, they are limited in a number of ways. Currently there are 3 methods I can see in trying to solve this. This module goes with #3.

1. Use existing modules (such as features_extras or exportables). This provides taxonomy (among other) machine name support, however, it can require multi-module dependencies, and typically require additional calls while programming. As well, there is typically no views support to remove "vid"s from view exports.

read more

• Legacy Protector Provider Classes for Pre and Post Check Removed
• Protector Provider on now by Default

Chuck Norris ordered a Big Mac at Burger King, and got one.

Minimal feature set: creates a block with random Chuck Norris "facts". Could be used to display in admin UI to prevent admins from falling asleep while administering boring Drupal sites.

We are pretty sure Chuck Norris deserves a dedicated module and have some ideas about what the module functionality should be. However, Chuck Norris is too much for a single brain to comprehend, therefore we ask the community to contribute ideas for the Chuck Norris module.

cheers.