Do it like this: You split the ordering from the node. I assume here that all nodes to buy have the same price, so you pay for the url so to speak

It is like a giftcertificate in a way..

Ok, I buy a job posting product. All this needs to know which url to a certain jon posting you do mean during this shopping session. (Attributes!!)

Under your created job posting which is published only to be seen by author and role "view special job postingS".. unchecked yet: After the ordering procress all folks with this role, the shopper guest in genereal can then see it as well..

You change the flag after the order has gone thru!!!

So, all you need to do is to alter the uc_attributes function by adding an if statement so that only attributes are shown for porduct type job posting that are made by the current viewer.. Goal: Only one current attribute offered..

Ok, all we need is a module offering a link under your job posting nodes created and only seen by you the author prior to order complete status. this then writes a new attribute into the attributes table (I think what we could even do is to use attribute option adjustments and do it like author id + job posting url = sku)

Done.

Thanks for the suggestion. I am going to start working on creating a custom action that gets fired when someone checks out. I really appreciate your help.

I was entering the URL for redirect to before the ? instead of after it. D'oh! The redirect is working perfectly now. Next stop, figuring out how to carry the nid of the new node throughout the checkout process.

Earlier today I finished creating a module which sounds exactly like what your looking for.

What it does is allow you to add a feature to a product which allows you to select the node type and number you would like to create during checkout.

The checkout pane then loads all the node add forms for each content type and stores them into a a serialized array waiting for the order to be completed.. once completed it pulls that information and saves them as nodes created by the user who placed the order.

This works nicely for anonymous customers as well because once ubercart assigns them a userid it updates the temporary node arrays with the new user id.

It does need some finishing touches but I'd be more than happy to post it as a contrib and if anyone else wants to take it over and improve it that would be great.

Let me know...

Thanks for the suggestion. I've looked at pay-per-node before and it seems like a nifty module.

One problem I see with pay-per-node is that the user first pays and then is able to create content. It seems like it would make more sense to first create content, then pay, then have the node published.

I'm trying to create a system for job listings, and after looking at other job sites, it seems like the model of creating content and then paying for it is somewhat standard.

hmm, on a different, perhaps more simple approach...
You could sell roles ("advertiser") and use views to only show the nodes of which the author has the role "advertiser"...

I'd say only create the nid at the END of the process - after checkout and post-payment. I would consider using the sequences table and the node_nid value found inside it. Then, upon order update, if balance is 0, yadda yadda, find the next node_nid in the sequence table and assign that value to the purchased node.

Maybe the creation of a uc_temp_purchased_nodes table to store these purchased nodes before the checkout completion process.

Just my thoughts. This sounds somewhat similar to the "user created content available for purchase" system I'll be working on for the next couple months. Let me know if you need anything!

Thanks torgosPizza. I am going to go with GileS solution. But, I started working on your method before getting his code. I thought that it might be risky to use the sequences table and instead grabbed the last node created by the current user. I'm not sure how I would handle it if users were not logged in. Here's how I ended up grabbing the node info.

I'm sure that there's a better way to do this.

GileS' code can be found at uc_nodetype: module to purchase right to publish node. Let's move the discussion there.

My problem is...I'm trying to charge for a product post. So, what would I have to do differently?