Seeking new maintainer

The presets module provides an API for creating a set of settings to accomplish more advanced functionality on a site that requires multiple modules set up a certain way. Traditionally, the only way to accomplish this was to create a “recipe” or howto of how to set everything up and hope people could follow it.

These howtos often looked like this:

1. Download and install these modules.
2. Create some content type with these fields.
3. Create some views with these properties.
4. Set up some vocabularies like this
5. Go to this module’s settings page and enter your API key.
6. Go to this module’s settings page and set this up.

Oftentimes a step was a little vague or misunderstood when being followed by an end user and after following the instructions, things didn’t work. In addition, the end user didn’t really know what they did right or what they did wrong and how to fix it.

This is where the presets module comes in. Presets allows a developer to not just develop a “howto” for setting up some functionality but to add checks and quick fix links to each of those settings. With presets you can say which modules are recommended for the feature, have a list of settings for those modules with help in setting them up, and a general overview of if each of those settings are set correctly.

Help your visitors find relevant information much easier with yolink search for Drupal!

The yolink module digs under search result links to present users with the information they want. It currently layers seamlessly over core search (D6 and D7), Apache Solr (D6), Google Custom Search (D6 and D7), and Lucene (D6). We plan to also incorporate our own indexing in the near future.

Because yolink also presents sharing options under each result, the yolink Drupal module may help improve time on site, page views, and overall traffic.

This is a very simple install, and you’ll be very pleased with the results. Try yolink search today!

Installation instructions:
1. The yolink Drupal module searches under links. You'll currently still need a base search module for yolink to layer over. In Drupal 6, you'll need to enable either core Search, Apache Solr, Google Custom Search, or Lucene. In Drupal 7, yolink has been tested with core Search and Google Custom Search.
2. Run cron to index your content.
3. Download the yolink module (below) and unzip to your Drupal modules folder.
4. Enable the yolink module.
5. Under User configuration -> Permissions, make sure users have permission to search.
6. On your Drupal administration page, click the yolink link.

This is a Drupal module that fetches and parses OAI_DC (Dublin core) metadata records from OAI-PMH services, as defined by http://www.openarchives.org/. It depends on the Feeds module.

Features

• Harvests from OAI-PMH repositories, respecting resumptionTokens, compression (but no deleted record support yet).
• Can map OAI_DC metadata into Feeds targets (CCK, taxonomy, etc.) (other metadata schemas can be supported by this or other modules in the future, today you can roll your own using existing modules)
• Can harvest from the entire repository or a single set. Available sets are loaded in via AHAH when creating the importer.
• You can set up multiple harvesting rules/mapping per set and/or repository as you desire.
• Record storage handled by Feeds: nodes (CCK support), raw database, etc. Extensible with other modules.
• Cron scheduling handled by Feeds: as often as every cron run up to a month between harvests.

Requirements

You need the Feeds module and its dependencies (Ctools, etc.) This module has been tested on Feeds 6.x-1.x-beta10.
Recommended additional modules: CCK, Link (to hold the resource URLs)

Usage

Object cache is a simple module using Drupal's cache API to store and retrieve objects (nodes, comments, users etc) to speed up rendering of pages, to lower the number of requests to the database and so on which benefits both anonymous as authenticated users. Since the Drupal cache API is used, these objects can also live in memcache or any other storage mechanism you can think of.

CiviEvent Discount allows you to create discount codes and assign them to events and membership.

Features

• Support for price sets and individual items in a price set
• Use of monetary or percentage based discounts
• Automatic discount based on membership
• Generate random discount codes
• Usage and assigned code tabs on a contact record
• Code summary screen displays usage for a given discount code
• Experimental: Ubercart integration for memberships
• Experimental: Views support
• Experimental: Apply discounts against offline memberships and events
• Option to apply discounts to additional participants

Ubercart integration

The latest stable and -dev releases include support for Ubercart. If you enable CiviEvent Discount for Ubercart, a new class (content type) will be created called Membership discount. This allows you to create a new product (node) with the desired code settings. When someone purchases this product, a code will be generated after checkout and posted to their order summary and can be used immediately.

Theming

The placement of the discount code textfield is controlled by CiviCRM. By default, CiviCRM places it at the top of the page. You can customize this and other functionality by overriding the templates.

User Relationship Locator extends User Relationships module to provide the ability to find and add new user relationships based on user information provided by a sub-module.