Quote for finishing up pay node module

Submitted by giggler on Thu, 02/07/2008 - 11:16

Posts: 48
Joined: 01/31/2008

This is regarding the following module that Julia is trying to solve with Ubercart. Though a solution was found using e-commerce, I think Ubercart is better and should have the ability to do this since Drupal has a lot to do with community/user submitted nodes. I know Ubercart wants to set itself apart from e-commerce, but it should set it apart by having better features and not necessarily by not including something just because they have it.

Since Julia offered a bounty on it and no one seem to be taking it, how much would it take to finish up a module like this or is it just impossible to do:

http://www.ubercart.org/forum/development/2121/uc_nodetype_module_purcha...
http://www.ubercart.org/forum/bounties/2879/javascript_issue_file_upload...

permalink #1 Thu, 02/07/2008 - 13:23

NikLP

Posts: 5
Joined: 11/29/2007

I think that being able to "buy nodes" is a real bonus that ubercart would do well to implement. It's simple, and the support for userpoints is already there, afaik.

This would set ubercart apart as a solution for selling the most simple things, most easily. Early adoption of these simpler things would lead to more developers and hopefully greater traction across the board, which means more core work?

Could be wrong... Smiling

permalink #2 Thu, 02/07/2008 - 14:51

JuliaKM

Posts: 37
Joined: 11/28/2007

Thanks giggler! The more I work with pay-per-node, the more I think that we should scrap uc_nodetype and try to adapt pay-per-node for Ubercart.

It would be especially cool if someone could hook into recurring purchases so that nodes could be repurchased when they are close to expiring.

permalink #3 Thu, 02/07/2008 - 16:58

giggler

Posts: 48
Joined: 01/31/2008

I thought about asking the creator of pay-per-node to make one for Ubercart also... I'll try and send 'm something.

permalink #4 Fri, 02/08/2008 - 11:03

JuliaKM

Posts: 37
Joined: 11/28/2007

As I explore pay-per-node more, I'm noticing that one feature that's lacking is the ability to tie node creation to workflow status. uc_nodetype actually does this right now.

It would be great it you could set a node to be added only when a transaction is completed. We could easily add some sort of email notification to this. So, say that I purchase a job listing online and pay with an invoice, when my invoice is received, a site administrator could set that status via ubercart and I would get an email explaining how to create a job.

permalink #5 Sat, 02/09/2008 - 13:21

cwittusen

Posts: 13
Joined: 01/30/2008

Hi:
I have been following your thread closely ever since I once again reinstalled ubercart hoping that I could get the effect of someone selecting a product that will allow them to fill out a form and then hit submit that then put it in their cart and once they are ready they can check out. Upon receiving payment the node is posted and I get notified about it and I can work on it (house comparable report) but so far it doesn't seem like ubercart can handle that (seems like a simple integration).

Your post's are right inline with what I want to accomplish so I am willing to add $100 to bounty of getting a module like that finished.

/Chris W

permalink #6 Sun, 02/10/2008 - 14:25

torgosPizza

Posts: 1140
Joined: 08/14/2007

Julia, if you get a chance, can I check out your ec_paypernode module on your site to see how it works? Not sure what you'll need to do to get that working. But I'm looking at ec_paypernode and thinking of adapting some of their code for an Ubercart module, but that UC version will be more based off allowing users who purchase a Product Creator role to be able to do just that. That way we could have the module be fairly independent and only rely on the user having the proper permission. From there you can set # of allowed nodes to create, expiration, etc.

Also, what were you looking at with regards to tying the paypernode module into Workflow-ng? I would imagine the Payment complete features and that sort of thing. That's probably a good idea, looking ahead...

"Pain don't hurt." - Dalton

Mike Nelson's RiffTrax! www.rifftrax.com

permalink #7 Sun, 02/10/2008 - 18:12

giggler

Posts: 48
Joined: 01/31/2008

"From there you can set # of allowed nodes to create, expiration, etc."

and probably set the type of nodes (content type) they are allowed to create... But say if I were a user and I purchase a Product Creator Role (say story) so I am set to create 1 story node. After that what will happen to the role, will it just be back to default user role...and then they purchase another Creator Role to create another node? If they purchase multiple nodes, how will it know which type of nodes if it's based on roles?

Also if it is set that someone can create 5 allowed nodes, would they all be the same type of nodes since it would likely be hard to distinguish one type from another if it's based on role?

Sorry if this is confusing or I'm just confusing myself now. I think I might take a look into pay per node by ecommerce also to see how it's really working. But the idea of paying per node will be more clear as to exactly what type of node it will be that they are paying for.

permalink #8 Mon, 02/11/2008 - 23:20

giggler

Posts: 48
Joined: 01/31/2008

Read the comment from TR about using workflow-ng...

http://www.ubercart.org/forum/support/3159/selling_story_access

permalink #9 Fri, 02/22/2008 - 21:20

richygecko

Posts: 15
Joined: 02/22/2008

I would be willing to add a $100 bounty to this. It would be perfect for Advertising Campaigns and Job Boards.

I definitely believe that users should be able to create the content first and pay to publish it. (and expire after a certain date)

1. their created content is reusable. Their unpublished data can simply be paid to published again

2. I feel that users will be a bit annoyed that they have to pay first if they do not know exactly what they are going to get / are up against. In a job board setting paying for a node and then having to run around to get all the necessary data for the job post might put some pressure on them.

3. Being able to create a post then preview that post prior to paying for it would be ideal

If anyone has a working or partial solution that they would like to share please let me know. I would love to get this project out.

Best,

Nathan

permalink #10 Sat, 02/23/2008 - 02:19

giggler

Posts: 48
Joined: 01/31/2008

Paypal Node is able to do this if you are open to using paypal. You can also edit the module so that it is based on subscription, so you don't have to really worry about expiration or reposting except when they decided to cancel the subscription. Which paypal will send you a note, then you can mark the node for unpublish time. I also found a way for it to work with advertisement module with one simple code change.

But if you need authorize or other payment method, then this module being worked on will be your best route...once it works perfectly.

permalink #11 Sat, 02/23/2008 - 03:08

richygecko

Posts: 15
Joined: 02/22/2008

giggler,

Thanks for the advice. I looked into the paypal node and was "surprised" that it had the pay to publish option where the other larger systems ecommerce and ubercart didn't. No too surprised... i realize ubercart is still technically beta. However as I am hoping for a lot of traffic and like the other management options available in ubercart and also wish to move away from paypal (scares me if large money is involved), I have installed the uc_nodetypeV3 that was previously posted and have been poking around the code a bit but as I am not the best programmer I'm not sure how much help i can be. But I am willing to help out as best and pay some if needed.

You mentioned

Quote:

then this module being worked on will be your best route...once it works perfectly.

Does that mean this is in the works? At this point where does it stand?

Best,

Nathan

permalink #12 Sat, 02/23/2008 - 17:23

richygecko

Posts: 15
Joined: 02/22/2008

After poking my head around for a bit I have come back to Ryan's post here:

http://www.ubercart.org/forum/support/1987/purchase_right_publish_node

Quote:

Well, the main problem here is that the event that gets fired when someone completes checkout takes the order and the user as arguments. The action for publishing a node requires a node object to be passed to it, so it's not available for the completed checkout event. With a little bit of code mojo you can create your own action that will find the referenced node and publish it.

Also I found someone is doing a publish action for the revision moderation action here:

http://drupal.org/node/175370

dunno if this is really anything but maybe someone with better php skills / "mojo" could use it to write the node publish action for here.

Best,

Nathan

permalink #13 Sat, 02/23/2008 - 23:42

giggler

Posts: 48
Joined: 01/31/2008

Julia probably has the closes thing (uc_nodetype) to what you need, however she is stuck but no one seem to want to work on it even if it's a paid offer. So unless if you can find a developer who can do this maybe in the Drupal forum(?), I don't know when there'll be a completely working module for it:

http://www.ubercart.org/forum/development/2121/uc_nodetype_module_purcha...

permalink #14 Wed, 02/27/2008 - 08:47

richygecko

Posts: 15
Joined: 02/22/2008

giggler,

Thanks for all the input. I decided to work out my ideas in the the above post and have come up with an approach that fits my needs. I put it in a separate post as it is not related to this module. It can be found here:

Pay to Publish using workflow_ng

Best,

Nathan

permalink #15 Wed, 02/27/2008 - 21:17

giggler

Posts: 48
Joined: 01/31/2008

Thanks - will try this when I get a chance!