7029 pointsLike some sort of WPMU DEV God"Mindblowingly helpful memberLifetime member
Aaron
Lead Developer
—
12th July 2011 (10 months ago)
Hey guys, here is an exciting announcement many of you have been waiting a very long time for!
Here is the early beta release of Supporter 3.0, now renamed "Pro Blogs". We have a ton of new features in this, it has been completely rewritten from the ground up:
- Pro Blog Levels!!!!!!!! And every optional module has full level support
- Coupons
- Permanent Pro Blog status switch
- Premium plugins/themes get removed on downgrades/cancelations
- Better stats
- Better blog management
- More customization/rebranding power
- Email notifications
- Every module spruced up and improved
- Front end checkout
- A new, incredibly powerful PayPal Express Checkout and Pro gateway:
Accept credit cards directly!
Allows modifications, level upgrades, payment plan changes, and cancelations by the user.
Powerful admin management: Process refunds, cancelations, partial refunds, and keep track of everything for the blog via a detailed audit log.
- And a whole lot more i've forgotten about!
So first off a warning, this is very early beta, and the plugin is so incredibly complex there's a good chance you may see the occassional php error, or a feature doens't work how it's supposed to. This is most true with the advanced checkout process, it has only had minimal (well days) of testing, but I need your help to work out the kinks.
So for now, please do not use on a live site unless it's real small and you can afford to work through problems your users experience.
Some things to know: - install in plugins and network activate
- remove all supporter files first
- Single payments are no longer supported, only subscriptions now (I may add them back later)
- The Amazon gateway no longer exists, it wasn't powerful enough for the levels and such (I may add it back if there is demand)
- If you have existing user subscriptions with the old paypal or Amazon gateways, make sure to copy the backwards compatibility IPN handlers to your webroot from the gateways folder.
I think that's it, please please test, and report bugs here so I can work them out.
Hey guys, here is an exciting announcement many of you have been waiting a very long time for!
Here is the early beta release of Supporter 3.0, now renamed "Pro Blogs". We have a ton of new features in this, it has been completely rewritten from the ground up:
- Pro Blog Levels!!!!!!!! And every optional module has full level support
- Coupons
- Permanent Pro Blog status switch
- Premium plugins/themes get removed on downgrades/cancelations
- Better stats
- Better blog management
- More customization/rebranding power
- Email notifications
- Every module spruced up and improved
- Front end checkout
- A new, incredibly powerful PayPal Express Checkout and Pro gateway:
Accept credit cards directly!
Allows modifications, level upgrades, payment plan changes, and cancelations by the user.
Powerful admin management: Process refunds, cancelations, partial refunds, and keep track of everything for the blog via a detailed audit log.
- And a whole lot more i've forgotten about!
So first off a warning, this is very early beta, and the plugin is so incredibly complex there's a good chance you may see the occassional php error, or a feature doens't work how it's supposed to. This is most true with the advanced checkout process, it has only had minimal (well days) of testing, but I need your help to work out the kinks.
So for now, please do not use on a live site unless it's real small and you can afford to work through problems your users experience.
Some things to know: - install in plugins and network activate
- remove all supporter files first
- Single payments are no longer supported, only subscriptions now (I may add them back later)
- The Amazon gateway no longer exists, it wasn't powerful enough for the levels and such (I may add it back if there is demand)
- If you have existing user subscriptions with the old paypal or Amazon gateways, make sure to copy the backwards compatibility IPN handlers to your webroot from the gateways folder.
I think that's it, please please test, and report bugs here so I can work them out.
Nice! Well done Aaron! Although I'd love to beta test, will have to wait for a stable release before installing this. Excited about the front end and levels, awesome!
I try to use supporter, have problems, and Aaron says, wait for this. I put up this beta and seems to more robust, and nice. Thanks
But I want to translate this (this is my previous problem) and this module have 663 strings to translate, but this found in 5 textdomain (default, mp, pm, wpmudev, pblgs), If i make a patch to all 663 string come from pblgs you will include this in this work early state? If not, i can't translate this, and i can't test this.
Thanks!
2227 pointsLike some sort of WPMU DEV GodExceptionally helpfulLifetime member
Lifetime member!
—
12th July 2011 (10 months ago)
#
mmmm loving it already.
But haumm... Where shall we enter the ads codes and set where they appear ? Did not found any place for that !
In adition, well... ^^ a racoon for moneybooker ;)
Oh yes some enhancement (simple) : the theme screenshot on setting up premium theme would be really a PLUS just essential. Setting premium themes on 400 themes without seeing them is just a mess ;)
Any chance of a option to have levels that includes only the themes and plugins assigned to that level, rather than also including all the plugins in the levels below.
For instance - I have a number of Genesis child themes available and it would be good if I could have a package that allowed anyone wanting access to the Genesis Level to be offered all the plugins that work specifically with Genesis themes. These plugins would then not be available to users with different themes, as they obviously can't be used.
It would also mean that you could create say an e-commerce package with just the themes and plugins needed for running an e-commerce site, rather than making this the highest level and giving the user access to all the plugins. Sometimes users need saving from themselves and it would be nice to never given them the option of activating all 200 plugins.
Also if I know that a plugin causes a problem with a particular theme or other plugin I can ensure that they are never in the same level.
jphogbin: hello! Your problem related to plugin files copied to mu-plugins dir. Remove all new or old supporter related files, or save other space. After this install this plugin via plugin manager upload.
But I want to translate this (this is my previous problem) and this module have 663 strings to translate, but this found in 5 textdomain (default, mp, pm, wpmudev, pblgs), If i make a patch to all 663 string come from pblgs you will include this in this work early state?
Ya, thanks for catching those. And thanks for the patch, will use it.
will any statistics feature,like as plug-in edublogs?
Yes, the stats are improved from the last version. I'll attach a screenshot in a bit.
But haumm... Where shall we enter the ads codes and set where they appear ? Did not found any place for that !
This is still in the separate supporter ads plugin. I think it will be good to merge them though, no?
In adition, well... ^^ a racoon for moneybooker ;)
Ya, more gateways are in the future, though I don't know of any with the power of paypal for backend management.
Oh yes some enhancement (simple) : the theme screenshot on setting up premium theme would be really a PLUS just essential. Setting premium themes on 400 themes without seeing them is just a mess ;)
Good idea.
I guess,have a bug,
when enable paypal Pro options once,can't disable.
Good catch, fixing up now.
Fatal error: Call to a member function get_page_permastruct() on a non-object in /home2/diycus/public_html/wp-includes/link-template.php on line 276
Does the error still appear when you save the settings?
1267 pointsLike some sort of WPMU DEV GodExceptionally helpfulLifetime member
Lifetime member!
—
12th July 2011 (10 months ago)
#
@wotacharlie:
For instance - I have a number of Genesis child themes available and it would be good if I could have a package that allowed anyone wanting access to the Genesis Level to be offered all the plugins that work specifically with Genesis themes. These plugins would then not be available to users with different themes, as they obviously can't be used.
I agree with your suggestion. However, in the case of Genesis, you can already do this yourself by including any desired Genesis plugins in the themes' functions.php files. This also has the benefit of not requiring users to activate the plugins because they're automatically there when the theme is activated.
I know, this isn't a substitute for what you suggested, but I just wanted to recommend it as a stopgap fix in case it helps.
Great work on the new version of the plug-in, looks good so far!! :D
One thing I am unsure about is sending users to a page on the main blog to manage/buy their subscriptions. I liked how the Supporter plug-in was all managed via the users own admin panel. Maybe an option depending on how it is required would be good.
In my case I am looking to get people creating their site on a free trial, then if they want to continue with their site after 30 days, they can set-up a subscription via their own admin panel.
Also I noticed you mention the 'Pay to Blog' in the above post, which is coming soon? What is this merging in with exactly? Any more details?
I have been playing around with a few of these plug-ins over the past couple of months and essentially what I am after is... the Pay to Blog functionality of being required to pay in order to have a site, but with a few more advanced features, such as recurring payments, X days free trial and site take-down if no payment is received.
One thing I am unsure about is sending users to a page on the main blog to manage/buy their subscriptions. I liked how the Supporter plug-in was all managed via the users own admin panel. Maybe an option depending on how it is required would be good.
This was done for 2 reasons, so that you could accept CC payments (SSL cert), and because it was highly requested.
Also I noticed you mention the 'Pay to Blog' in the above post, which is coming soon? What is this merging in with exactly? Any more details?
Basically just pulling in the functionality of Pay To Blog as a Pro Blog module, adding additional features such as disabling the front end.
I like the idea of rewriting all the plugins that currently work with Supporter, and simply making them modules. That way, once you have Pro Blogs set up, you can select modules if and when you require them. Also, if a single module causes a conflict with a theme/plugin, the problem can easily be found.
We have a "Pay to Blog" module that will be coming soon that will do this, we're merging the two plugins together.
A cool new feature though is that when they expire they will automatically be sent to the checkout untill they resubscribe or click the dismiss link.
Basically just pulling in the functionality of Pay To Blog as a Pro Blog module, adding additional features such as disabling the front end.
Thanks and congrats on the milestone. I've been "bugging" you guys about this for a while now and I gotta say thanks for listening. Definitely moving in the right direction with the Mods and keeping Pay to Blog!
+1 for merging supporter ads.
+1 for bringing back 1 time payment... lifetime subscriptions would require this no?
+1 for previews
Would it make sense to add the much requested "select template on signup" feature as a mod or something?
1267 pointsLike some sort of WPMU DEV GodExceptionally helpfulLifetime member
Lifetime member!
—
12th July 2011 (10 months ago)
#
A cool new feature though is that when they expire they will automatically be sent to the checkout untill they resubscribe or click the dismiss link.
Is this just for the admin area? If a blog is expired and someone tries to visit the front end, they shouldn't be directed to the payment/checkout page (because it's not their blog to pay for, of course).
I'd love to see the option to specify how the front end is disabled (redirect to a URL, or display a message, etc.).
I know that this might seem a detail... but my users won't make "blogs" and furthermore most of them will probably have no idea what a "blog" is. Please, would you like to consider finding a better and more "universal" name? (Pro? Pro account? ...)
Just a quick glance but I like this new version of supporter...I mean Pro Blogs. I have been trying to get the finishing touches on my site using Membership but after looking the Pro Blogs I might want to use it instead. I like the Pro Blogs setup and the ability to pick themes and plugins to give access to. The modules is a great idea and seems like a good way to expand Pro Blogs in the future.
I am wondering how it will integrate with the new Membership plugin? Is it possible to make it so that Pro Blogger can restrict content like Membership does? Maybe a way to drip content too?
I think for me it would be better if Pro Blogger integrated with Membership instead of the way it is now. Not sure if that's possible or something others might like.
I also didn't notice anything about giving the option for private blogs to supporters which I thought is an option on the previous version or is that going to be in an Upgrades module?
Are there any changes required to db-config.php for multi-db? I have deleted all the supporter files but would the references in db-config.php to Supporter cause any problems?
I don't know if it is possible, but it would be good if we could have it so that each level places the user on a different user role. That way, we can use the various plugins that work on user roles and those who are supporters will get extra functionality throughout the site.
Maybe this could be an option and if you didn't want to put in the funcuionality to create new user roles, those wanting it could create those themselves, and Pro Blogs can take advantage of that thrugh a simple drop-down menu for each level.
The membership plugin is good, but it is quite a monster fr those just wanting to set up something simple, and that would mean we wouldn't have to use it if we didn't want to.
Lorange: You can rename it to anything you want, so your users will see whatever you name it.
Yes, I know. But I think that my suggestion makes sense as a general good practice (can we say that in English?) and might be a "good idea" for everyone, not only for me. Since WP 3.0 the wording has changed and I think it should be a good rule (especially here) to avoid systematically restricting what we are doing to "blog" or "blogging".
I know that this might seem as a detail. But this is not.
Lorange - I see your point, I'll see if our marketing peeps prefer pro sites for the name. Note it's purely a marketing thing, as the actual name shown to your users is configurable.
Charles/Joe - I think you are still confused to how the plugin works. This is one of the reasons we are changing the name. Pro blog is user agnostic, status is tied to a site, not any user. So it doesn't make sense to have a connection to user roles, and you can't use it to limit content or access, only features for a site.
Jphog, the table names haven't changed so no multidb changes.
As to privacy, that's built into the privacy plugin, not.a pro blog module. A number of our plugins have these limits built into them, like marketpress, google analytics, domain mapping, etc.
thank you for this nice plugin! Love those new features very much!
But I have some problems.
Checkout in testmode does work well, but when I switch to life mode and click on checkout, I got just a site reload and nothing changes. As I get redirected in testmode to paypal, in live mode I don't see the paypal site at all.
Since WP 3.0 the wording has changed and I think it should be a good rule (especially here) to avoid systematically restricting what we are doing to "blog" or "blogging".
One of my biggest problems with BiuddyPress is that in the admin menu it says My Blogs & Create a Blog, but I want to call them websites at all times, move away from the whole thought of WP being used only for blogs.
I think you are still confused to how the plugin works. This is one of the reasons we are changing the name. Pro blog is user agnostic, status is tied to a site, not any user. So it doesn't make sense to have a connection to user roles, and you can't use it to limit content or access, only features for a site.
I think I have it now. Pro Blogs for sites, Membership for people.
None of the payment checkout options work for me, in fact I can't even get it to work in test bed. It just tries to load and then reloads the page over and over again.
Also, users can still create posts even though they are not 'pro members' and it explicitly says they cant. It says above the post they're editing or created "go pro to publish/edit posts" and then you can just edit them anyway.
Looks like it's off to membership land for me, or pay to blog.
+1 on the maintenance mode feature... I also see messages saying I need to become a pro member to write post and pages, but it's letting me anyway. and if I'm Super Admin then it shouldn't show message at all but it does.
Checkout in testmode does work well, but when I switch to life mode and click on checkout, I got just a site reload and nothing changes. As I get redirected in testmode to paypal, in live mode I don't see the paypal site at all.
Not sure what you mean by reload. If you have paypal pro checked and in live mode, you have to have an SSL cert or it will error out. You can use sandbox mode though without a cert.
Is that really what it said in the settings? It should have a wp-admin in there.
Also, users can still create posts even though they are not 'pro members' and it explicitly says they cant.
Just to check your not logged in as a super admin? And you can still create/edit posts, just not publish new ones. It takes away the publish permissions.
I was logged in as a subsite owner, not super admin. I will test the publishing abilities..
What are some of the minimum requirements to get paypal integration working?
I have the API username, pass, and signature added, and my paypal account is a paypal business account.
Yet Both Live/Testbed result in nonfunctioning checkout processes. Is there something special that has to be done for the testbed to work? (other than putting the plugin in testbed mode)
Yet Both Live/Testbed result in nonfunctioning checkout processes. Is there something special that has to be done for the testbed to work? (other than putting the plugin in testbed mode)
The credentials have to match your live or sandbox account, depending on what setting you have it at. ALso to do sandbox checkouts you have to be logged into the sandbox account I believe.
I'd like to confirm that yes, I can create both posts and pages (and publish them) as a site admin (not super admin) while it simultaneously is displaying that I have to become a supporter to publish posts.
edit: Tested by using a firefox browsing session logged out, while editing in a chrome session. Definitely not logged in in anyway and can still see the posts that were not supposed to be published.
For me at least, users aren't shown the option to signup for "Pro" when registering a new site, even if they mark "I'm interested". They can only process the upgrade after logging in and clicking on "Pro Blogs"
Well, it looks like reload, I click on checkout with paypal (express, I don't use Paypal Pro yet) and the site seems to relaod... finally it doesn't change anything.
Is there any log file?
If you have paypal pro checked and in live mode, you have to have an SSL cert or it will error out. You can use sandbox mode though without a cert.
I want use the express gateway. It does work in sandbox mode fore me (with a separate sandbox account) but I guess in testmode it doesn't use the IPN listener, does it?
I get no error messages, but quite a bit of on page problems with things being rendered oddly (breaks my site pretty much).
It's unique behavior to if a user is made using the pro blogs process or not.
if problogs is enabled but someone is NOT a supporter, and makes more than one SITE, there is no problems.
However, if someone becomes a user, registers a site, purchases their first Pro Blogs subscription, and then uses wp-signup to make an additional website under the same user account, it breaks the theme's display and moves elements around all over the place. I'll try to get a screenshot of it with a different theme.
As a note, it still creates the new site, and the next time I go to the Pro Blogs page it has it as a site that can be modified (and the process of upgrading both sites under one user account individually works great!)
Also, perhaps a little off topic.. But how do I clear out the purchases after I'm done testing? I don't have anything but test data so I dont care about losing "valid" data.
Not quite what I was getting at. I understand you can manually grant bulk upgrade credits by editing their blogs directly..
After you enable bulk upgrades you can set a paypal email address (rather than using your API key) and a paypal mode.
Payments are in 12 month increments ONLY either as a 1 time payment or as an annual payment.
What Pro Blog level credits will upgrade to.
Option 1 Settings Credits: Price: $
One credit allows for one blog to be upgraded for one year.
Option 2 Settings Credits: Price: $
One credit allows for one blog to be upgraded for one year.
Option 3 Settings Credits: Price: $
One credit allows for one blog to be upgraded for one year.
Option 4 Settings Credits: Price: $
One credit allows for one blog to be upgraded for one year.
The default checkout message is:
"You can upgrade multiple blogs at a lower cost by purchasing Pro Blog credits below. After purchasing your credits just come back to this page, search for your blogs via the tool at the bottom of the page, and upgrade them to Pro Blog status. Each blog is upgraded for one year."
This leads me to believe that this feature is intended to upgrade additional user sites to LEVELs, rather than the user doing another monthly subscription for each additional site after the typical signup process.
My confusion comes down to:
1) Why an annual subscription only?
2) Option 1 - 4. If they all do the same thing, why have 4? Am I Missing something? It does not make sense to me to have 4 prices for the same product.
The Bulk Upgrades module doesn't appear to be working using the sandbox, when I enter my sandbox merchant address into the email address field and go and try to make a credit purchase the page doesn't navigate anywhere, it just refreshes (on both subscribe and one time pay)
I see where you are coming from and hopefully we can clear some confusion up.
1. Why an annual subscription only?
To be honest, the demand for other options hasn't really been high enough to justify building other options in. If others would like to chime in it might be something to look at building into future versions.
In our experience (on Edublogs.org) the annual subscription is by far the most popular (around 90% of all subscriptions) so it just made sense to go with it.
The important thing to remember is that credits never expire, so if someone buys 5 credits, then they could use one each year for the next five years on the same blog over and over.
2. Option 1-4 - Why so many?
This is so you can set different prices for different numbers of credits.
Example:
Option 1 could be 5 blog credits for $10
Option 2 could be 10 blog credits for $13
Option 3 could be 20 blog credits for $20
That makes perfect sense. I can't believe I failed to take the credit discounts into account, since the purpose of the credits in the first place were to be a discount on top of the original pricing schema.
I think that the credits system could be quite powerful to have some granular control.
I was hoping to use it in this fashion:
1) User Makes a Blog, Goes Pro w/ Monthly Sub
2) User is interested in additional blogs. Registers more
3) Rather than setting up additional recurring payments, so long as User has 1) Recurring Montthly Pro Blog (primary blog), they could add Credits to their account to purchase Pro on a month by month credit basis for additional blogs. 1 credit = 1 month.
A year seems like a long time to offer something sometimes. Say a user needed a blog for a 3 month festival. They could start up a 3 month subscription, or just add some credits for 3 months (easily extendable if they need to carry it on longer).
I understand there's some overlap between the ideas, but I think it would have some potential. My .02 :) Keep up the great work guys! Looking forward to the bugs getting polished out of this so I can launch my site with it here in the next few weeks.
I agree with Kruzen that 1, 3 & 6 month options would be good to have.
One reason, si that not everybody has the money to pay a full year upfront and, to use one of the examples he gave, one of our sites is for indie film makers and a film festival may just want to set up a site for 3 months. Only having the option for an annual payment may cause them to go elsewhere for their site.
Just to make sure we are all clear, there is a monthly option (and others) built in for subscriptions.
What Kruzen and I were talking about only applies to bulk upgrade credits, which are an optional addition to the plugin that allow for discounts if you buy more than one subscription at a time. I agree month subscriptions that can be cancelled anytime do help get more people in the door! :)
1207 pointsLike some sort of WPMU DEV GodExceptionally helpfulLifetime member
Lifetime Member
—
18th July 2011 (10 months ago)
#
hello again :)
i set marketpress to auto-activate and i had to manually activate it on a sub-blog once it was upgraded to supporter.
and.. if someone registers and selects "i'm interested" and then they confirm their account... upon first login are they supposed to be redirected to http://mydomain.com/pro-blog/ - because when i tested it just now they are directed to mydomain.com on first login after confirming.
1207 pointsLike some sort of WPMU DEV GodExceptionally helpfulLifetime member
Lifetime Member
—
18th July 2011 (10 months ago)
#
hello,
chained payments works perfect...
but as far as paying for pro blog status... after i confirm email i click on dashboard.. it takes me to pro-blog subscription page.. i select a plan and click paypal payment button.. taken to paypal payment page.. enter password.. then i am taken back to the pro-blog subscription option page where it says:
There was a problem setting up the Paypal payment:
"A successful transaction has already been completed for this token."
Please try again.
i log in to the sandbox account used to pay and there is a successful payment made for one month but there is no subscription created on "preapproved payments" page where usually all subscription payment plans are listed.
then i try to go to the dash board and again it redirects to pro-blog subscription option pages.
and then when i go check on that site on admin dashboard it is not listed as a pro-blog.
Another interesting option for 'free trial' is what I'm doing. Limit posts/pages. They can still "preview" but cannot publish anything, so they can play with all of the features (and sign up for an account, so you can market to them until they buy!)
Does this new version support specific plugins/themes for each premium level? For example Plugin1 for Supporter level "1" and Plugin2 for Supporter level "2".
I think I am asking same question and sorry for that - but I haven't understood quite clearly - yes, those plugins and themes will auto-activate if they subscribe for higher level, but will some plugins auto deactivate too? (Some - which I will set)
While I appreciate that ETA's are often frowned upon, I would also like to know if there is even a general sense of when a stable version will be available?
It certainly seems from much of the feedback bugs and issues are being addressed fairly quickly?
ERROR:
Warning: Missing argument 2 for ProBlogs::page_title_output() in /home/mysite/public_html/wp-content/plugins/pro-blogs/pro-blogs.php on line 1168
SUGGESTION:
Would be nice to be able to sort plans so that cheaper plans appear at top.
SUGGESTION:
Move coupon code field right above plans - Due to the flow once coupon is applied (message appears at top of plans indicating that coupon has been applied) This is much more friendly for end users as they see instantly that coupon worked and then can scroll down through plans - it might even compel them to subscribe to a higher plan since they have already seen the coupon applied.
SUGGESTION:
Center payment information/links under plans
SUGGESTION:
Add message above plans instructing user to click desired plan 'and' then click the payment link. This may seem obvious but it actually too me a few clicks of the plan info to realize it wasn't going to redirect me automatically and then I realized clicking the plan was just a highlight function and you need to click payment link below.
ERROR:
When clicking the PayPal link after applying coupon code and selecting plan, I'm directed back to the 'plans' page I was just on instead of paypal. Double checked all paypal IPN and API details and everything seems okay. I will continue to test the paypal process once this issue is resolved.
My biggest worry is the payment API, which so far only Gina seems to be testing ;-) Especially refunds, upgrades, downgrades, etc.
I'd like to test very much, but here isn't any popular payment ways in Georgia yet. Even PayPal is planned to be available in August.
---
Aaron, I think I haven't explained in correct way what I was asking you yesterday.
So, it's good that if User upgrades package from 1 to 2, (s)he will have activated all plugins, plugins for 1 package and plugins for 2 package.
And so - if (s)he downgrades from 2 to 1, plugins for 2 package will be deactivated and there will be left only package 1 plugins.
But I am asking something different - Will I be able to assign only plugins package 3 will have?
For example (this example will clarify everything I think):
There will be 3 packages:
1) First will be free and it'll be for blogs.
2) Second will be paid and it'll be for blogs too (with more functions and themes, which will be auto-activated).
3) Third will be paid and it'll be for e-Shops (with MarketPress & FrameMarket). So this is what I am asking: If user purchases this package, it's quite clear that this user doesn't need standard blog features, for example - Auto Blog (which second package has).
So yes, it's good that if user upgrades, it will auto-activate some themes and plugins for him, but will it be possible to DE-activate too?
---
I'll make another example - The last stable version of Supporter has premium plugins feature you know, and when admin clicks on it, it shows page, where admin can assign which plugin will be accessible for None, Everyone, Premium.... So, now I think it will be like this - None, Everyone, Premium, Premium1, Premium2... Am I right?
So, If I select MarketPress plugin for Premium2 and Auto-Blog for Premium 1, this means that Premium 2 will have both of them - MarketPress and Auto-Blog? If this is so it's bad for me, as user, who uses MarketPress, doesn't need AutoBlog.
This is what I am asking if it is possible. If it isn't take it as my suggestion please, as there is lot time before stable version comes out (Aug, as you said).
1207 pointsLike some sort of WPMU DEV GodExceptionally helpfulLifetime member
Lifetime Member
—
21st July 2011 (10 months ago)
#
Keshingelia,
Using your example.. Yes your level 3 would have access to plugins available to level 2...like Aaron said they are additive. Your level 3 would have access to autoblog (which they can always deactivate and not use) but maybe they would want to use this feature. I know I would on my ecommerce site.
I actually prefer they stair-step way it is set up now where users (via levels) gain access to more and more features.
Thanks Gina, but that's something which I already know (Aaron told me). I am very sorry because I can't explain exactly because of my English (maybe).
So this is last try:
Your level 3 would have access to autoblog (which they can always deactivate and not use)
You said "which they can always deactivate and not use". I have marked with bold important part - "can", but is it possible that those plugins were auto-DE-activated and users still have possibilty to activate them.
So you say that (and I know that) when user upgrades to higher level, he will have access to plugins and themes those level offers him and lower levels too.
But my question is - Yes, it's very good that higher package offers users features of lower packages too, but is it possible to offer them those plugins/themes in "Deactivated" way? So that yes, user will have access to them, but they will be deactivated as default.
So the conclusion is that:
NOT - Users will be able to deactivate plugins they don't need, but
YES - Users will be activate plugins they need
---
It seems to be very little difference between those sentences, but I think you understand now, I have tried my best to explain it :)
Wondering if you are testing pro-blogs-3-beta-2 and if so, did you expereience any issues with being directed back to the 'plans' page after clicking the Checkout With PayPal link instead of the paypal page?
I have double checked all paypal IPN and API details and everything seems okay.
kshengelia, the difference is autoactivating or just having access to. When upgrading to a higher level, only the plugins for the new level will be activated if you have checked them to. So if they go from free to level 3, only level 3 plugins will be autoactivated, though they will still have access to level 2 plugins.
kshengelia, the difference is autoactivating or just having access to. When upgrading to a higher level, only the plugins for the new level will be activated if you have checked them to. So if they go from free to level 3, only level 3 plugins will be autoactivated, though they will still have access to level 2 plugins.
Ok, that's exactly what I wanted to hear from you, thanks thanks!
So am I to understand that even though you were having the redirect issue we discussed earlier you were able to eventually get to the paypal checkout page?
If so how did you bypass the issue of redirection to the plans page?
I'm hoping to test some of the paypal features as requested by Aaron (refunds, upgrades, downgrades, etc.)
1207 pointsLike some sort of WPMU DEV GodExceptionally helpfulLifetime member
Lifetime Member
—
22nd July 2011 (10 months ago)
#
yes i get to the paypal page to enter account info to authorize payment but after putting in password it takes me back to the pro blogs page with that error.
1207 pointsLike some sort of WPMU DEV GodExceptionally helpfulLifetime member
Lifetime Member
—
22nd July 2011 (10 months ago)
#
i was reading another developers site for a plugin in which a user was getting the same paypal error i am getting and he said "some plugins or site settings can cause the hooks which call the plugin functions to be called multiple times from within a single WordPress request."
that could be. I havn't had a chance to look into the billings stuff at all yet, so it could very well be completely nonfuncitonal (though was working on my test site before beta). Patience guys ;-)
2227 pointsLike some sort of WPMU DEV GodExceptionally helpfulLifetime member
Lifetime member!
—
24th July 2011 (10 months ago)
#
well a little out of purpose but still related, concerning ads.
When you'll dev the adds insertion plugin, remind a detail : many themes allows to add the featured image on pages/post.
Would need to insert ads BEFORE the thumb, if not page / post layout is just weird.
Ad block ads isertion on home pages and archive pages using the excerpt thing....
I like some of the new features! Especially the coupons and easier management of the premium plugins and themes. Looks like a lot of work has been going into this. I'd drop the blog out of 'pro-blog' though and just leave it at 'pro'.
One thing I was really surprised and very disappointed to to see left out was the trial period...that feature alone equates to thousands of dollars when you compare the conversion rates. It really is a no brainer to have that simple option added in there when it comes to subscriptions if you want to see loads of signups when you run a 'Free Trial' campaign.
I did find a bug on being redirected back to my page when trying to make a paypal payment and yes, the api settings were all in. Not sure what happened there but I guess I'm not the only one with that issue.
The plan graphics leave much to be desired, the little square thing going on for the pricing could be worked on, it might be best to take a minimalistic approach so that it blends in well with any theme.
Overall I do like the new version so far and really hope to see what the final outcome is after the dust has settled. Hopefully the trial option gets back in there where it belongs too! ;)
i had simple question. would it be possible to have multiple free levels, and then be able to upgrade those levels. or simply would be able to have free levels without upgrading
hey
for the different levels of supporter, could each have a one time payment instead of subscription? or is the one time payment only avaliable for the pay to blog (which i think is an awesome feature)
Hey all, thank you so much for your bug reports and testing, I've got a good list to go on. Unfortunately I've run out if time before my scheduled vacation, so need to put those on hold for a bit.
Rest assured that as soon as I get back aug 8th I'll be finishing this as a top priority. We're trying to get this live on Edublogs before the school year starts.
So until then, I'm gonna unstick this and open a new thread when I put up beta 3. Thanks again for your help and patience!
I have installed the Pro-Blogs plugin and looks great. Please also add manual payment as a gateway. I don't think much person in my community in Indonesia having paypal account. Or would be great functionally if the admin can setup local payment gateway, I don't know would be doable or not.
Cheers.
Fatal error: Call to a member function get_page_permastruct() on a non-object in home/agric/public_html/wp-includes/link-template.php on line 276
This happened when I went to add a second level of payment. Backed up and tried again. This time it took out my admin panel. Had to rename the plugin folder and recover.
I believe I found what is happening. I reloaded the plugin (several times) to troubleshoot. Found I can set up levels but if I change the Pro Blog Setting to rebrand the plugin as anything other than Pro Blogs, it causes the fatal error. Might be tied to having more than one level and rebranding.
Responses (143)
Member — 12th July 2011 (10 months ago) #
Looks like I'm the first to say it... thank you, thank you, THANK YOU!
Member — 12th July 2011 (10 months ago) #
Nice! Well done Aaron! Although I'd love to beta test, will have to wait for a stable release before installing this. Excited about the front end and levels, awesome!
Member — 12th July 2011 (10 months ago) #
Thanks Aaron....had something waiting for this so will start testing now :)
Member — 12th July 2011 (10 months ago) #
Sorry, i post to fast... Module is working, please read instalation instructions!
Member — 12th July 2011 (10 months ago) #
Hello,
I try to use supporter, have problems, and Aaron says, wait for this. I put up this beta and seems to more robust, and nice. Thanks
But I want to translate this (this is my previous problem) and this module have 663 strings to translate, but this found in 5 textdomain (default, mp, pm, wpmudev, pblgs), If i make a patch to all 663 string come from pblgs you will include this in this work early state? If not, i can't translate this, and i can't test this.
Thanks!
Member — 12th July 2011 (10 months ago) #
BTW: patch is here: http://www.dds.hu/patches/wpmu/problogs_textdomain.patch
Member — 12th July 2011 (10 months ago) #
Thank you so much! Credit card is a nice feature!
I think the Pro blogs is a better name than supporter :)
Lifetime Member — 12th July 2011 (10 months ago) #
Great! and working fine.
will any statistics feature,like as plug-in edublogs?
Lifetime member! — 12th July 2011 (10 months ago) #
mmmm loving it already.
But haumm... Where shall we enter the ads codes and set where they appear ? Did not found any place for that !
In adition, well... ^^ a racoon for moneybooker ;)
Oh yes some enhancement (simple) : the theme screenshot on setting up premium theme would be really a PLUS just essential. Setting premium themes on 400 themes without seeing them is just a mess ;)
Lifetime Member — 12th July 2011 (10 months ago) #
I guess,have a bug,
when enable paypal Pro options once,can't disable.
Member — 12th July 2011 (10 months ago) #
I can activate ok but as soon as I go to the settings page I get this error:
Fatal error: Call to a member function get_page_permastruct() on a non-object in /home2/diycus/public_html/wp-includes/link-template.php on line 276
Member — 12th July 2011 (10 months ago) #
Any chance of a option to have levels that includes only the themes and plugins assigned to that level, rather than also including all the plugins in the levels below.
For instance - I have a number of Genesis child themes available and it would be good if I could have a package that allowed anyone wanting access to the Genesis Level to be offered all the plugins that work specifically with Genesis themes. These plugins would then not be available to users with different themes, as they obviously can't be used.
It would also mean that you could create say an e-commerce package with just the themes and plugins needed for running an e-commerce site, rather than making this the highest level and giving the user access to all the plugins. Sometimes users need saving from themselves and it would be nice to never given them the option of activating all 200 plugins.
Also if I know that a plugin causes a problem with a particular theme or other plugin I can ensure that they are never in the same level.
Lifetime member! — 12th July 2011 (10 months ago) #
mmm If I understand quite privative levels, in fact package instead levels hum ?
Means that pack "ecommerce" will activate some things, pack "cms" others things but not as "levels", without activating the other themes/plugins ?
mmmmm Yes, that is good....
Package instead level didnt thought about that way !
Could be an option in settings : packs or levels !
+1 !
Member — 12th July 2011 (10 months ago) #
jphogbin: hello! Your problem related to plugin files copied to mu-plugins dir. Remove all new or old supporter related files, or save other space. After this install this plugin via plugin manager upload.
Lead Developer — 12th July 2011 (10 months ago) #
Ya, thanks for catching those. And thanks for the patch, will use it.
Yes, the stats are improved from the last version. I'll attach a screenshot in a bit.
This is still in the separate supporter ads plugin. I think it will be good to merge them though, no?
Ya, more gateways are in the future, though I don't know of any with the power of paypal for backend management.
Good idea.
Good catch, fixing up now.
Does the error still appear when you save the settings?
Lead Developer — 12th July 2011 (10 months ago) #
That's and interesting idea. It would require another complete rewrite though, so will have to hold off on that for a bit...
Lead Developer — 12th July 2011 (10 months ago) #
Here are some screenshots as well:
Lifetime member! — 12th July 2011 (10 months ago) #
@wotacharlie:
I agree with your suggestion. However, in the case of Genesis, you can already do this yourself by including any desired Genesis plugins in the themes' functions.php files. This also has the benefit of not requiring users to activate the plugins because they're automatically there when the theme is activated.
I know, this isn't a substitute for what you suggested, but I just wanted to recommend it as a stopgap fix in case it helps.
Mark
Lifetime member! — 12th July 2011 (10 months ago) #
I haven't tried it yet, but I'm wondering:
Is there a function to block access to the front end if a blog is unpaid (preferably with a grace period and a configurable page for blocked sites)?
Also, can this restrict access to the Dashboard until a user signs up for a paid plan?
Lead Developer — 12th July 2011 (10 months ago) #
We have a "Pay to Blog" module that will be coming soon that will do this, we're merging the two plugins together.
A cool new feature though is that when they expire they will automatically be sent to the checkout untill they resubscribe or click the dismiss link.
Member — 12th July 2011 (10 months ago) #
Hey Aaron,
Great work on the new version of the plug-in, looks good so far!! :D
One thing I am unsure about is sending users to a page on the main blog to manage/buy their subscriptions. I liked how the Supporter plug-in was all managed via the users own admin panel. Maybe an option depending on how it is required would be good.
In my case I am looking to get people creating their site on a free trial, then if they want to continue with their site after 30 days, they can set-up a subscription via their own admin panel.
Also I noticed you mention the 'Pay to Blog' in the above post, which is coming soon? What is this merging in with exactly? Any more details?
I have been playing around with a few of these plug-ins over the past couple of months and essentially what I am after is... the Pay to Blog functionality of being required to pay in order to have a site, but with a few more advanced features, such as recurring payments, X days free trial and site take-down if no payment is received.
Thanks! :)
Lead Developer — 12th July 2011 (10 months ago) #
This was done for 2 reasons, so that you could accept CC payments (SSL cert), and because it was highly requested.
Basically just pulling in the functionality of Pay To Blog as a Pro Blog module, adding additional features such as disabling the front end.
Member — 12th July 2011 (10 months ago) #
Brilliant. I eagerly await! :)
Member — 12th July 2011 (10 months ago) #
I like the idea of rewriting all the plugins that currently work with Supporter, and simply making them modules. That way, once you have Pro Blogs set up, you can select modules if and when you require them. Also, if a single module causes a conflict with a theme/plugin, the problem can easily be found.
Lifetime member! — 12th July 2011 (10 months ago) #
ok for ads inclusion. The "pro blog advertising" will go out soon so ?
Remember that auto excerpt thing and have a look on ads inserter that works just fine....
Member — 12th July 2011 (10 months ago) #
Thanks and congrats on the milestone. I've been "bugging" you guys about this for a while now and I gotta say thanks for listening. Definitely moving in the right direction with the Mods and keeping Pay to Blog!
+1 for merging supporter ads.
+1 for bringing back 1 time payment... lifetime subscriptions would require this no?
+1 for previews
Would it make sense to add the much requested "select template on signup" feature as a mod or something?
I'm off to test!
Lifetime member! — 12th July 2011 (10 months ago) #
Is this just for the admin area? If a blog is expired and someone tries to visit the front end, they shouldn't be directed to the payment/checkout page (because it's not their blog to pay for, of course).
I'd love to see the option to specify how the front end is disabled (redirect to a URL, or display a message, etc.).
Member — 12th July 2011 (10 months ago) #
Hey this a great announcement!
I know that this might seem a detail... but my users won't make "blogs" and furthermore most of them will probably have no idea what a "blog" is. Please, would you like to consider finding a better and more "universal" name? (Pro? Pro account? ...)
Member — 12th July 2011 (10 months ago) #
Lorange: You can rename it to anything you want, so your users will see whatever you name it.
Member — 13th July 2011 (10 months ago) #
Just a quick glance but I like this new version of supporter...I mean Pro Blogs. I have been trying to get the finishing touches on my site using Membership but after looking the Pro Blogs I might want to use it instead. I like the Pro Blogs setup and the ability to pick themes and plugins to give access to. The modules is a great idea and seems like a good way to expand Pro Blogs in the future.
I am wondering how it will integrate with the new Membership plugin? Is it possible to make it so that Pro Blogger can restrict content like Membership does? Maybe a way to drip content too?
I think for me it would be better if Pro Blogger integrated with Membership instead of the way it is now. Not sure if that's possible or something others might like.
I also didn't notice anything about giving the option for private blogs to supporters which I thought is an option on the previous version or is that going to be in an Upgrades module?
Member — 13th July 2011 (10 months ago) #
Are there any changes required to db-config.php for multi-db? I have deleted all the supporter files but would the references in db-config.php to Supporter cause any problems?
Thanks,
J-P
Member — 13th July 2011 (10 months ago) #
I don't know if it is possible, but it would be good if we could have it so that each level places the user on a different user role. That way, we can use the various plugins that work on user roles and those who are supporters will get extra functionality throughout the site.
Maybe this could be an option and if you didn't want to put in the funcuionality to create new user roles, those wanting it could create those themselves, and Pro Blogs can take advantage of that thrugh a simple drop-down menu for each level.
The membership plugin is good, but it is quite a monster fr those just wanting to set up something simple, and that would mean we wouldn't have to use it if we didn't want to.
Member — 13th July 2011 (10 months ago) #
Yes, I know. But I think that my suggestion makes sense as a general good practice (can we say that in English?) and might be a "good idea" for everyone, not only for me. Since WP 3.0 the wording has changed and I think it should be a good rule (especially here) to avoid systematically restricting what we are doing to "blog" or "blogging".
I know that this might seem as a detail. But this is not.
I hope this simple suggestion will be considered.
Lead Developer — 13th July 2011 (10 months ago) #
Lorange - I see your point, I'll see if our marketing peeps prefer pro sites for the name. Note it's purely a marketing thing, as the actual name shown to your users is configurable.
Charles/Joe - I think you are still confused to how the plugin works. This is one of the reasons we are changing the name. Pro blog is user agnostic, status is tied to a site, not any user. So it doesn't make sense to have a connection to user roles, and you can't use it to limit content or access, only features for a site.
Jphog, the table names haven't changed so no multidb changes.
As to privacy, that's built into the privacy plugin, not.a pro blog module. A number of our plugins have these limits built into them, like marketpress, google analytics, domain mapping, etc.
Member — 13th July 2011 (10 months ago) #
Hi Aaron,
thank you for this nice plugin! Love those new features very much!
But I have some problems.
Checkout in testmode does work well, but when I switch to life mode and click on checkout, I got just a site reload and nothing changes. As I get redirected in testmode to paypal, in live mode I don't see the paypal site at all.
What's wrong?
Btw: is the IPN Url correct? It says http://mydomain.com/admin-ajax.php?action=pblgs_pypl_ipn
Seems strange, as this file doesn't exist (it is in the folder wp-admin) so shouldn't it be
http://mydomain.com/wp-admin/admin-ajax.php?action=pblgs_pypl_ipn ?
I checked this with paypay sandbox and it responded "Okay" So I tried a transaction with the IPN http://mydomain.com/wp-admin/admin-ajax.php?action=pblgs_pypl_ipn, but still no success
Any idea?
Thank you
Dorina
Member — 13th July 2011 (10 months ago) #
One of my biggest problems with BiuddyPress is that in the admin menu it says My Blogs & Create a Blog, but I want to call them websites at all times, move away from the whole thought of WP being used only for blogs.
I think I have it now. Pro Blogs for sites, Membership for people.
Lifetime Member — 13th July 2011 (10 months ago) #
How about having the site/blog automatically put to maintenance mode.
Member — 13th July 2011 (10 months ago) #
Thanks for clearing that up Aaron. After your explanation it seems I was using the wrong plugin for what I am trying to accomplish with my site.
Member — 13th July 2011 (10 months ago) #
I have the same problems as gdharre,
None of the payment checkout options work for me, in fact I can't even get it to work in test bed. It just tries to load and then reloads the page over and over again.
Also, users can still create posts even though they are not 'pro members' and it explicitly says they cant. It says above the post they're editing or created "go pro to publish/edit posts" and then you can just edit them anyway.
Looks like it's off to membership land for me, or pay to blog.
Member — 13th July 2011 (10 months ago) #
+1 on the maintenance mode feature... I also see messages saying I need to become a pro member to write post and pages, but it's letting me anyway. and if I'm Super Admin then it shouldn't show message at all but it does.
Lead Developer — 13th July 2011 (10 months ago) #
Not sure what you mean by reload. If you have paypal pro checked and in live mode, you have to have an SSL cert or it will error out. You can use sandbox mode though without a cert.
Is that really what it said in the settings? It should have a wp-admin in there.
Just to check your not logged in as a super admin? And you can still create/edit posts, just not publish new ones. It takes away the publish permissions.
Member — 13th July 2011 (10 months ago) #
I have the same path to the IPN.
I was logged in as a subsite owner, not super admin. I will test the publishing abilities..
What are some of the minimum requirements to get paypal integration working?
I have the API username, pass, and signature added, and my paypal account is a paypal business account.
Yet Both Live/Testbed result in nonfunctioning checkout processes. Is there something special that has to be done for the testbed to work? (other than putting the plugin in testbed mode)
Lead Developer — 13th July 2011 (10 months ago) #
I'll fix up the IPN.
Yet Both Live/Testbed result in nonfunctioning checkout processes. Is there something special that has to be done for the testbed to work? (other than putting the plugin in testbed mode)
The credentials have to match your live or sandbox account, depending on what setting you have it at. ALso to do sandbox checkouts you have to be logged into the sandbox account I believe.
Member — 13th July 2011 (10 months ago) #
Thanks Aaron, The IPN is probably my live problem, and the credentials are probably my testbed problem :p
Member — 13th July 2011 (10 months ago) #
I'd like to confirm that yes, I can create both posts and pages (and publish them) as a site admin (not super admin) while it simultaneously is displaying that I have to become a supporter to publish posts.
edit: Tested by using a firefox browsing session logged out, while editing in a chrome session. Definitely not logged in in anyway and can still see the posts that were not supposed to be published.
Member — 13th July 2011 (10 months ago) #
Another thing.
For me at least, users aren't shown the option to signup for "Pro" when registering a new site, even if they mark "I'm interested". They can only process the upgrade after logging in and clicking on "Pro Blogs"
Member — 13th July 2011 (10 months ago) #
Okay.. some small corrections.
Somehow the options got unchecked.
Publishing IS being withheld for normal accounts.
The only issue's i've come across so far is the registration issue and the IPN.
Member — 14th July 2011 (10 months ago) #
Well, it looks like reload, I click on checkout with paypal (express, I don't use Paypal Pro yet) and the site seems to relaod... finally it doesn't change anything.
Is there any log file?
I want use the express gateway. It does work in sandbox mode fore me (with a separate sandbox account) but I guess in testmode it doesn't use the IPN listener, does it?
regards
Dorina
Member — 14th July 2011 (10 months ago) #
Another bug..
I get no error messages, but quite a bit of on page problems with things being rendered oddly (breaks my site pretty much).
It's unique behavior to if a user is made using the pro blogs process or not.
if problogs is enabled but someone is NOT a supporter, and makes more than one SITE, there is no problems.
However, if someone becomes a user, registers a site, purchases their first Pro Blogs subscription, and then uses wp-signup to make an additional website under the same user account, it breaks the theme's display and moves elements around all over the place. I'll try to get a screenshot of it with a different theme.
As a note, it still creates the new site, and the next time I go to the Pro Blogs page it has it as a site that can be modified (and the process of upgrading both sites under one user account individually works great!)
Member — 14th July 2011 (10 months ago) #
Here's the break I'm talking about using Twenty Eleven as the theme.
Member — 14th July 2011 (10 months ago) #
Also, perhaps a little off topic.. But how do I clear out the purchases after I'm done testing? I don't have anything but test data so I dont care about losing "valid" data.
Member — 14th July 2011 (10 months ago) #
Can someone expand on the Bulk Upgrades feature and how it works? It looks like it's not quite developed out all the way yet.
Member — 15th July 2011 (10 months ago) #
Hi @Kruzen,
There's an area to extend and remove the subscription in the network admin "Pro Blogs" section. you'll use the ID of the blog I believe.
Member — 15th July 2011 (10 months ago) #
Hi Wecreateyou,
Not quite what I was getting at. I understand you can manually grant bulk upgrade credits by editing their blogs directly..
After you enable bulk upgrades you can set a paypal email address (rather than using your API key) and a paypal mode.
Payments are in 12 month increments ONLY either as a 1 time payment or as an annual payment.
What Pro Blog level credits will upgrade to.
Option 1 Settings Credits: Price: $
One credit allows for one blog to be upgraded for one year.
Option 2 Settings Credits: Price: $
One credit allows for one blog to be upgraded for one year.
Option 3 Settings Credits: Price: $
One credit allows for one blog to be upgraded for one year.
Option 4 Settings Credits: Price: $
One credit allows for one blog to be upgraded for one year.
The default checkout message is:
"You can upgrade multiple blogs at a lower cost by purchasing Pro Blog credits below. After purchasing your credits just come back to this page, search for your blogs via the tool at the bottom of the page, and upgrade them to Pro Blog status. Each blog is upgraded for one year."
This leads me to believe that this feature is intended to upgrade additional user sites to LEVELs, rather than the user doing another monthly subscription for each additional site after the typical signup process.
My confusion comes down to:
1) Why an annual subscription only?
2) Option 1 - 4. If they all do the same thing, why have 4? Am I Missing something? It does not make sense to me to have 4 prices for the same product.
Member — 15th July 2011 (10 months ago) #
Ya'll are probably getting sick of me by now :)
The Bulk Upgrades module doesn't appear to be working using the sandbox, when I enter my sandbox merchant address into the email address field and go and try to make a credit purchase the page doesn't navigate anywhere, it just refreshes (on both subscribe and one time pay)
Member — 15th July 2011 (10 months ago) #
Hi Kruzen,
I see where you are coming from and hopefully we can clear some confusion up.
1. Why an annual subscription only?
To be honest, the demand for other options hasn't really been high enough to justify building other options in. If others would like to chime in it might be something to look at building into future versions.
In our experience (on Edublogs.org) the annual subscription is by far the most popular (around 90% of all subscriptions) so it just made sense to go with it.
The important thing to remember is that credits never expire, so if someone buys 5 credits, then they could use one each year for the next five years on the same blog over and over.
2. Option 1-4 - Why so many?
This is so you can set different prices for different numbers of credits.
Example:
Option 1 could be 5 blog credits for $10
Option 2 could be 10 blog credits for $13
Option 3 could be 20 blog credits for $20
Or however you would like to set it up.
Does that help?
Member — 15th July 2011 (10 months ago) #
Ah yes Ronnie,
That makes perfect sense. I can't believe I failed to take the credit discounts into account, since the purpose of the credits in the first place were to be a discount on top of the original pricing schema.
I think that the credits system could be quite powerful to have some granular control.
I was hoping to use it in this fashion:
1) User Makes a Blog, Goes Pro w/ Monthly Sub
2) User is interested in additional blogs. Registers more
3) Rather than setting up additional recurring payments, so long as User has 1) Recurring Montthly Pro Blog (primary blog), they could add Credits to their account to purchase Pro on a month by month credit basis for additional blogs. 1 credit = 1 month.
A year seems like a long time to offer something sometimes. Say a user needed a blog for a 3 month festival. They could start up a 3 month subscription, or just add some credits for 3 months (easily extendable if they need to carry it on longer).
I understand there's some overlap between the ideas, but I think it would have some potential. My .02 :) Keep up the great work guys! Looking forward to the bugs getting polished out of this so I can launch my site with it here in the next few weeks.
Member — 15th July 2011 (10 months ago) #
I agree with Kruzen that 1, 3 & 6 month options would be good to have.
One reason, si that not everybody has the money to pay a full year upfront and, to use one of the examples he gave, one of our sites is for indie film makers and a film festival may just want to set up a site for 3 months. Only having the option for an annual payment may cause them to go elsewhere for their site.
Member — 15th July 2011 (10 months ago) #
It would be nice to have the month to month/cancel anytime option for subscriptions. Annual commitments scare people off, especially on new sites.
Member — 15th July 2011 (10 months ago) #
Hi Joe and trykd,
Just to make sure we are all clear, there is a monthly option (and others) built in for subscriptions.
What Kruzen and I were talking about only applies to bulk upgrade credits, which are an optional addition to the plugin that allow for discounts if you buy more than one subscription at a time. I agree month subscriptions that can be cancelled anytime do help get more people in the door! :)
Ronnie
Member — 15th July 2011 (10 months ago) #
no problem then :0) That makes sense to be annual, as it offers a discount.
Member — 15th July 2011 (10 months ago) #
Install question: install in plugins and not mu-plugins like the old supporter?
Member — 15th July 2011 (10 months ago) #
Hi trykd,
Correct in plugins and network activate. :)
Member — 16th July 2011 (10 months ago) #
AAAA :))))
I was so waiting for this
Thank you very much! I'll notify you about bugs if I find.
Can you tell me when full version will come out (only approximate date) - two days, two weeks or?
Thanks!
Lifetime Member — 16th July 2011 (10 months ago) #
any way to disable PayPal Pro in the meantime?
thanks
gina
Member — 16th July 2011 (10 months ago) #
@Gina,
You can disable paypal pro in the settings as network superuser
Lifetime Member — 16th July 2011 (10 months ago) #
@kruzen
thanks but it's a bug...once you enable it.. you can't disable it..
:)
gina
Lead Developer — 16th July 2011 (10 months ago) #
Ah yes, I've fixed it but havnt had a chance to upload the next beta yet. Monday...
Lifetime Member — 16th July 2011 (10 months ago) #
ok awesome :) looks great aaron.
gina
Lifetime Member — 18th July 2011 (10 months ago) #
hi aaron :)
just wondering if we should still be expecting that upload today with the changes?
thanks... loving this new version.
gina
Lifetime Member — 18th July 2011 (10 months ago) #
hello again :)
i set marketpress to auto-activate and i had to manually activate it on a sub-blog once it was upgraded to supporter.
and.. if someone registers and selects "i'm interested" and then they confirm their account... upon first login are they supposed to be redirected to http://mydomain.com/pro-blog/ - because when i tested it just now they are directed to mydomain.com on first login after confirming.
thanks :)
gina
Lead Developer — 18th July 2011 (10 months ago) #
Ok, here is beta 2, with ipn url fix, textdomains patched, and settings checkboxes fixed.
Also it reenables the checkout redirect on first signup and when they loose supporter features.
Member — 18th July 2011 (10 months ago) #
Thanks Aaron! checking out now!
Member — 18th July 2011 (10 months ago) #
Aaron,
Was the break on signing up for a secondary site fixed?
Lifetime Member — 18th July 2011 (10 months ago) #
Great. Thanks. Checking it out. :)
Member — 18th July 2011 (10 months ago) #
Looks like the break on signing up for a secondary site is still not fixed. FYI
Lifetime Member — 18th July 2011 (10 months ago) #
hello,
chained payments works perfect...
but as far as paying for pro blog status... after i confirm email i click on dashboard.. it takes me to pro-blog subscription page.. i select a plan and click paypal payment button.. taken to paypal payment page.. enter password.. then i am taken back to the pro-blog subscription option page where it says:
There was a problem setting up the Paypal payment:
"A successful transaction has already been completed for this token."
Please try again.
i log in to the sandbox account used to pay and there is a successful payment made for one month but there is no subscription created on "preapproved payments" page where usually all subscription payment plans are listed.
then i try to go to the dash board and again it redirects to pro-blog subscription option pages.
and then when i go check on that site on admin dashboard it is not listed as a pro-blog.
gina
Lifetime Member — 19th July 2011 (10 months ago) #
i cleared cache and tried again and got this:
There was a problem setting up the Paypal payment:
"You have exceeded the maximum number of payment attempts for this token."
Please try again.
but the with the tokens the PayerID matched but the EC- part of it did not match.
gina
Lead Developer — 19th July 2011 (10 months ago) #
Hey guys, thanks for the continued bug reports. I'll keep sorting through them.
Lifetime Member — 19th July 2011 (10 months ago) #
am i suffering from lack of sleep or just blind? can we do a free trial with pro blogs?
thanks :)
gina
Lead Developer — 19th July 2011 (10 months ago) #
Not currently, the old one was so screwed up. What I was thinking is giving the ability to assign level 1 as a trial level.
Ultimately it would be best to include the trial as an actual PayPal checkout, so they have to cancel the trial to avoid being charged.
Lifetime Member — 19th July 2011 (10 months ago) #
Ok. I thought I was losing it haha.
Ya that would be perfect to have the trial as an actual PayPal checkout.
Thanks Aaron
Member — 19th July 2011 (10 months ago) #
Gina,
Another interesting option for 'free trial' is what I'm doing. Limit posts/pages. They can still "preview" but cannot publish anything, so they can play with all of the features (and sign up for an account, so you can market to them until they buy!)
Lifetime Member — 19th July 2011 (10 months ago) #
Ya.. I was thinking something morevalong the lines of free trial with an ad supported website and limited features.
Thanks :)
Gina
Member — 19th July 2011 (10 months ago) #
On the topic of coupons. Do these function over the course of the entire subscription or just on the first payment?
Lead Developer — 19th July 2011 (10 months ago) #
First payment only.
Lifetime Member — 20th July 2011 (10 months ago) #
hi aaron,
just wondering if the errors i am getting [see: http://premium.wpmudev.org/forums/topic/supporter-30-beta-release-help-us-test#post-114115 is a bug or something i set up wrong?
thanks,
gina
Lead Developer — 20th July 2011 (10 months ago) #
I haven't had a chance to test.
Lifetime Member — 20th July 2011 (10 months ago) #
ok. thanks.
i have my site set up with sandbox accounts if you want to test mine to see what i mean. http://goo.gl/IHNxl
gina
Member — 20th July 2011 (10 months ago) #
Hi,
Does this new version support specific plugins/themes for each premium level? For example Plugin1 for Supporter level "1" and Plugin2 for Supporter level "2".
Same to themes.
Thanks
Lead Developer — 20th July 2011 (10 months ago) #
Yes, but levels are additive, so level 2 can access level 1 plugins/themes.
Member — 20th July 2011 (10 months ago) #
Can I set default for level 2 - which plugins will be activated as default? They will have access, but talking about default activated plugins.
ant Themes.
Lead Developer — 20th July 2011 (10 months ago) #
I think so. If they go from say level 0 free to level 2, only autoactivate checked plugins for level 2 will be autoactivated.
Member — 20th July 2011 (10 months ago) #
I think I am asking same question and sorry for that - but I haven't understood quite clearly - yes, those plugins and themes will auto-activate if they subscribe for higher level, but will some plugins auto deactivate too? (Some - which I will set)
Lead Developer — 20th July 2011 (10 months ago) #
If you go from 0 to 2, it will activate level 2 plugins.
If you go from 2 to 0, it will deactivate level 2 and level 1 plugins.
Member — 20th July 2011 (10 months ago) #
OK, Thanks.
Member — 20th July 2011 (10 months ago) #
By the way, can you tell me approximate date of coming out of Supporter 3.0 stable version?
Member — 20th July 2011 (10 months ago) #
While I appreciate that ETA's are often frowned upon, I would also like to know if there is even a general sense of when a stable version will be available?
It certainly seems from much of the feedback bugs and issues are being addressed fairly quickly?
Great job ..... looking forward to this plugin.
Lead Developer — 20th July 2011 (10 months ago) #
I can't say, have a lot to do before a little vacation coming up. So it may be Aug.
My biggest worry is the payment API, which so far only Gina seems to be testing ;-) Especially refunds, upgrades, downgrades, etc.
Member — 21st July 2011 (10 months ago) #
Hi Aaron,
Downloaded and testing pro-blogs-3-beta-2. WPMU version 3.2.1
While the install and settings process went very smoothly here is what I have experienced so far, hope it helps:
http://mysite.com/pro-blog/?bid=2
ERROR:
Warning: Missing argument 2 for ProBlogs::page_title_output() in /home/mysite/public_html/wp-content/plugins/pro-blogs/pro-blogs.php on line 1168
SUGGESTION:
Would be nice to be able to sort plans so that cheaper plans appear at top.
SUGGESTION:
Move coupon code field right above plans - Due to the flow once coupon is applied (message appears at top of plans indicating that coupon has been applied) This is much more friendly for end users as they see instantly that coupon worked and then can scroll down through plans - it might even compel them to subscribe to a higher plan since they have already seen the coupon applied.
SUGGESTION:
Center payment information/links under plans
SUGGESTION:
Add message above plans instructing user to click desired plan 'and' then click the payment link. This may seem obvious but it actually too me a few clicks of the plan info to realize it wasn't going to redirect me automatically and then I realized clicking the plan was just a highlight function and you need to click payment link below.
ERROR:
When clicking the PayPal link after applying coupon code and selecting plan, I'm directed back to the 'plans' page I was just on instead of paypal. Double checked all paypal IPN and API details and everything seems okay. I will continue to test the paypal process once this issue is resolved.
Member — 21st July 2011 (10 months ago) #
I'd like to test very much, but here isn't any popular payment ways in Georgia yet. Even PayPal is planned to be available in August.
---
Aaron, I think I haven't explained in correct way what I was asking you yesterday.
So, it's good that if User upgrades package from 1 to 2, (s)he will have activated all plugins, plugins for 1 package and plugins for 2 package.
And so - if (s)he downgrades from 2 to 1, plugins for 2 package will be deactivated and there will be left only package 1 plugins.
But I am asking something different - Will I be able to assign only plugins package 3 will have?
For example (this example will clarify everything I think):
There will be 3 packages:
1) First will be free and it'll be for blogs.
2) Second will be paid and it'll be for blogs too (with more functions and themes, which will be auto-activated).
3) Third will be paid and it'll be for e-Shops (with MarketPress & FrameMarket). So this is what I am asking: If user purchases this package, it's quite clear that this user doesn't need standard blog features, for example - Auto Blog (which second package has).
So yes, it's good that if user upgrades, it will auto-activate some themes and plugins for him, but will it be possible to DE-activate too?
---
I'll make another example - The last stable version of Supporter has premium plugins feature you know, and when admin clicks on it, it shows page, where admin can assign which plugin will be accessible for None, Everyone, Premium.... So, now I think it will be like this - None, Everyone, Premium, Premium1, Premium2... Am I right?
So, If I select MarketPress plugin for Premium2 and Auto-Blog for Premium 1, this means that Premium 2 will have both of them - MarketPress and Auto-Blog? If this is so it's bad for me, as user, who uses MarketPress, doesn't need AutoBlog.
This is what I am asking if it is possible. If it isn't take it as my suggestion please, as there is lot time before stable version comes out (Aug, as you said).
Thank you!
Lifetime Member — 21st July 2011 (10 months ago) #
Keshingelia,
Using your example.. Yes your level 3 would have access to plugins available to level 2...like Aaron said they are additive. Your level 3 would have access to autoblog (which they can always deactivate and not use) but maybe they would want to use this feature. I know I would on my ecommerce site.
I actually prefer they stair-step way it is set up now where users (via levels) gain access to more and more features.
:)
Gina
Lifetime Member — 21st July 2011 (10 months ago) #
@Aaron weird thing... When I tried to select the 3 month payment plan for Problog I got taken to a PayPal page that said:
Page Not Found
You have requested an outdated version of PayPal. This error often results from the use of bookmarks.
Gina :)
Member — 21st July 2011 (10 months ago) #
Thanks Gina, but that's something which I already know (Aaron told me). I am very sorry because I can't explain exactly because of my English (maybe).
So this is last try:
You said "which they can always deactivate and not use". I have marked with bold important part - "can", but is it possible that those plugins were auto-DE-activated and users still have possibilty to activate them.
So you say that (and I know that) when user upgrades to higher level, he will have access to plugins and themes those level offers him and lower levels too.
But my question is - Yes, it's very good that higher package offers users features of lower packages too, but is it possible to offer them those plugins/themes in "Deactivated" way? So that yes, user will have access to them, but they will be deactivated as default.
So the conclusion is that:
NOT - Users will be able to deactivate plugins they don't need, but
YES - Users will be activate plugins they need
---
It seems to be very little difference between those sentences, but I think you understand now, I have tried my best to explain it :)
Thank you!
Lifetime Member — 21st July 2011 (10 months ago) #
Yes you can set all plugins and themes where the user would have to activate them to use them. :)
Gina
Member — 21st July 2011 (10 months ago) #
Ok, thank you very much :)
Lifetime Member — 21st July 2011 (10 months ago) #
you are welcome :)
Member — 21st July 2011 (10 months ago) #
Hi Gina,
Wondering if you are testing pro-blogs-3-beta-2 and if so, did you expereience any issues with being directed back to the 'plans' page after clicking the Checkout With PayPal link instead of the paypal page?
I have double checked all paypal IPN and API details and everything seems okay.
Thanks,
Chris
Lifetime Member — 21st July 2011 (10 months ago) #
yes i am. i am being directed back to the plans page with this message on it:
There was a problem setting up the Paypal payment:
"A successful transaction has already been completed for this token."
Please try again.
somehow it's getting sent twice...
Member — 21st July 2011 (10 months ago) #
Okay, thanks.
I'm experiencing a similar issue with the redirect, although I'm not seeing any messages.
Chris
Lead Developer — 21st July 2011 (10 months ago) #
kshengelia, the difference is autoactivating or just having access to. When upgrading to a higher level, only the plugins for the new level will be activated if you have checked them to. So if they go from free to level 3, only level 3 plugins will be autoactivated, though they will still have access to level 2 plugins.
Member — 21st July 2011 (10 months ago) #
Ok, that's exactly what I wanted to hear from you, thanks thanks!
Lifetime Member — 21st July 2011 (10 months ago) #
hi aaron,
if i were to launch now with supporter 2.2.8 are there going to be many issues in switching to problogs next release when api issues etc are resolved?
...or should i just wait?
thanks,
gina
Lifetime Member — 21st July 2011 (10 months ago) #
also with problogs.. i noticed no matter what payment level you select (1, 3 or 12 months) on the paypal check out page it says "per month" on it.
for example.. say these are the price levels:
1 month: $5.00
3 months: $10.00
12 months: $50.00
then if you were to select 12 months it would say "$50.00 USD Per Month"
gina
Member — 22nd July 2011 (10 months ago) #
Hi Gina,
So am I to understand that even though you were having the redirect issue we discussed earlier you were able to eventually get to the paypal checkout page?
If so how did you bypass the issue of redirection to the plans page?
I'm hoping to test some of the paypal features as requested by Aaron (refunds, upgrades, downgrades, etc.)
Thanks,
Chris
Lifetime Member — 22nd July 2011 (10 months ago) #
yes i get to the paypal page to enter account info to authorize payment but after putting in password it takes me back to the pro blogs page with that error.
Lifetime Member — 22nd July 2011 (10 months ago) #
i was reading another developers site for a plugin in which a user was getting the same paypal error i am getting and he said "some plugins or site settings can cause the hooks which call the plugin functions to be called multiple times from within a single WordPress request."
do you think that is what is happening here?
gina
Lead Developer — 22nd July 2011 (10 months ago) #
that could be. I havn't had a chance to look into the billings stuff at all yet, so it could very well be completely nonfuncitonal (though was working on my test site before beta). Patience guys ;-)
Lifetime Member — 22nd July 2011 (10 months ago) #
no problem :)
gina
Member — 23rd July 2011 (10 months ago) #
hiya
whats the ETA on release date?
cheers
Johnny
Member — 23rd July 2011 (10 months ago) #
August-ish.
Lifetime member! — 24th July 2011 (10 months ago) #
well a little out of purpose but still related, concerning ads.
When you'll dev the adds insertion plugin, remind a detail : many themes allows to add the featured image on pages/post.
Would need to insert ads BEFORE the thumb, if not page / post layout is just weird.
Ad block ads isertion on home pages and archive pages using the excerpt thing....
Member — 25th July 2011 (10 months ago) #
Hi Aaron,
Looking forward to continue testing of the plugin specifically paypal features as you requested (refunds, upgrades, downgrades, etc.)
Just waiting on a fix for the redirect issue on plan selection and paypal link as described in my earlier 'test notes'.
Ready to go as soon as this issue is resolved and I can access ore payent features.
Best regards,
Chris
Member — 25th July 2011 (10 months ago) #
I like some of the new features! Especially the coupons and easier management of the premium plugins and themes. Looks like a lot of work has been going into this. I'd drop the blog out of 'pro-blog' though and just leave it at 'pro'.
One thing I was really surprised and very disappointed to to see left out was the trial period...that feature alone equates to thousands of dollars when you compare the conversion rates. It really is a no brainer to have that simple option added in there when it comes to subscriptions if you want to see loads of signups when you run a 'Free Trial' campaign.
I did find a bug on being redirected back to my page when trying to make a paypal payment and yes, the api settings were all in. Not sure what happened there but I guess I'm not the only one with that issue.
The plan graphics leave much to be desired, the little square thing going on for the pricing could be worked on, it might be best to take a minimalistic approach so that it blends in well with any theme.
Overall I do like the new version so far and really hope to see what the final outcome is after the dust has settled. Hopefully the trial option gets back in there where it belongs too! ;)
Member — 25th July 2011 (10 months ago) #
+1 Free Trial
Member — 25th July 2011 (10 months ago) #
Just got back from vacation so I missed this but this is the greatest update I have ever seen! I can;t wait to try it out!
Member — 25th July 2011 (10 months ago) #
+1 Free Trial? That means that new version of Supporter doesn't have trial feature? If so, my
+1 to Free Trial
Lifetime Member — 26th July 2011 (10 months ago) #
ya i think most of us will +1 to Free Trial
Member — 26th July 2011 (10 months ago) #
Hey guys, I'm testing it right now but I would like to know if it would be possible to add the PayPal Brazilian website to the PayPal Site option.
Thank you for the incredible plugin
Member — 26th July 2011 (10 months ago) #
Is it possible to have only 1 plugin. Instead of multiple activations?
In the super network admin, if the tickbox enables the feature only then will it hook wordpress.
Or is that not how it works? Is activated 10+ plugins the easiest way for an admin to set it up?
If you are keeping the 10+ plugins could you please update the description on the plugins page so they are informative and not exactly the same.
Just wondering your thoughts,
Johnny
Member — 26th July 2011 (10 months ago) #
I activated supporter plugin. then activated limit blogs sub plugin.
Call to undefined function is_supporter() in mydomain_com/wp-content/plugins/supporter-plugins.php on line 207
Am I not activating these in the right order?
John
Member — 26th July 2011 (10 months ago) #
just testing the plugin now
i had simple question. would it be possible to have multiple free levels, and then be able to upgrade those levels. or simply would be able to have free levels without upgrading
this plugin is so powerful. thank you so much!
Member — 26th July 2011 (10 months ago) #
I am testing the plugin now and its fantastic! As far as payment gateways, -1 for amazon but would Authorize.net ever be in the cards?
+1 Authorize.net
Member — 26th July 2011 (10 months ago) #
+1 for authorize.net, no paypal in the country of alot of my projects :(. but otherwise it would be full on paypal.
Member — 27th July 2011 (10 months ago) #
hey
for the different levels of supporter, could each have a one time payment instead of subscription? or is the one time payment only avaliable for the pay to blog (which i think is an awesome feature)
thanks
Lead Developer — 27th July 2011 (10 months ago) #
Hey all, thank you so much for your bug reports and testing, I've got a good list to go on. Unfortunately I've run out if time before my scheduled vacation, so need to put those on hold for a bit.
Rest assured that as soon as I get back aug 8th I'll be finishing this as a top priority. We're trying to get this live on Edublogs before the school year starts.
So until then, I'm gonna unstick this and open a new thread when I put up beta 3. Thanks again for your help and patience!
Member — 27th July 2011 (10 months ago) #
Hi Aaron,
I have installed the Pro-Blogs plugin and looks great. Please also add manual payment as a gateway. I don't think much person in my community in Indonesia having paypal account. Or would be great functionally if the admin can setup local payment gateway, I don't know would be doable or not.
Cheers.
Member — 27th July 2011 (10 months ago) #
Fatal error: Call to a member function get_page_permastruct() on a non-object in home/agric/public_html/wp-includes/link-template.php on line 276
This happened when I went to add a second level of payment. Backed up and tried again. This time it took out my admin panel. Had to rename the plugin folder and recover.
This is a new install of WPMS, very few plugins.
Trying to set 3 levels of service: Free/ $x / $y
Thanks
Member — 27th July 2011 (10 months ago) #
Line 276
$link = $wp_rewrite->get_page_permastruct();
Member — 27th July 2011 (10 months ago) #
I believe I found what is happening. I reloaded the plugin (several times) to troubleshoot. Found I can set up levels but if I change the Pro Blog Setting to rebrand the plugin as anything other than Pro Blogs, it causes the fatal error. Might be tied to having more than one level and rebranding.
Lifetime member! — 29th July 2011 (10 months ago) #
note : be carefull guys with free trial... Onece activated, any theme and plugin will REMAIN activated after trial period.
Only quota and ads will return. This is not a good thing. And it is not really possible to auto deactivate activated plugins....
For gateways moneybookers (skrill) is available in almost all countries... And free of charge setup....
Sales & Support Lead — 29th July 2011 (9 months ago) #
Whew. So this thread is ridiculously long. I'm closing it up to avoid further comments here (please feel free to open new threads on the topic).
I'm also going to mark it as a sticky so folks can still grab it up easily :)
Thanks!
Lead Developer — 19th August 2011 (9 months ago) #
Hey guys, beta 3 is out, yay!
http://premium.wpmudev.org/forums/topic/pro-blogs-supporter-30-beta-3-release
Thanks for viewing this post but this topic has been closed to new replies.
Become a member