Pay2Publish

This project is not covered by Drupal’s security advisory policy.

NOTE: the module was thought for Drupal 4.7 and then updated to 5.x. Has been abandoned with Drupal 6.x, as (almost) the same functionalities can be obtained with other more flexible means (mainly LM_paypal role subscriptions, views, phptemplate). Please contact me in case you are looking for a unified solution and would like to take it over.

Initial commit: the module is still in development and requires some PHPTemplate and Views skills to get things to work at it's best.

Pay2Publish lets users publish basic versions of listings (nodes) for free, and later be able to pay to "upgrade" them to custom Levels (categories) to add more visibility (Views plays) and/or show more information (CCK fields).

How does it work in brief:

  • set up different "Levels" with different costs and properties (Silver, Gold, Platinum style). Each level will have its corresponding taxonomy (category) term.
  • to upgrade a node, the user will have to buy the desired "Level" and assign it to one of his published nodes. The corresponding taxonomy term will be assigned to the desired node.
  • user will also be able to choose a duration in months. The final price will be a combination of Level x Number of months.

Once you've done that:

  • a condition can be used in the template of the content-type to show more or less text-fields or whatever fields (show additional information) depending on the level they bought.
  • Views will play the role of showing higher-level listings in specific pages and blocks views in the site (more visibility).

FAQs:

Q: Why not use role memberships to define different roles for publishers?
A: Tried this in the early days, but this way is not possible to differentiate levels on a per-node level. Each node published by a user asssume the properties of the role he buys. No good.

Q: Why not just add a price to publish a node type?
A: This way users have to pay a fixed price for each node they wish to publish. This is very straightforward and effective, but also can be a showstopper for some users who would like to get familiar with the site before actually paying for publishing.

Q: And why not have a node-type per level instead of taxonomy levels?
A: True, different per-level content-types each with additional information fields could be set up, but in this case issues would arise when a user decides to upgrade/downgrade a node listing (he should copy the information into the new node and delete old one).

Requirements: E-commerce, Taxonomy or Category (4.7 works with Category module only!).
Strongly suggested: CCK, Views.

Project information

Releases