| Attribute | Average |
|---|---|
| Features | 2 / 5 |
| Reliability | 5 / 5 |
| Ease Of Use | 3 / 5 |
| Documentation | 1 / 5 |
| Vote Count | 1 |
This module adds a new node option Premium content along with core publishing options (Published, Promoted to front page, Sticky at top of lists). When a node is published as premium content, only users with proper privileges may view the full content of the node. Non-premium users can still access premium... [More...]
| Maintainer: | anrikun |
| Links: | |
| Categories: | Content, Content display, Rules, User Access & Authentication, Views |
| Version | Date | Files | Release notes |
|---|---|---|---|
| 7.x-1.1 | 2011-Apr-02 | Download | Recommended |
| 6.x-1.2 | 2011-Apr-02 | Download | Recommended |
| 6.x-1.x-dev | 2011-Jul-18 | Download | Development |
Options: Add a review
There's a big need for Drupal to show a node's Teaser to some users, and the full node to other users, based on whether the user is in a particular role (member/subscriber/etc).
It's always been a shock that default Drupal doesn't do this, given how common it is on web sites. Drupal's "normal" action is to block all access to a node -- very crude, non-professional site behavior.
The classic case is a subscription-based site (magazine, newspaper, etc) that lets everyone see the article (node) titles and Teasers to promote them, and below the Teaser shows a message stating that viewing the entire node requires membership/subscription/etc. When a current subscriber is signed-in, and has been put in a certain Role (perhaps via Ubercart), the user can see the full node. This if often referred to as Premium content.
This module allow this control, quite simply. Assign the user to the Role, assign the role to the node type, then in a given node (article), check the Premium box to invoke the desired behavior. That part works fine.
The module's shortcomings are of two types:
1. The Teaser + explanatory message is not customizable, except by hacking. The module's developer says the hack should be to the theme's template file to add PHP code, which I find unacceptable. (I learned this only by posting an Issue; documentation is sparse and never mentions this major need.) But I think it's wrong to hack a major theme file used by multiple sites (mine is a multi-site Drupal installation) just to customize one module of one site.
Instead, I hacked the module's main file, which is where the message is. I changed the wording, added a link to my purchase-subscription page, and added CSS tags so I can better control how the message appears. The module really needs to allow this customization via a form, probably storing the message text in Drupal's Variables table.
2. The module is one-site-only. It could be enabled/disabled for multiple sites, but there's only one module installation with one message, so difficult to make this work in real situations. I'd like to see the module support some way (via standard Taxonomy, ideally, and/or the Domain module) to handle multiple sites, multiple users roles, and multiple messages, as is done by many other modules.
That said, the module works, and was simple to hack to revise the message for a single site. So it's a wonderful start for me, and might already be everything you need.
