By budda on
I'd like to provide users with the opportunity to create different types of nodes, but charge them for each node they want to create.
Ideally I'd like to make use of existing components as much as possible.
My initial thoughts are to describe each node type in an ecommerce product node. The user can then buy a product node. But what's the best way of then allowing the user to create 1 of these nodes after payment has been taken?
The user can create more of the same node, as long as they pay again for it.
Is this possible maybe by creating a new ecommerce product type module? Suggestions welcome!
Comments
Suggestion
I think it would be a good approach to create a credits module for e-commerce (if it doesn't already exist), in which a person purchases "credits" which can then be "spent" any way you choose.
Look at the userpoints module. It assigns a value to each node type, and then gives a user points based on activity (creating comments, nodes, etc.). You could use the same approach to deduct credits from a user's account when they create a node.
I know the framework already exists to do this, but, since it is a specific usage, the module probably has not been created yet. That being said, if you build the module, it would be nice if you shared it with the community! ;o)
- Corey
I think adding the aspect of
I think adding the aspect of credits to the process may confuse some "simple" users when they are trying to pay to create a node (in my case pay to place a classified advert).
--
Ixis (UK): Drupal support, Drupal hosting.
money
a lot of people want this, including myself. so far no one has sponsored it
I agree adding a layer of credits is very confusing.
also userpoints is buggy and i have not been able to get it to do this.
Userpoints works great for
Userpoints works great for me ( 4.7). I've using custom code to do something similar, with userpoints.
Purchasing from the store using the ecommerce module. This can be used as a reward points system.
What problems are you having with userpoints ? http://drupal.org/project/userpoints
The developer for userpoints would happily fix them. He is very active the forums.
Contact kbahey - http://drupal.org/user/4063
UserPoints also has a API.
The functions are:
hook_userpoints($points, $uid)
userpoints_get_current_points($uid)
marcel
http://01wholesale.com
http://01ftp.com
money
I am thinking of sponsoring this
please post here or private message me with an estimate of hours/cost.
I'd like to launch by Aug. 31st.
thank you.
Please post here if you'd like to contribute.
I'm thinking of using the lm paypal module as the gateway.
Ready and willing
If anybody can chip in with suitable suggestions on the best way to tackle this problem i'm happy to do the work to get it in to a usable module.
I'm just looking for some guidance/advice on an implementation that's flexible and node-type independent.
--
Ixis (UK) providing Drupal consultancy and Drupal theme design.
--
Ixis (UK): Drupal support, Drupal hosting.
great
that's great! I don't know how to code it but if there are ways I can help, just let me know. If you are able to write it without charge, I could even pay a core developer to talk with you for an hour (or more) and give you ideas about what would work and not work.
irc
budda,
I just realized I don't know what you've tried.
have you tried drupa irc? you can always try back several times because different developers vary in their willingness to address questions they are not working on.
i don't know how active the ecommerce developers irc is.
and you can of course try the ecommerce developers list, plus group ecommerce.
I've loitered on
I've loitered on #drupal-ecommerce for a week or so, asking this question, and pointing to this node - hoping somebody might have some ideas on how to work to the goal.
However due to being in the UK, the time difference with Australia isn't always ideal to catch the active ecommerce developers.
If you're able to get anybody to look at this node in the meantime that would be handy mariun!
--
Ixis (UK): Drupal support, Drupal hosting.
A suggested solution is to
A suggested solution is to allow a user to create a node, and then add an item to their shopping cart. Until the item is paid for by the user, the newly created node remains unpublished.
Upon payment completion the node status changed to published.
Unpublished nodes could remain in the database if users decide not to make the purchase. A regular cron job to clean up the stray nodes could be performed.
Would this be acceptable? Comments welcome.
--
Ixis (UK): Drupal support, Drupal hosting.
gordon
Hi Budda,
I wrote Gordon and offered to pay him to walk you through this. He said he'd get in touch with you. Can you email him please?
I'd have to think about what you suggested. I'm not inclined toward it because of the complexity for the user. thank you.
Alternative suggestions are
Alternative suggestions are welcome. Please post.
--
Ixis (UK): Drupal support, Drupal hosting.
What I did for a similar
What I did for a similar case is to add a "buy me" link to a sample node. The link goes directly to the payment processor, but I think it could go to the shopping cart instead. Upon completion of payment, I add a special property to the user object and save. When the user goes to /node/add/foo where foo is the node type I check whether he has the special property and delete it after the node got created.
--
Drupal services
My Drupal services
--
Drupal services
My Drupal services
cost
Dear Killes,
is your solution fully automated (no manual deletion, etc?)
I will send you a private message.
I would like to know how much it would cost to get this functionality.
Thank you .
Classified Adverts
My LM PayPal module provides paid adverts with payments taken by, surprise!, PayPal.
http://lmmrtech.com/lm_paypal_module_for_drupal
--
Lee McLoughlin
lmmrtech.com
Yeah, and also pay-per-node
That's right, and there's also the Pay-per-Node module: http://drupal.org/project/paypernode . Surely this does exactly what you want?
On a slightly different subject, is it possible to integrate lm-paypal and userpoints so users can pay for points and redeem points into cash?
another possible solution
@budda: sorry for the late time i answer back here man, you managed to answer my post on groups.ecommerce the day i left for my vacations! ;)
@mariun: i struggled a bit in the past looking for a solution to this issue too. IMO role subscription is not a valid choice, because then that role properties and permissions are reflected to *all* the node listings of a user (can be valid for other purposes though!)
What i am actually working on is a taxonomy (category) based solution:
basicly, a user can publish a node listing for free, and then buy a "Level" (something like Silver, Gold, Platinum) to upgrade his listing(s) and give it more visibility on the site as well as output more information (text or other fields in the content-type).
Once he pays for it, the node listing is "tagged" by the level. Once tagged, phptemplate and Views module can be used to publish (almost) any sort of combinations of nodes/levels.
I'm actually aiming at letting users publish a basic free listing, but tweaking the module and playing with Views it should be easily possible to force users pay for every node listing.
As about the workflow, it will be very similar to what Killes proposes.
The module will be called presumably Taxonomy_actions. You can read more about it at http://drupal.org/node/83079
please post comments there if interested!
cheers