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

JSON server

JSON server

The JavaScript server provides a JSON backend to the services module.

This means that you can access the outputs of any service in JSON, by POST-ing to a URL.

FeedAPI

Note: FeedAPI versions lower than 1.9 are not compatible with Drupal 6.14 or higher (see #580508 for details).

The maintainers of FeedAPI launched a successor project: Feeds. Read more about the future of FeedAPI in Good bye FeedAPI, hello Feeds and upgrade FeedAPI to Feeds.

FeedAPI aggregates feeds on a Drupal website by generating light weight items or nodes from feeds. It provides a straightforward configuration for most use cases and is extensible through an API. FeedAPI integrates with OG (but does not require it).

CurvyCorners

CurvyCorners 7.x-1.x-dev Beta on Drupal 7
This module is abandoned due to a security issue the maintainer didn’t fix. See SA-CONTRIB-2013-008 - CurvyCorners - Cross Site Scripting (XSS) - module unsupported for details.

If you want to use this module, your options are:

#D7CX: I pledge that CurvyCorners will have a full Drupal 7 release on the day that Drupal 7 is released.

What is CurvyCorners?

A free JavaScript library for creating gorgeous rounded corners for HTML block elements i.e. DIVs. Supports anti-aliasing, borders and background images.

Why use CurvyCorners?

Level1 Node Access

Level1 implements a simple "level" based node access system using a single vocabulary defined by the taxonomy module. Level based access is defined as a cascading access based on the user level compared to the level of the content. An example makes it more clear.

----------
For Drupal 7, a module that can be used to accomplish level1's functionality is Access By Term.
----------

Say you want to create content and put it into one of 3 levels. You coulddefine a vocabulary, lets call it Level1, with the following terms.

Beginner
Intermediate
Advanced

The vocabulary is non-hierarchical and the terms are weighted as appropriate for the desired cascading order - ie. Advanced is heavier then Beginner.

Now you can start "tagging" your content with any of those 3 options (4 if you also allow "none" which is perfectly valid and a content with "none" is not access controlled by Level1). As with all vocabularies, its also up to you which content types to apply it to.

Next you edit your user accounts and also put users into one of the 3 taxonomy levels (or 4 if allowing "none"). In otherwords, you assign the taxonomy term to your users as well.

Pages

Subscribe with RSS Subscribe to RSS - Unsupported