Wishlist: Pay-per-Post

[blatternet]

Hi there,

I know the Pay-per-View-Feature of eStore. But what would be really cool: A Pay-per-Post-Feature in eMember.

Look: I have some premium-content for members like checklists, longer articles,… There are visitors who don’t want to become a member but want to have this checklist or that article. I can’t make for every premium-content a new eStore-product, so a Pay-per-Post-Feature would be really cool.

Regards from a dreaming

Ivan

[admin]

Our new Pay Per View feature of eStore might do the job. This feature lets you use a URL (a post or page) as your digital product:

WP eStore’s Pay Per View – Using WordPress Permalinks as Digital Products (APR)

If you like it then thank Assurer for adding it to eStore

[blatternet]

Almost.

It’s a great feature (thank you Assurer ), but one problem remains: I have to add a new eStore-product for every post or page. That would be no problem for 3, 4 or 5 URLs. But for 20 or more it’s a little annoying.

I think more of a real Pay-per-Post-Feature. My dream: When I write a post I can activate the Pay-per-Post-Feature and I can set a price for the post – that’s it.

There are other membership-plugins that can do this. But none of them is as good like eMember, so I don’t want to change.

[wzp]

The eStore APR feature offers the pay per post feature through the eStore side of the house, so that it can be membership plugin independent.

In the future, an API might be added, so that eMember could automagically add posts to the product database. Once added to the database, all you’d need to do is add a buy now button to the post.

[kimjcastleberry]

I agree totally with what blatternet is saying.

I’m looking at the possibility of needing pay-per-post for over 100 posts.

The amount of overhead needed makes me wince.

Normally I’d grab another plugin for this solution but at this point I really want to stay working within the TTHQ plugin stack and integrated into my own affiliate system.

Perhaps wzp’s suggestion could be considered seriously.

[mxmark]

I’m also in on this dilema.

I have WP eStore and WP eMember which I would really like to use together, but unlike the above posts I’m not too concerned about having to setup new URL’s for each new pay per view product.

Over the past few days I have been rigorously testing the 2 aforementioned plugins together to see if I can achieve what I need.

Here’s what I’ve been doing and encountered:

Setup a free members area (done)

Setup a main premium page with all the links and pay buttons to the pay per view content(done)

Setup the protected premium pages with the pay per view content in them (done)

After carrying out some test purchases here’s the problem I’ve encountered…If someone buys premium product A they’ll obviously gain access to premium product A. Now lets say later that day or whenever this same customer wants to buy access to another pay per view product (product In theory he or she should have access to both product A and product B but this isn’t happening. They will lose access to their first purchase and gain access to their latest purchase (product .

If there’s a way to set this up where if a member buys premium product A and then after buys premium product B, to allow them access to both purchased premium pay per view products (products A + .

Or alternatively they initially buy premium product B first and follow that by purchasing premium product A they’ll still have access to both A + B no matter which order they purchase them in.

Hope I’m making sense with my explanation and I’m all ears if there’s a workaround for this without having to give them access to both A + B manually through the dashboard?

[wzp]

Since any pay per post functionality shares the same code base as the APR routines for eStore; the following implementation decision needs to be made:

Should we require use of both eStore and eMember, or do we have it as an eMember independent feature? If it requires eStore *with* eMember, you obviously need both plugins. If it is an independent eMember feature, we increase the memory requirements for those who have both plugins.

I’ll need to privately consult with @Admin on this and other issues.

[kimjcastleberry]

I personally don’t mind the requirement to use both to make this happen.

It really is code-base from both that if added to eMember would be somewhat redundant based on the current code-split style being used.

But if we’re going to bring both in, then it would be best to do a deep integration to prevent the issues that mxmark is seeing. If someone pays for a post, make them have a way to access all 5, 12, 20+ videos they’ve paid for. This will probably require making them a member record (which I think is why pay-per-post is part of wishlist member, it’s using deep integration into the membership system).

[Author]

Posts