Maintenance fixes only

Module to convert the 6.x Favorite nodes instances to flag.

Handy UI tool to generate Ubercart "cart links".

Users with permissions to access the cart links builder can generate cart links without memorizing the URL format or finding node IDs. A simple form gives them this workflow:

Exposes all boxes (using the box module) as tokens. Also adds all available tokens to the help screen.

This is fork of the subuser module. I need this working and the original seems not going forward at the moment.

Original Module Page:
http://drupal.org/project/subuser

I will commit patches from the original issues if I need them and and add/fix things where no patch is available.

I have this common request from my clients to allow them to "name" each individual sub-queue of a smartqueue. so for example, if I have three smartqueues, LEFT, CENTER, and RIGHT that print lists of content for various tax term pages in those lcoations, we may want to title them differently for different terms. Not all left lists are the 'hottest' content in that category.

Provides an autocomplete FAPI element, basically an enhanced version of a textfield with autocomplete, with the benefit of hiding away the real record ID. It allows the user to search and select an appropriate record as normal but uses a hidden field to store the selected record ID.

Commerce Popular Projects looks through your Drupal Commerce orders and figures out the most popular products for a given timeframe. You can include/exclude product node types, set the timeframe for your popularity ranking and calls a View to display your Commerce products.

The settings screen is found in the main Commerce store settings.

This project implements MercadoPago service for Drupal Commerce

At the moment I have developed two versions. Version 1 (7.x-1.x) was based on the old payment system from Mercado Pago (to be deprecated) and version 2 (7.x-2.x) for the newest API.

All that we see or seem
Is but a dream within a dream.
-Edgar Allan Poe

Context Bean block types display other beans (block entities). The block entity settings show all available contexts inside vertical tabs. Context Beans output a range list of beans selected by the user. The child beans can be of any block entity bundle other than 'context_bean' itself. Additionally, settings allow users to define a bean entity view mode on it's children for each existing context.

This module provides an additional table-like style to views that allows administrators to indicate that only some fields (columns) should be rendered by default but the user should have the ability to add/remove additional fields (columns) through drop-downs below the header and above the filters. The administrator can also choose which fields (columns) the user should have control over displaying.