Not supported (i.e. abandoned), and no longer being developed. Learn more about dealing with unsupported (abandoned) projects

Nodelocks

Nodelocks prevents any user from deleting a node if that node has been added to a list of "locked" nodes.

⋅ Categories: Unsupported, No further development

CiviCRM User Reference

Reference User Reference, CiviCRM Contact Reference and CiviCRM User Reference fields

#NOD8CX: I have no plans to have a full D8 release within even a year of when Drupal 8 is released unless someone else volunteers to co-maintain that branch.

⋅ Categories: Unsupported, Obsolete, Content editing experience, Site structure, Access control

UC Legal Aspects

Adds a legal aspects pane for Europe to the checkout page.

Show General terms and conditions
Show Revocation rights

2 Checkboxes for completing the checkout

⋅ Categories: Unsupported, No further development, E-commerce

Jumpstart

"JUMPSTART" is an installation profile designed to get a site up and running quickly. It creates a Drupal7 site, enables some of the most usefull core and contributed modules while it does not enable some core modules that are enabled on the "standart" installation profile.

It helps for rapid-development, creating sandboxes and of course for every day drupal usage since it saves you some time (eg: it auto enables views).

Contrary to most Installation Profiles, Jumpstart is version agnostic.
This means that it can be used against any version of D7. This is true for
the modules too. The reason that Jumpstart is version agnostic is simple:
By itself it doesn't do much, it simply enables a set of common modules.

NOTE: drupal.org demands a version on each project that is being packaged. So an experienced user might prefer using the profile-only package instead of the one including core.

At the moment Jumpstart enables the following modules (and dependencies):
Views_UI
Transliteration
Admin_menu
Token
Backup_migrate
Colorbox (the .make file also fetches the script)

It doesn't enable comments, toolbar, overlay and several other core modules.
This shouldn't tamper with the users experience in any way though.

⋅ Categories: Unsupported, Obsolete

Boost Expire

[NOTE: This module has been deprecated as of June 2013 in favor of Cache Expiration. If you're currently using Boost Expire, please follow these directions to switch from Boost Expire to Cache Expiration on your site!]

A cache expiration module to go with Boost for Drupal 7.

Currently, Boost for Drupal 7 doesn't do any active cache expiration (see #1069438: How to Flush Boost Cache in Drupal 7.x), and this means that when you update a node, post a comment, etc., Boost will continue serving stale content from its static HTML cache until the file is finally cleaned up on a cron run.

For many sites, especially smaller sites where content is updated infrequently and cron may be run hourly or even less frequently, this means stale content will be served for quite some time, unless someone visits the Performance page and clears all the site's caches manually.

This module alleviates that problem by simply flushing Boost's static HTML cache every time a node or comment is posted or updated. You can set the module to respect your site's Minimum cache lifetime so it doesn't flush the cache until the minimum lifetime has passed.

This module may become deprecated in favor of a more universal solution (like Boost integration with the Cache Expiration module).

⋅ Categories: Unsupported, Obsolete, Performance, Developer tools

WSCCI Fake Demo

This is a temporary demo of what Larry thinks a module might look like in a WSCCI world, kinda sorta, as of early January 2012.

⋅ Categories: Unsupported, No further development

Pages

Subscribe with RSS Subscribe to RSS - Unsupported