Content display

Please download the latest development snapshot.

This project uses Nodequeue's Smartqueue API to provide a nodequeue for each user of one or more specified roles.

This project was originally written by ezra-g as part of the 2008 Google Summer of Code and provides the following functionality in the list below.

The 6.x-2.x branch is a rewrite by daniboy that allow for multiple subqueues per-user.

1) Administrators can specify which user roles automatically receive nodequeues
2) When a user of a specified role is created, a nodequeue corresponding to that user will be created.
3) When a user is deleted, the corresponding nodequeue will be deleted.
- a) The module should prompt and warn the administrator before deleting the nodequeues.
4) Administrators can specify which node types should be available in user nodequeues.
5) An 'edit own user nodequeue' permission will be defined to allow for use cases where users cannot edit their own node queues, such as a list of selected content by a particular user that is maintained internally by website administrators\moderators.
6)The content of the user-nodequeue will display on the user's profile page
- a) The module will define a default view that is utilized on the user profile page

This project uses Nodequeue's Smartqueue API to provide a nodequeue for each organic group, editable by members of that group or the group's administrators. This project was part of the 2008 Google Summer of Code.

Use the dev snapshot release or the latest from CVS HEAD until RC3 is rolled

1) When an OG homepage node is created, a nodequeue that corresponds to that OG homepage node will be created.
2) When an OG homepage node is deleted, the corresponding nodequeue will be deleted
3) Depending on configuration
- a) Members of the Organic Group and site administrators will be able to manipulate the nodequeue for that Organic Group.
- b) Administrators of the Organic Group and site administrators will be able to manipulate that OG's nodequeue.
4) The content of the Organic Group's nodequeue displays in a block defined by a view, provided by this module
- a) Administrators can specify an alternate view that will control the display of OG nodequeues
5) Administrators can specify which node types should be available in OG nodequeues

For the complete project proposal, visit http://groups.drupal.org/node/10067 .

Requirements

- You must install the latest version of Nodequeue.module!
- You must have PHP 5.1.0 or higher to run this module.

Please Note

The Mobile Codes module provides the ability to render Text, URLs or any other form of informaton as a Mobile Code, including but not limited to the QR codes and Datamatrix formats, providing a simple way of transfering said information from the screen to a Mobile phone.

Mobile Codes was written and is maintained by Stuart Clark (deciphered).
- http://stuar.tc/lark

Features:

• User definable and Features exportable Mobile Code Providers and Presets.
  • Defaults provided:
    • Six (6) External Providers.
    • One (1) Internal Provider (see below).
    • Three (3) to five (5) Presets (based on installed modules).
• Render Mobile Codes via:
  • CCK/Fields/Views formatters:
    • CCK/Drupal core Text module.
    • FileField/Drupal core File module.
    • ImageField/Drupal core Image module.
    • Link module.
    • plus an example Custom Formatter for extended support.
  • Input filter.
  • Drupal API Theme() call.
• Blocks:
  • Node URL block - Creates a Mobile Code of the current Node URL.
  • User vCard - Uses the vCard module to provide a vCard Mobile Code from a Nodes Author or a users profile.
  • [D6] Mobile Code generator - An Admin module optimized helper block.
• Support for:
  • [D7-DEV] Drupal core Image module - Use an Image style on the Mobile Codes.
  • [D6] Mobile Tools module - Redirect internal Mobile Code URLs to Mobile site URL.
  • [D6] Redirecting Click Bouncer module - Track URLs accessed via Mobile Codes.
  • Shorten module - Shorten URLs in Mobile Codes.

AHAH Fragment is a module which returns a specified fragment from the requested page. This allows users to create callbacks for AHAH functionality with little or no code.

Note: As of 2009/07/24, this module appears to no longer be supported. If you are interested in a module with similar functionalities, you can check Advanced Blog; if you as the module maintainer feel this message has been posted in error, please reply to #432248: Blog Add-ons, Blog Information, and Blogger seem abandoned.

Blog Add-ons module adds some useful features to core blog module. It deals only with an existing content (no modification of db) so it can be easily installed and uninstall without affecting Drupal.

This module provides a way to find similar nodes by taxonomy using views.

Features:

• Weighting by vocabulary - Say you have two vocabularies on a movie site "Genre" and "Community Tags", the latter being a free tagging taxonomy. With this module, you can give Genre a weight of 10 and Community tags a weight of 1. Which means that if I'm looking at "Meet the Parents", I'm most likely to see a list of similar Romantic Comedies like "Sleepless in Seattle" and "French Kiss" with something like "Taxi" or "The Godfather II" coming lower in the list, because someone tagged both "Robert De niro"
• Sorting - Sorts by weight... pretty simple
• Filtering - I want to see only those with a weight higher than 15... this is a little arbitrary, and you are better off using the pager / limiting results, but it does work - Actually, doesn't. I tried to hack around views not letting me mess with the count query, but just couldn't get a HAVING in there... Oh well.

Usage:

1. Install the module (duh)
2. Go to admin/settings/similarnodes
3. Set the weight for each taxonomy
4. Now create a view, add the argument "SimilarNodes: Source Node Id" - You need this to make it work
5. Add the field SimilarNodes: Weight