jQuery User

Component type

module

Maintenance status

Development status

Component created

Component changed

Provides a jQuery UI dialog with tabs of the common user account operations "Login", "Create new account" and "Request new password".

The operations will be loaded on request only. Error messages and cross-links between these operations are all done within the dialog. It's also possible to configure whether the user should be redirected to its profile page or just reload the current page, based on current path. The destination GET argument is properly honored.

Key-value Queue

Component type

module

Maintenance status

Development status

Downloads

621

Component created

Component changed

An abstract implementation of the Drupal Queue API. It will contain multiple strategies for cache managing, and it is possible to easily plug in different backends (like APC or memcached).

This module is sponsored by Pronovix.

Browsing History

Component type

module

Maintenance status

Development status

Downloads

741

Component created

Component changed

A feature (see Features) that implements fully fledged browsing history using Flag, Rules, and Views.

Features

  • Includes browsing history for content, categories, and basic searches.
  • Provides a "recently viewed content" block on node pages.
  • Provides a "My browsing history" page with content or category history as the main view and content/category and search history as secondary views.
  • Individual history items can be removed by the user.
  • Provides an ON/OFF switch to allow the user to disable and clear, or re-enable their browsing history.
  • Supports both authenticated and anonymous users.
  • Works with pages cached using Authcache for authenticated and anonymous users.
  • Is fully configurable via Flag, Rules, and Views UI's (with the exception of Authcache support.
  • Can be extended with Browsing History Flag Recommender to provide browsing history based content recommendations.
  • Conforms to KIT Features Specification..

There is a full discussion of why and how it was put together at Browsing history for Drupal.