This module allows users to export nodes and then import it into another Drupal installation, or on the same site.
Using this module you can save yourself a lot of time setting up new websites that have similar nodes to websites you've already made, migrating nodes to new Drupal versions, or between development/staging/production sites.
You will need the same content types for the imports to work (unless using Feeds to import), and ideally relevant compatibility with fields, and modules.
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
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).
Note: As of 2010/01/28, this module appears to no longer be supported. If you are interested in taking this module over, please create a report in the Drupal.org webmasters' queue.