Supporter 2.0
I can't tell you how excited I am about this release... it's a *brand new* version of Supporter that really takes it the next level!
http://premium.wpmudev.org/project/supporter
I've spent so much time writing about it today so far that I really can't say much more except huge kudos to Aaron who's been the driving force behind the code here.
And ask you guys for feedback, bugs, comments, general 'wow's etc. :)
Help & Support from WPMU Dev members and staff
Looks good. Can I just overwrite the old version and the supporters keep their supporter status etc?
A guestion about the advertising: Is ad-sharing in any way affected by the remove ads thing?
I guess the two plugins by Aaron for premium plugin management and premium themes have now become redundant?
just noticed the new plugin management doesn't have the exact same features as Aarons old plugin, i.e. the mass activate and auto activate features are missing...
can I run that plugin in parallel or will it conflict?
what was the reason to not incorporate the exact same features here? maybe I am not seeing it?
my error log says: ´[Tue Nov 03 11:34:25 2009] [warn] mod_fcgid: stderr: PHP Fatal error: Call to undefined function deactivate_plugins() in /var/www/clients/client1/web9/web/wp-content/mu-plugins/supporter-plugins.php on line 150
´
I have no idea where this comes from :-(
I uplaoded all files except for the amazon files, the buddypress plugin and the supporter write plugin as I don't want to restrict writing...
sorry guys, I need some help:
most of the blogs fail after I upgraded the Supporter plugin, here are some examples:
- http://gurascheiului.zice.ro/
- http://enigmavietii.zice.ro/am-invatat/mira-pe-cineva/
- http://enigmavietii.zice.ro/am-invatat/mira-pe-cineva/
- http://theodorcapricorn.zice.ro/uncategorized/risen/
- http://revistanaturista.zice.ro/uncategorized/ce-este-bioritmul/
besides anyone has a clue what this error is supposed to tell me:
´
[Tue Nov 03 11:46:08 2009] [warn] (103)Software caused connection abort: mod_fcgid: ap_pass_brigade failed in handle_request function
´
and, I had to manually make certain blogs supporters, although they were supporters in the old version...
ok, is the upgrade reversible? can I simply repalce all files again with the old version? the whole installation broke :-(
Wow! Sorry for the trouble Ovidu! We've been testing this thing for a week without trouble. Here to help.
First, you should be fine overwriting ALL files with the older versions. I left the old db tables intact so downgrades wouldn't be a problem.
And what do you mean by most of the blogs fail? Can you give me more details?
Also what version of wpmu are you using?
well, the downgrade went smooth. up and running again.
by failing I meant that the blogs load, kinda 10%, most of them were showign the background color, then nothing. checking the sourcecode, it seemed to stop loading right after the admin bar I am using, I mean the last code in the source of the page was always the admin bar, then nothing.
I am using this admin bar: http://wpmudev.org/project/MU-Admin-Bar
I can't imagine what would hang up admin bar. There is this in code that was added for MU 2.7, but it's been in there for a few supporter versions:
add_filter('wpabar_menuitems', 'supporter_admin_bar');
Is anything coming up in error logs for the blogs it was hanging?
Call to undefined function deactivate_plugins() in /var/www/clients/client1/web9/web/wp-content/mu-plugins/supporter-plugins.php on line 150
That makes no sense as deactivate_plugins() is a wordpress core function in the plugins.php include. It is also called in WPMU Plugin Manager which it sounds like you have no problems with.
and, I had to manually make certain blogs supporters, although they were supporters in the old version...
I can't imagine how that could happen. The upgrade does not modify any records in the supporters db table, and the core code for checking supporter status is the same.
Did all blogs loose supporter privileges, or just certain ones? Any pattern? If you pulled those up in the supporter backend, when did it say they expired?
Another thing, i'm sure you visited the Supporter admin page after upgrading? The upgrade script is only run on the first visit to the admin page.
Also check that the new wp_supporter_signup_stats and wp_supporter_daily_stats tables were created. Also that the "gateway" and "term" columns were added to the wp_supporters table.
Qlof:
Looks good. Can I just overwrite the old version and the supporters keep their supporter status etc?
Yes, *shouldn't* cause any problems. If you're really super cautious you can make sure you have a backup of the wp_supporters table. (you should be doing that for your site daily anyway).
A guestion about the advertising: Is ad-sharing in any way affected by the remove ads thing?
No, it's not affected. The supporter-ads.php extension wasn't changed much, and still only integrates with the supporter advertising plugin.
http://premium.wpmudev.org/project/supporter-advertising
I guess the two plugins by Aaron for premium plugin management and premium themes have now become redundant?
Premium Themes definitely. There are some major improvements (namely previewing), and no donate nag message (never got a single donation anyway). ;-)
just noticed the new plugin management doesn't have the exact same features as Aarons old plugin, i.e. the mass activate and auto activate features are missing...
can I run that plugin in parallel or will it conflict?
what was the reason to not incorporate the exact same features here? maybe I am not seeing it?
You can use either/or. A warning message will show if you try to have both installed, as that would create some strange behaviour. The goal here was to have a premium plugins functionality as part of Supporter that just gave you the basics of what you need to increase supporter sales. Advanced plugin management was a little beyond the scope and purpose of Supporter.
Note that WPMU Plugin Manager doesn't deactivate plugins when a supporter expires. Eventually I will release an updated version of that either free or through premium here.
Is there a way to demo like the older Supporter plugin did? I don;t see that mentioned in the text.
Is there a way to demo like the older Supporter plugin did? I don;t see that mentioned in the text.
If you mean sandbox then yes. You can activate sandbox mode for both the amazon and paypal gateways.
Note that you would want to do this not on a live site as the sandbox buttons would display to users and likely cause some confusion!
The previously plugin gave the option for new users to have the features of Supporter for 'x' number of days as a test to try the features before having the premium features reduced. That went over well with our clients.
Sorry that I didn;t explain fully.
Yes, the trial period is still an option.
Call to undefined function deactivate_plugins() in /var/www/clients/client1/web9/web/wp-content/mu-plugins/supporter-plugins.php on line 150
We've fixed this bug now. Thanks for reporting!
Yes, the trial period is still an option.
Cool. Thanks.
2.0.1 has been released with fixes for the bugs above.
Let us know if you have anymore issues.
I think I'll sit and wait for someone else to try it out :-)
will give it another try in the next couple of days ;-)
Just a quick bit of feedback - apart from a 'wow' from us - where can I change the text that appears when a user has upgraded to Supporter?
The bit that says:
As a Supporter, you now have access to all our premium plugins!
We've named ours something that makes it not quite read correctly
(also, while I'm thinking about it, it would be quite handy to have a 'Hide' link in that message so people can choose not to see it anymore)
Cheers and great work!
I think I'll sit and wait for someone else to try it out :-)
will give it another try in the next couple of days ;-)
Haven't had a problem with all our test sites and my live site. Some of your issues may have been due to the bug you discovered and I fixed in 2.0.1.
We've named ours something that makes it not quite read correctly
I thought about that. What do you call it? I make the entire message text an option in settings next version.
(also, while I'm thinking about it, it would be quite handy to have a 'Hide' link in that message so people can choose not to see it anymore)
Probably won't implement that. With enough votes we can just remove it though.
Meanwhile it's an easy edit. Modify the text in lines 167 and 169 of the supporter-plugins.php file. If you don't want the message you can comment out (//) line 169.
@Aaron: no disrespect meant, just too busy to do it now in case I hit another bug and I am pretty sure my problems were related to that particular bug.
Forgive me if I missed a step somewhere. Is the supporter option available on the /register page if you are using Buddypress, or can it only be accessed on the wp-signup.php page? Thanks.
Is the supporter option available on the /register page if you are using Buddypress, or can it only be accessed on the wp-signup.php page?
Only on the blog signup pages. (wp-signup.php and buddypress create blog)
Got it. Thanks.
Questions on behalf of all of us out here running Plugin Manager and considering this awesome looking upgrade ...
It appears we should deactivate (remove) plugin-manager prior to upgrading. Can you confirm this and whether or not doing so will affect any current Supporter blogs? And, are there any db tables that need to be dropped or modified?
Also, since I haven't yet compared any code, can you confirm the show-ads script included with Supporter v.1 has not changed any? Or will I need to replace that?
Thanks for all your hard work!
PS: Adding the auto-activate certain plugins option for Supporters into next release would be dandy.
I cant say for sure but I'm fairly certain that:
a. Yes, remove plugin manager (use the default Activate sitewide' if you want
b. No dbtabled modded as far as I know, although you might want to check the install instructions for multi-db if you are using that
c. show ads should be just fine as it is
And thanks for the request, we'll bear it in mind and please do come back on the next review and add it (and any others) in again.
Giving it a go now. Thanks!
FYI: I think the install.txt instructions need some clarification ...
Required:
supporter-files - entire folder and contents goes in /wp-content/mu-plugins
This indicates there is a directory called "supporter-files" that needs to be placed into /mu-plugins but the 2.01 download includes no such folder.
I'm going to assume these instructions refer to all the files in the /wp-content/mu-plugins folder of the 2.01 download, but some of these are optional files so the instructions are still misleading.
Or, am I missing something?
There is a supporter-files directory in the zip file. We used to have every file piled in their but with so many it was getting confusing where they go, so we put them in the correct dir structure in the zip file to make it a little less confusing.
On the question about supporter-plugins, you could continue with Plugin Manager as you cam use either or, and it has a little bot more functionality. The main difference is our version will deactivate anything they are not set to allow to have.
So if you install supporter-plugins make sure to choose which ones to allow right away or when users login it will deactivate all their plugins. Thinking about it now I'll release a small update to not deactivate plugins until you have first saved your user control settings.
There is a supporter-files directory in the zip file.
Take a look at the 2.01 archive again again (see attachment). There is a directory structure showing what should go where, but there is no folder titled supporter-files as the instructions suggest.
[attachments are only viewable by logged in members]
Nevertheless, so far so good. I just have a few questions / concerns ...
1. Where will I find the list of Supporter blogs? The previous version's admin page listed the blog ids of all current supporters. I cannot find this on any of the new Supporter admin pages.
2. My main Supporter admin page just has a lot of big blank spaces with "No Data Available Yet" ... I assume this is where the "pretty graphs" will display, but i would expect at least the active Supporters to be displayed. See question #1.
3. Avatars are not showing in the widget. I recall this happened in a previous version and Andrew had to release a fix. Unlike last time, Random Supporters are showing in the widget, but only their names even though I've selected Avatars and names.
but there is no folder titled supporter-files as the instructions suggest.
Thanks for spotting that. We're uploading a fixed zip file ASAP. Meanwhile you can pull just that folder from the previous version (2.0.0) here:
http://premium.wpmudev.org/project/supporter/download
Where will I find the list of Supporter blogs? The previous version's admin page listed the blog ids of all current supporters. I cannot find this on any of the new Supporter admin pages.
That wasn't a feature in the previous version But now you can view supporter status on the Site Admin -> Blogs page. Or use the supporters widget.
My main Supporter admin page just has a lot of big blank spaces with "No Data Available Yet" ... I assume this is where the "pretty graphs" will display, but i would expect at least the active Supporters to be displayed. See question #1.
Thats because of the missing supporter-files folder.
Avatars are not showing in the widget. I recall this happened in a previous version and Andrew had to release a fix. Unlike last time, Random Supporters are showing in the widget, but only their names even though I've selected Avatars and names.
Not sure whats up with that. Didn't touch that widget's code in this version. Can you give us a link? We'll look into it.
Are you using our blog avatars plugin? Those are the only Avatars the widget supports. If you're using buddypress you can try the edit mentioned in that thread.
Are you using our blog avatars plugin?
Yes. And avatars are still showing fine in the blogs and global posts/comments widgets. Thanks for the quick reply!
I've tried re-saving the widget settings, but nothing gets avatars to display...
http://tripawds.com
(See supporter widget in left sidebar and recent blog posts beneath that.)
Do you see this input in the widget options?
[attachments are only viewable by logged in members]
pull just that folder from the previous version
OK, thanks! Stats are showing... well, most of them. Should I assume the Summary only tracks activity going forward? I'm just getting a flat line for all three variables in the first graph, and nothing (no lines) in History and Term History.
No graph at all for Current Terms, just "No data available yet".
Sorry to hijack this topic!
PS: Since you asked about future enhancements ... a list showing active Supporters with Links to the blogs, would be a nice addition to the stats.
FYI: When sorting the wpmu-blogs page by the Supporters header, "No blogs found." is shown even if there are supporters on the page.
Note the 2.0.1 zip file has been fixed to include the needed supporter-files directory.
If anyone recently installed 2.0.1 please confirm that you have the supporter-files directory in mu-plugins, otherwise your pretty charts won't show. (everything else would still work though)
Do you see this input in the widget options?
Yes, I saw all three options, and tried each. Only the name shows up no matter which I try.
Side Note: v. 1.5.6 of the Supporter widget is still running on another site using the same theme, avatars and all ...
OK, thanks! Stats are showing... well, most of them. Should I assume the Summary only tracks activity going forward? I'm just getting a flat line for all three variables in the first graph, and nothing (no lines) in History and Term History.
Those stats will only track things going forward. There was no recorded history to create stats for the past on upgrade. The term counts and ratios will update the next time each supporter's subscription payment comes through. All the history charts are run on a daily cronjob (as long as your main blog has enough traffic).
When sorting the wpmu-blogs page by the Supporters header, "No blogs found." is shown even if there are supporters on the page.
That's a known limitation in MU. The filter lets us add a column, but makes it look sortable when there is no way to do that in a plugin.
We'll consider adding a supporter list. That's really pretty easy unless we have to add pagination.
FYI: I uploaded the old version on the widget, and the avatars display fine. Is there any harm in just using that one until you guys figure out this anomaly?
Go ahead and use the old one if it works. That definitely sounds like a bug. I'll check it out.
Thanks for the stats clarification. Multiple pages of supporters would be a good thing! For us at least. ;-) I doubt anyone would mind just having a long list, perhaps on its own sub-page, i.e. ...
Statistics | Active Supporters | Modify a Blog | Settings | Premium Plugins
Just a thought, thanks again for all the help and hard work!
Looks like you found a bug introduced in 1.6.3. It's amazing what a missing ! will do.
We will release the fix in 2.0.2 in a day or two.
Thanks for the update, very nice!
One minor glitch: for the admin account, all of the installed plugins aren't showing up under the plugins menu, only the ones marked as available to premium or everyone under the premium plugins module.
keep up the good work.
all of the installed plugins aren't showing up under the plugins menu
I noticed this too, for sub-blogs. But you got me thinking, so I looked and now discover that all my primary-blog-only plugins – set to none in the new Supporter admin – are no longer in my Plugins menu. This is a bad thing.
Unless I'm missing some option somewhere for showing all plugins to admins, I'm really hoping this can be addressed with the release in the works.
Thanks!
I will include those in 2.0.2. Note I can't allow site admin to activate supporter only plugins on non-supporter blogs as it will just get deactivated again.
I also am experience the problem with plugins, they don't show for the admin unless you enable them for subscribers. That's kind of a deal killer if you are constantly reconfiguring and updating your site.
I can't allow site admin to activate supporter only plugins on non-supporter blogs
Hmmm... so I suppose the plugins we had activated on various non-supporter blogs have already been disabled. :-/ Wasn't expecting that.
We run a number of sub-blogs which need certain plugins activated that we don't provide to anyone else, not even Supporters, Unfiltered MU for instance. With Plugin Manager, admin activation was possible. We also liked the idea of having certain sub blogs of our own remain non-supporters since we wrap header ads in the if-supporter-hide-ads code.
Any suggestions?
PS: Please bump this topic when 2.0.2 is available. Thanks!
@jcnjr
We too used the same functionality of activating plugins on non-supporter blogs that aren't used anywhere else, and it'd be nice if they could integrate that feature into this some how as well. It seems to be a popular one.
@jcnjr & @Inspirosity,
i have the same problem, it will be nice to include this feature too.
Just waiting for the 2.0.2 release to seee what happen
also, what about a feature to import the plugin settings from Aaron's old plugin manager so when one upgrades to supporter 2.0 one doesn't have to quickly go through the plugin list again and set permissions from scratch?
Otherwise I'll have to leave the old plugin manager active to compare side by side with the new one to get all permissions (none, all , supporters only) right...
A big ++ would be to have the following options:
none (can only be enabled by ADMIN, but still functions on all blogs)
all (can be enabled by anyone)
auto (auto on for everyone)
supporter (CAN be enabled by supporter)
supporter auto (auto on for supporters)
This way, if your sales page lists "analytics" as perk for becoming a supporter, when payment goes through.. you have analytics (one click).
Extra items (eg event calendar) can be turned on one by one..
I don't know if this is a bug but i'm getting this error:
Fatal error: Call to undefined function is_supporter() in /home/hannover/public_html/romeotest.com/wp-content/mu-plugins/widget-supporter-badge.php on line 68
When i delete this file than works...
We run a number of sub-blogs which need certain plugins activated that we don't provide to anyone else, not even Supporters, Unfiltered MU for instance. With Plugin Manager, admin activation was possible. We also liked the idea of having certain sub blogs of our own remain non-supporters since we wrap header ads in the if-supporter-hide-ads code.
Thanks guys for all the feedback. I fully understand all your needs, but we are starting to get beyond the scope of the Supporter plugin. Go ahead and continue to use WPMU Plugin Manager if you need to, I can say I still do on my own live site!
The only feature not in Plugin Manager that is in supporter-plugins.php is that it won't deactivate supporter plugins when the blog's supporter privileges expire. I don't think that's a dealbreaker as we've all been living with it for a while now. I might patch that in to a Plugin Manager update.
I'm eventually hoping to move Plugin Manager into MU core anyway as that's really where it should belong, then making sure our supporter-plugins.php file extends it's functionality.
supporter auto (auto on for supporters)
I definitely think that is worthy of adding and will consider it for next release.
+ one more
'default' = auto with an option to turn off
where 'auto' is more like a wpmu plugin that all blogs must have, default is a suggested plugin that is on by default but can be turned off if needed.
Ideally, I'd like to be able to pick and choose which plugins a user (even the admin of a member blog) is able to see / edit the settings for.
Sometimes I want all users to have a plugin, I want to set the default settings (currently done by modifying the plugin itself), and I dont want them to see those settings (usually) or deactivate (always). This would be the 'auto' use case.
'default' would be a case where I do want them to be able to see the settings panel, and be able to de-activate if desired.
(still vote for a plugin-by-plugin control over who sees the settings)
Fatal error: Call to undefined function is_supporter() in /home/hannover/public_html/romeotest.com/wp-content/mu-plugins/widget-supporter-badge.php on line 68
What pages are you getting this error on? Are you sure you have the supporter-framework.php file in mu-plugins?
Sometimes I want all users to have a plugin, I want to set the default settings (currently done by modifying the plugin itself), and I dont want them to see those settings (usually) or deactivate (always). This would be the 'auto' use case.
You can do this by modifying the plugin and using sitewide activation.
(still vote for a plugin-by-plugin control over who sees the settings)
There's no way to do that other than modifying the plugin file.
Hi Aaron,
just after uploading all files it shows that error, i mean i was in the Admin Panel and upload all the files then refresh the admin and had a blank page with that error, after 2 minutes i refresh again and everything worked.
I have another question about localization of this plugin.
I use CodeStyling Localization Plugin and when i am in the setting there i see your Plugin showin in the list, but as i try to scan it scans only 1 folder (mu-plugins) with 0 results.
Have you done the localization wrong or this is not a feature of this plugin?
Payment issues...
In admin/supporter/settings:
1 We're offered Paypal settings, but not Amazon's
2 On the SignUp page (2nd stage)
selecting 'I'm interested' & clicking SignUp
... leads to the "Thanks, your email is on its way" page
You'd expect it to ask for payment!
(& it would be good to be able to change "I'm interested" to a straightforward 'Buy Now' message)
Any ideas?!?
Otherwise, loving the whole thing!
just after uploading all files it shows that error, i mean i was in the Admin Panel and upload all the files then refresh the admin and had a blank page with that error, after 2 minutes i refresh again and everything worked.
That was probably just because the supporter-framework.php file wasn't finished transferring yet.
Have you done the localization wrong or this is not a feature of this plugin?
I think I did it right. If you place a language file in /mu-plugins/supporter-files/languages/ it should work.
Does the CodeStyling Localization Plugin normally work with plugins in mu-plugins? If so can you point out an mu plugin that it does scan correctly so I can compare code?
Additional issues:
Supporter-write.php does not appear in the settings or as a menu item when loaded into /wp-content/mu-plugins. Also supporter-quota.php is not increasing quota limits when added as a plugin even though you can make the changes in settings. Otherwise liking the improvements!
We're offered Paypal settings, but not Amazon's
You probably didn't upload the supporter-gateway-amazon.php file to mu-plugins. (And don't forget the supporter-amazon.php file in root!)
On the SignUp page (2nd stage)
selecting 'I'm interested' & clicking SignUp
... leads to the "Thanks, your email is on its way" page
You'd expect it to ask for payment!
Due to MU limitations (you can't pay for a blog that doesn't yet exist - no blogid), the checkout screen is shown after the blog has been activated on first login. They then either have to pay or click the small dismiss link on the bottom of the screen to see anything else in admin.
In case anyone wants to remove the dismiss link, you can comment out line 501 (//add_action('supporter_output_after', 'supporter_signup_dismiss');) in supporter-framework.php file.
@Aaron
I think you're right that maybe SOME of us (like me hah) might be expecting too much from the plugin portion of supporter.
I think updating WPMU Plugin Manager to deactivate after subscription expires would be a great enhancement and would also take care of a lot of other issues brought up in this thread.
Supporter-write.php does not appear in the settings
It has no options. Just disables the post and page write menus.
Also supporter-quota.php is not increasing quota limits when added as a plugin even though you can make the changes in settings.
Are you sure about that? Works for me. Have you saved the settings for quota increase? You can see the quota right on the dashboard under Storage Space. Also if not a supporter blog it adds a message there saying to become one for ###MB of space.
Hi Aaron,
yeah that's true about the localization with that plugin.
I try to translate it using poEdit but as i try to create a new catalog it shows me 2 errors (printscreen attached).
Then when i translate the file i save it as sq_AL.po and sq_AL.mo (stays for Albanian language) but nothing happens in the admin section. Should the file be renamed as pluginname-sq_AL.po or something like that?
[attachments are only viewable by logged in members]
Now see that the add new post/page are not available when a non-supporter.
The quota states 10MB Space Allowed under the dashboard when the settings have been saved at 11MB and a supporter. When a non-supporter it shows the proper message. Shouldn't the space allowed be showing the same as to what it is set to in settings as a supporter?
I believe it should be "supporter-sq_AL.mo/po". "supporter" is the text domain which should proceed the language.
Not sure whats causing the error in poedit. I guess skip the supporter-ads file for now.
Thanks Aaron, now the translation works.
It's a nice chooise to make the future plugins and themes with localization :)
Keep goind so, im very happy with support and the plugins here.
Thanks a lot.
Just for other who want to translate the plugin too:
Do it with poEdit (ignore the two errors) and save the file as supporter-it_IT.mo/po (ex for italian language) and then upload all to /mu-plugins/supporter-files/languages/
Refresh the Admin Panel and HERE YOU GO!!! ALL Works Great
Ok all, 2.0.2 version of supporter has been released:
- Fixed supporter widget bug added in 1.6.3: http://premium.wpmudev.org/forums/topic/supporter-20/page/2#post-18643
- Added ability for site-admins to activate ANY plugins for a blog
- Added "Supporter (auto-activate)" option for plugins
- Made the plugins page message editable in settings
Thanks for all your input and bug testing!
I'm closing this thread as it's getting quite busy!
You can continue reporting any bugs in this thread:
http://premium.wpmudev.org/forums/topic/supporter-202