Site navigation

Overview

This module allows to process nodes of selected content type and replace the words in the nodes with a links to taxonomy terms if it exists.

Installation

Installation is as simple as installing the module.

How it works

1. After standart installation Users will be able to do configurations via admin/settings/activetl/settings

2. Add links -> here Users will be able to select content type, content type's fields and vocabularies they want to use.

3. This module is not a copy of http://drupal.org/project/alinks, it is totally different. Because Current module rewrites the fields (Alinks does not change the node body as it is executed on display only)

Active Taxonomy Links prevent server loading induced by huge amount of content.

4. Users are able to check the module work results on the config page
a. the quantity of nodes from content type (total);
b. the quantity of nodes from content type (already processed);
c. percent already processed nodes.

5. Users are able to input the quantity of nodes for processing.

6. Users are able to delete the Modules results.

7. Module automatically proceed new added or created nodes.

This module provides a toolbar at the bottom of the window, like Facebook's Application Bar, which shows links (from a menu) on the left and AJAX-driven notifications (from system messages and/or other modules) on the right. It is meant to provide an easy way for users to see alerts or get to certain parts of the site.

This module is to make recommendations for points-based voting modules including Vote Up/Down and Plus 1. You have to enable either of them in order to use this module.

This module looks very much like the Fivestar Recommender, except that this module targets on Vote Up/Down and Plus 1. In fact, most codes are copied directly from the Fivestar Recommender module. Once enabled, this module provides 4 blocks:

1. Users who voted similarly as you
2. Recommended nodes from users who voted similarly as you
3. Other nodes voted similar to this one
4. You might also interest in these nodes based on your previous votes

For more details about the algorithms, please refer to Fivestar Recommender.

Note: The developer has consciously made the decision to keep Fivestar Recommender and Points Voting Recommender as two separate modules, rather than one big module for generic VotingAPI-based modules. The major reason is to simplify configuration process because configurations are hard coded in the code itself.

Sponsored by Google Summer of Code '09

This module, once enabled, provides 4 blocks:

1. Users who voted similarly as you
2. Recommended nodes from users who voted similarly as you
3. Other nodes voted similar to this one
4. You might also interest in these nodes based on your previous votes

The first 2 blocks are computed using the User-to-user algorithm. The first block returns a list of users who have made similar votes as the current user. The second block then recommends a list of nodes to the current user that were highly voted by those users from the first block. For detailsof this algorithm, please refer to: http://portal.acm.org/citation.cfm?doid=192844.192905

The other 2 blocks are computed using the Item-to-item algorithm. Block (3) returns a list of nodes in the sense of "users who liked this node also liked". It's different from block (2) because block (2) is personalized towards the current user, where as block (3) is not personalized. Block (4) returns a list of nodes similar to the nodes you voted highly. The "item-to-item" algorithm is also used by Amazon.com. Please refer to http://portal.acm.org/citation.cfm?id=642471 for more details about the algorithm.

Envts (Environments) module
by Ben Buckman (thebuckst0p) @ EchoDitto (ben at echoditto dot com)

This module was created to fill the need for *two-dimensional* environment/host management.
* What's an environment? An environment is a development or server location where a full Drupal build (possibly including multiple hosts) is set up. In our work, we tend to have
1) a primary 'dev' environment (site.dev.ourwork.com),
2) local environments for each developer (site.dev.local),
3) a staging environment (staging.site.com),
4) a live site (www.site.com), etc.
But each of these environments can have multiple sites/hosts, making the number of actual hosts to track and toggle grow exponentially.
The domain_access module does a good job of tracking hosts, but in only one environment.

The goal for now is not to manage deployment between multiple environments, but rather to allow for managing content between the environments, and more generally to have code- and user-level context awareness of each environment. The module is currently a barebones API, to be expanded upon for various use cases. I'm interested in hearing what use cases people have.

Envts has no UI yet, but simply allows other modules to define environments with a hook. (Anyone is welcome to create a UI for the module, since my time is limited!)

The Smart menus, Smart tabs duo of modules make everyone's Drupal experience just that little bit more convenient. The two modules give menus and tabs a memory, so that when you revisit a page, your previous tab or menu choice is already pre-selected for you. Not only will this save you numerous clicks, it will almost feel like the system senses where you'd like to go, making the experience more intuitive. No longer will you have to retrace your clicks to get back to where you wanted to stay or waste clicks to escape from Drupal's rigid default selections. Instead you'll find that Smart menus and Smart tabs create default selections naturally, based on your personal click patterns as they evolve during the session.
Once you've used these modules for a while you won't notice they're there -- but you'll miss them when they're gone.