I have uploaded the plugin and have entered the code as directed in the installation guidelines to make plugins only available to supporters but for some reason it doesn't appear to be working.
everything else appears to be working alright. As a feature request could access to various themes be built into the supporter interface or would I be better suited to trying the upgrades plugin?
7430 pointsLike some sort of WPMU DEV GodMindblowingly helpful memberLifetime member
Erstwhile founder
—
4th February 2009 (3 years ago)
#
Hi Guys,
I have uploaded the plugin and have entered the code as directed in the installation guidelines to make plugins only available to supporters but for some reason it doesn't appear to be working.
Oops, I didn't realize those instructions were there. Disabling the plugins the way we have on Edublogs requires heavily modifying the plugins page. That's not something I'm comfortable instructing premium members to do so we'll have to go a different route. I'll provide a plugin that removes the plugins page for non-supporter blogs.
As a feature request could access to various themes be built into the supporter interface or would I be better suited to trying the upgrades plugin?
That's a possibility. I should note though that other than bug fixes for this plugin, we'll be focusing on 2.7 compatibility issues for a while.
If I install this plugin how will it effect my current Bloggers?
That depends entirely on how you configure the plugin. If you just want to offer a quota upgrade then be sure to upload only the quota plugin. Read the installation instructions for more details.
6593 pointsLike some sort of WPMU DEV GodExceptionally helpfulLifetime member
Keeper of the Dark Chocolate
—
4th February 2009 (3 years ago)
#
Did we ever work out a system on Supporters get the additional file types to upload? I noticed that you mentioned that in passing on your wpmu.org article. Have to admit that would be a good feature for this plugin.
Oops, I didn't realize those instructions were there. Disabling the plugins the way we have on Edublogs requires heavily modifying the plugins page. That's not something I'm comfortable instructing premium members to do so we'll have to go a different route. I'll provide a plugin that removes the plugins page for non-supporter blogs.
Soem of us are using plugin commander to hide the plugin page, can you maybe get this plugin working with that one as well?
You should be able to change the quota per blogs in Site Admin > Blogs > Edit (default WPMU)
that never worked, just tested: I set the quota of a blog higher than the default, then check that blog's dashboard and it still displays the default quota there :-( didn't work out with the upgrades plugin either, I had to subscribe to one of the packages to get more upload space for the main blog too...
after upgrading the supporter plugin ( I just realized the date of publishing changed) I find out:
a) the problem with not saving the number of free days for each new blog works now
b) eaccelerator is acting weird, see screen shot http://screencast.com/t/alPB9zpPLYy it seems to chuck out the supporter_framework.php file the whole time :-(
anyone else running eaccelerator seeing this in the eaccelerator control panel?
7430 pointsLike some sort of WPMU DEV GodMindblowingly helpful memberLifetime member
Erstwhile founder
—
5th February 2009 (3 years ago)
#
Hi Ovidiu,
Soem of us are using plugin commander to hide the plugin page, can you maybe get this plugin working with that one as well?
We won't be integrating this plugin with the plugin commander. We'll basically just be providing simple example plugins for use with the Supporter Framework. If a member needs something more advanced like that they'll need to look into it.
How about this one?
What we've included is a basic quota plugin similar to the one we include with the Upgrades plugin. I'll look into this issue but can't guarantee anything.
b) eaccelerator is acting weird, see screen shot http://screencast.com/t/alPB9zpPLYy it seems to chuck out the supporter_framework.php file the whole time :-(
I think we're using APC on our servers. I honestly have no clue why eaccelerator is kicking it out. There really isn't any fancy code in that file. It may be due to the file size but that's just a guess.
this looks ok, but doesn't work. I assign a user a quota of 55MB and his dashboard still shows 50MB, after deleting the supporter plugin, his dashboard shows again 55MB!?
7430 pointsLike some sort of WPMU DEV GodMindblowingly helpful memberLifetime member
Erstwhile founder
—
6th February 2009 (3 years ago)
#
If you manually increase a blogs quota, the supporter quota plugin will ignore it. As I mentioned before, it's just a simple example plugin. Feel free to customize it to your needs.
[blockquote]Oops, I didn't realize those instructions were there. Disabling the plugins the way we have on Edublogs requires heavily modifying the plugins page. That's not something I'm comfortable instructing premium members to do so we'll have to go a different route. I'll provide a plugin that removes the plugins page for non-supporter blogs.[/blockquote]
6593 pointsLike some sort of WPMU DEV GodExceptionally helpfulLifetime member
Keeper of the Dark Chocolate
—
7th February 2009 (3 years ago)
#
Quick question. The Disable Post and Page writing. Is that what happens if you log in and are over the time limit? Just wondering about the usage of that feature.
The next development of this plugin may be directed to divide user right when using plugins and themes.
For example, I'd like to share a list of premium and free plugins/themes. So, free user only entitled to use the free plugin/theme. While premium member (paid member) can use the premium plugin/theme that we have set.
6593 pointsLike some sort of WPMU DEV GodExceptionally helpfulLifetime member
Keeper of the Dark Chocolate
—
9th February 2009 (3 years ago)
#
Should be able to do that already. Just do a check against is_supporter. We do something like that with Adsense widgets. If they have one of the upgrades, they get full use of the widget. If they don't, the host gets 20% (or whatever percentage) of the displays.
I am confused... Does this plugin need to be run in conjunction with upgrades plugin or is it its own seperate plugin? I have downloaded and installed the plugin and am not seeing all these wonderful features about themes and plugins that you are talking about?
I mentioned the plugin issue earlier and Andrew said that he would develop another plugin to disable the plugins for non-supporter blogs. The potential features of this plugin sound awesome and I think it is a must have but the installation I have doesn't do all the things you guys are talking about?!
6593 pointsLike some sort of WPMU DEV GodExceptionally helpfulLifetime member
Keeper of the Dark Chocolate
—
12th February 2009 (3 years ago)
#
I found an issue. If you have a user who is within their preliminary period, when you visit the Supporter page, it's giving you the "Unless you have canceled your subscription via PayPal, your supporter privileges will automatically be renewed." message. There's no option or link to actually subscribe or signup to continue the program.
I use the is_support function to control plugins like on edublogs, but you do have to edit plugins.php directly. But I like to show plugin that they are missing not being a supporter.
7430 pointsLike some sort of WPMU DEV GodMindblowingly helpful memberLifetime member
Erstwhile founder
—
13th February 2009 (3 years ago)
#
That's really the best way to "disable" the plugins as it does exactly what you said, shows them what they're missing out on. We just can't instruct users to make hacks like that though. We'd be up to our ears in support requests from people editing the wrong bit of code, etc.
Ho ho...
I need to wipe out other plugins that are conflict.
a list of conflict plugins that can not be used at the same time:
> upgrades
> pay to blog
> supporter
Unfortunately, among the three of the plugin above not once has not been meets my needs. Supporter plugin still needs further development to determine which plugins may be used by the user and free plugin which can be used only for the supporter. The interface to do this classification still darken.
I installed your new supporter version 1.0.1 with the plugins code but the plugins menu still shows up for users. Do I need to make any code changes to plugins.php in wordpress for this to work?
Yes, I am logged in as the main site admin for the main blog. I can see the plugin which is good.
When I log in as site admin (of the sub-blog) for the sub-blog, I can still see the plugin menu.
So, are you saying that this plugin doesn't block the plugin menu for site admins of sub-blogs? If so, then that is the problem for me. The site admins of sub-blogs are customers of mine and I don't want them to have access to the plugins menu unless they are paid supporters. Isn't that what this plugin is supposed to do?
If not, what code changes can I make to get this behavior?
Thanks. The new version worked. The plugins menu no longer appear in the sub-blog site admin's backend. I see there was a change to the filenames using a "-" instead of a "_". Not sure if that made a difference.
However, there is a new issue in that version, probably a quick and simple fix. Now, there is a new top menu on the top of the page that is blank (with just an arrow). When you click on it, there is a link to "Supporter" which would be ok if it went to the page where the user could upgrade to a Supporter subscription but instead, it shows the Supporter options page where a sub-blog admin can change the main admin settings. Can you remove that blank top menu?
7430 pointsLike some sort of WPMU DEV GodMindblowingly helpful memberLifetime member
Erstwhile founder
—
19th February 2009 (3 years ago)
#
Hiya,
I see there was a change to the filenames using a "-" instead of a "_". Not sure if that made a difference.
That's just me switching out underscores for dashes. There's a chunk of code that I use in almost every plugin and I spent some time to update that bit of code a few months ago. Plugins with underscores have the old code and plugins with dashes have the updated code. This plugin accidentally got named with underscores even though it has the updated code. So I just updated the filenames.
However, there is a new issue in that version, probably a quick and simple fix. Now, there is a new top menu on the top of the page that is blank (with just an arrow). When you click on it, there is a link to "Supporter" which would be ok if it went to the page where the user could upgrade to a Supporter subscription but instead, it shows the Supporter options page where a sub-blog admin can change the main admin settings. Can you remove that blank top menu?
I can't see the menu item on either of my test installs. Can you take a screenshot?
6593 pointsLike some sort of WPMU DEV GodExceptionally helpfulLifetime member
Keeper of the Dark Chocolate
—
20th February 2009 (3 years ago)
#
One of my clients raised a pair of issues.
- We would like the option to rename the "Supporter" name and call it something else.
- Leaving some plugins available to the non supporter would be nice. She has one of the anti scrapper plugins available to her clients under her plugin menu. I guess we could move that over to the mu-plugins directory and give it a turn on/off function.
And a reminder about being able to allow those within their free period to go ahead and pay for their supporter status instead of waiting to have that time period run out would be a plus.
edit: Also listing free supporter status, both as a grant and for beginning blogs, within the transaction table would be a plus.
7430 pointsLike some sort of WPMU DEV GodMindblowingly helpful memberLifetime member
Erstwhile founder
—
21st February 2009 (3 years ago)
#
Hiya,
- We would like the option to rename the "Supporter" name and call it something else.
This isn't one of the planned additions at this time. For now the best thing to do is to just run a find/replace. Should take less than ten minutes even inspecting each instance for issues.
- Leaving some plugins available to the non supporter would be nice. She has one of the anti scrapper plugins available to her clients under her plugin menu. I guess we could move that over to the mu-plugins directory and give it a turn on/off function.
Unless I've missed something in the plugin page code that's not possible without hacks. If someone can find a simple way to do this just let me know.
And a reminder about being able to allow those within their free period to go ahead and pay for their supporter status instead of waiting to have that time period run out would be a plus.
And a reminder about being able to allow those within their free period to go ahead and pay for their supporter status instead of waiting to have that time period run out would be a plus.
We'll look into this.
edit: Also listing free supporter status, both as a grant and for beginning blogs, within the transaction table would be a plus.
6593 pointsLike some sort of WPMU DEV GodExceptionally helpfulLifetime member
Keeper of the Dark Chocolate
—
21st February 2009 (3 years ago)
#
Not really sure what you mean here.
Meaning when the site admin gives a grant of supporter status, a record of such is made in the transaction database. Also when a blog is first given Supporter status when first created, a record is made in the transaction table.
7430 pointsLike some sort of WPMU DEV GodMindblowingly helpful memberLifetime member
Erstwhile founder
—
21st February 2009 (3 years ago)
#
Hiya,
Records are not added to the transactions table when either of those events happen. The transaction table is just there to keep track of PayPal transactions.
7430 pointsLike some sort of WPMU DEV GodMindblowingly helpful memberLifetime member
Erstwhile founder
—
21st February 2009 (3 years ago)
#
Ah, gotcha. Sorry, was a bit confused there! ;)
Unfortunately I won't be making that change as those events aren't actually transactions. That feature is only to help keep track of/look up PayPal transactions. Basically if a user whines about their blog not being upgraded you can look up the transaction without having to gather their info and find it in the PayPal system.
6593 pointsLike some sort of WPMU DEV GodExceptionally helpfulLifetime member
Keeper of the Dark Chocolate
—
21st February 2009 (3 years ago)
#
Basically if a user whines about their blog not being upgraded you can look up the transaction
Actually that's why I was suggesting it. In the case of a user whining about an upgrade that was giving for free either at the start of their blog or by the intervention of a site admin, there would be a record of it occurring.
- Leaving some plugins available to the non supporter would be nice. She has one of the anti scrapper plugins available to her clients under her plugin menu. I guess we could move that over to the mu-plugins directory and give it a turn on/off function.
Unless I've missed something in the plugin page code that's not possible without hacks. If someone can find a simple way to do this just let me know.
Seem like I suggest previous above. I want to a free user still using some free plugins.
6593 pointsLike some sort of WPMU DEV GodExceptionally helpfulLifetime member
Keeper of the Dark Chocolate
—
22nd February 2009 (3 years ago)
#
I guess if you get stuck, you can not use the "Hide the Plugins page" plugin, put the plugins you want for supporters elsewhere within their own subdirectory, and write a dirty and quickly mu-plugin where you do a check against is_supporter() and, if true, use an include to add in those plugins.
That'll probably work with the supporter themes as well.
That's just off the top of my head and three cups of coffee though. I know there's that recent trac ticket on assigning plugins that's still pending.
7430 pointsLike some sort of WPMU DEV GodMindblowingly helpful memberLifetime member
Erstwhile founder
—
22nd February 2009 (3 years ago)
#
Hi Guys,
I really need to point out that if you're looking to just make a handful of plugins work only on upgraded blogs then you might want to take a look at using the Upgrades plugin.
But when using Supporter -> Supporter, or the link on the bottom left of the Admin panel (http://domain/example1/wp-admin/supporter.php) it works properly and tells the Supporter when their privileges expire. Nothing else seems to fail - just this link. How might we hack the Admin topmost "Supporter" menu link to point to the working link?
1. If we have supporter installed can admin GIFT supporter status to certain people (so they don't have to pay)?
2. I think that answer to this is NO, but here is my question:
Can we configure supporter so that some plugins are available to all users, whereas others are only available to supporters. Or do I need a custom hack? If I need a custom hack, how hard would it be for an experienced programmer to do for me?
3. "supporter_write.php - Disables the "Write Post" and "Write Page" pages on non-supporter blogs - Note that the pages are never disabled for Site Admins"
I don't understand this feature. Why would anyone ever want a blog that would not allow them to write a page? It seems weird to allow people to create blogs but not allow them to create a single page unless they are a supporter. Am I missing something?
7430 pointsLike some sort of WPMU DEV GodMindblowingly helpful memberLifetime member
Erstwhile founder
—
18th March 2009 (3 years ago)
#
Hiya,
1. If we have supporter installed can admin GIFT supporter status to certain people (so they don't have to pay)?
You can extend blogs at "Site Admin > Supporter".
2. I think that answer to this is NO, but here is my question:
Can we configure supporter so that some plugins are available to all users, whereas others are only available to supporters. Or do I need a custom hack? If I need a custom hack, how hard would it be for an experienced programmer to do for me?
That's not a feature provided. An experienced WP developer should be able to help you out.
3. "supporter_write.php - Disables the "Write Post" and "Write Page" pages on non-supporter blogs - Note that the pages are never disabled for Site Admins"
I don't understand this feature. Why would anyone ever want a blog that would not allow them to write a page? It seems weird to allow people to create blogs but not allow them to create a single page unless they are a supporter. Am I missing something?
A lot of people want users to have to pay to blog.
6593 pointsLike some sort of WPMU DEV GodExceptionally helpfulLifetime member
Keeper of the Dark Chocolate
—
18th March 2009 (3 years ago)
#
Can we configure supporter so that some plugins are available to all users, whereas others are only available to supporters.
Actually that's how the upgrades plugin works. Download that and take a look at the included sample plugins. You'll note that before any of the add_actions are run, it looks to see if the user has the upgrade. Just do the same thing but do it against a check against is_supporter().
6593 pointsLike some sort of WPMU DEV GodExceptionally helpfulLifetime member
Keeper of the Dark Chocolate
—
19th March 2009 (3 years ago)
#
Two quick suggestions:
- I would like to see a message on the supporter page showing that if the support is already one, showing them when their time runs out.
- Also maybe a hook or a text area allowing the site admin to include their own message. (ie thanking them for upgrading, showing them a list of benefits for paying the bucks, etc.)
edit: For #2 there, I'd rather see a hook come to think about it. That way, you can include a check against supporter. If true, show them a thank you message, if no, show them a list of benefits. Does that make sense?
7430 pointsLike some sort of WPMU DEV GodMindblowingly helpful memberLifetime member
Erstwhile founder
—
19th March 2009 (3 years ago)
#
Hiya,
- I would like to see a message on the supporter page showing that if the support is already one, showing them when their time runs out.
Already one there.
- Also maybe a hook or a text area allowing the site admin to include their own message. (ie thanking them for upgrading, showing them a list of benefits for paying the bucks, etc.)
I am using the latest version, have uploaded the supporter-plugins.php to the correct directory, but I am not seeing an option to enable/disable plugins on the root site admin Supporters settings page and I am still seeing plugins logged in as a sub-site administrator non-supporter blog. I'm clueless at this point as to what's going on, but this is one of my last issues on my list before I can launch my site. Thanks for your plugins and help.
What kind of supporter badges do you use? It's not included in the plugin file, so I guess I need to make one myself. But isn't there any sample image files or psds?
6593 pointsLike some sort of WPMU DEV GodExceptionally helpfulLifetime member
Keeper of the Dark Chocolate
—
25th April 2009 (3 years ago)
#
Best bet would be to make your own. I know on my sites that use this plugin they use the site logo as a background and some sort of "I'm a supporter" message on top of that.
Responses (66)
Member — 4th February 2009 (3 years ago) #
I have uploaded the plugin and have entered the code as directed in the installation guidelines to make plugins only available to supporters but for some reason it doesn't appear to be working.
I am running mu 2.7
Founder & CEO — 4th February 2009 (3 years ago) #
I'll leave that bit up to Andrew (tomorrow) as I kinda hacked in the instructions for disabling plugins :)
Is everything else working OK?
Member — 4th February 2009 (3 years ago) #
everything else appears to be working alright. As a feature request could access to various themes be built into the supporter interface or would I be better suited to trying the upgrades plugin?
Member — 4th February 2009 (3 years ago) #
If I install this plugin how will it effect my current Bloggers?
I only want to set upload quota and want everybody who is existing on the platform to be able to continue to Blog with out bother
[Edit] is there any type of guidelines for this plugin?
Erstwhile founder — 4th February 2009 (3 years ago) #
Hi Guys,
Oops, I didn't realize those instructions were there. Disabling the plugins the way we have on Edublogs requires heavily modifying the plugins page. That's not something I'm comfortable instructing premium members to do so we'll have to go a different route. I'll provide a plugin that removes the plugins page for non-supporter blogs.
That's a possibility. I should note though that other than bug fixes for this plugin, we'll be focusing on 2.7 compatibility issues for a while.
That depends entirely on how you configure the plugin. If you just want to offer a quota upgrade then be sure to upload only the quota plugin. Read the installation instructions for more details.
Thanks,
Andrew
Keeper of the Dark Chocolate — 4th February 2009 (3 years ago) #
Did we ever work out a system on Supporters get the additional file types to upload? I noticed that you mentioned that in passing on your wpmu.org article. Have to admit that would be a good feature for this plugin.
Member — 5th February 2009 (3 years ago) #
Soem of us are using plugin commander to hide the plugin page, can you maybe get this plugin working with that one as well?
How about this one?
Member — 5th February 2009 (3 years ago) #
after upgrading the supporter plugin ( I just realized the date of publishing changed) I find out:
a) the problem with not saving the number of free days for each new blog works now
b) eaccelerator is acting weird, see screen shot http://screencast.com/t/alPB9zpPLYy it seems to chuck out the supporter_framework.php file the whole time :-(
anyone else running eaccelerator seeing this in the eaccelerator control panel?
Erstwhile founder — 5th February 2009 (3 years ago) #
Hi Ovidiu,
We won't be integrating this plugin with the plugin commander. We'll basically just be providing simple example plugins for use with the Supporter Framework. If a member needs something more advanced like that they'll need to look into it.
What we've included is a basic quota plugin similar to the one we include with the Upgrades plugin. I'll look into this issue but can't guarantee anything.
I think we're using APC on our servers. I honestly have no clue why eaccelerator is kicking it out. There really isn't any fancy code in that file. It may be due to the file size but that's just a guess.
Thanks,
Andrew
Member — 6th February 2009 (3 years ago) #
k, thx will follow the development of this plugin.
Member — 6th February 2009 (3 years ago) #
sorry to nag again, but I had a look at the supporter quota plugin:
this looks ok, but doesn't work. I assign a user a quota of 55MB and his dashboard still shows 50MB, after deleting the supporter plugin, his dashboard shows again 55MB!?
Erstwhile founder — 6th February 2009 (3 years ago) #
If you manually increase a blogs quota, the supporter quota plugin will ignore it. As I mentioned before, it's just a simple example plugin. Feel free to customize it to your needs.
Thanks,
Andrew
Member — 7th February 2009 (3 years ago) #
[blockquote]Oops, I didn't realize those instructions were there. Disabling the plugins the way we have on Edublogs requires heavily modifying the plugins page. That's not something I'm comfortable instructing premium members to do so we'll have to go a different route. I'll provide a plugin that removes the plugins page for non-supporter blogs.[/blockquote]
Is this available now?
Founder & CEO — 7th February 2009 (3 years ago) #
All in good time :) Andrew's enjoying a well deserved weekend!
Keeper of the Dark Chocolate — 7th February 2009 (3 years ago) #
Quick question. The Disable Post and Page writing. Is that what happens if you log in and are over the time limit? Just wondering about the usage of that feature.
thanks,
-drmike
Member — 9th February 2009 (3 years ago) #
The next development of this plugin may be directed to divide user right when using plugins and themes.
For example, I'd like to share a list of premium and free plugins/themes. So, free user only entitled to use the free plugin/theme. While premium member (paid member) can use the premium plugin/theme that we have set.
I believe that this feature will be more useful.
Keeper of the Dark Chocolate — 9th February 2009 (3 years ago) #
Should be able to do that already. Just do a check against is_supporter. We do something like that with Adsense widgets. If they have one of the upgrades, they get full use of the widget. If they don't, the host gets 20% (or whatever percentage) of the displays.
Member — 9th February 2009 (3 years ago) #
I am confused... Does this plugin need to be run in conjunction with upgrades plugin or is it its own seperate plugin? I have downloaded and installed the plugin and am not seeing all these wonderful features about themes and plugins that you are talking about?
I mentioned the plugin issue earlier and Andrew said that he would develop another plugin to disable the plugins for non-supporter blogs. The potential features of this plugin sound awesome and I think it is a must have but the installation I have doesn't do all the things you guys are talking about?!
Member — 10th February 2009 (3 years ago) #
Where do I place the ad code?
Founder & CEO — 10th February 2009 (3 years ago) #
Up to you, wherever you want :)
Personally I reckon between the post title and content is the best place.
Member — 11th February 2009 (3 years ago) #
Sorry, thanks, I was reading too into the directions I guess and thought the code went into the supporter_ads.php file. Makes sense now, thanks.
Member — 12th February 2009 (3 years ago) #
- Allows you to simply turn off areas of the site to users that aren't Supporters... for example, only supporters get Plugins!
I looked everywhere in admin but couldn't find this option. Am I missing something?
Founder & CEO — 12th February 2009 (3 years ago) #
Yep, we're going to be releasing a separate plugin that does this - my instructions weren't so great - it shouldn't be long now...
Keeper of the Dark Chocolate — 12th February 2009 (3 years ago) #
Is it going to be a check against is_supporter or something different?
Erstwhile founder — 12th February 2009 (3 years ago) #
Hi Guys,
I just uploaded a new version of the supporter plugin that contains the additional plugin to disable the plugins page on non-supporter blogs.
Thanks,
Andrew
Keeper of the Dark Chocolate — 12th February 2009 (3 years ago) #
Thanks.
Have to admit that I would like the option to restrict to specific types the file uploads.
I have a feeling though that the filter still isn't applied correctly. I know when I tried it, it was applied to user and not individual blogs.
Keeper of the Dark Chocolate — 12th February 2009 (3 years ago) #
Thinking about the WSA plugin. Is the way to go with that just a php check against is_supporter?
Keeper of the Dark Chocolate — 12th February 2009 (3 years ago) #
I found an issue. If you have a user who is within their preliminary period, when you visit the Supporter page, it's giving you the "Unless you have canceled your subscription via PayPal, your supporter privileges will automatically be renewed." message. There's no option or link to actually subscribe or signup to continue the program.
Hope this helps,
-drmike
Member — 13th February 2009 (3 years ago) #
I use the is_support function to control plugins like on edublogs, but you do have to edit plugins.php directly. But I like to show plugin that they are missing not being a supporter.
Erstwhile founder — 13th February 2009 (3 years ago) #
That's really the best way to "disable" the plugins as it does exactly what you said, shows them what they're missing out on. We just can't instruct users to make hacks like that though. We'd be up to our ears in support requests from people editing the wrong bit of code, etc.
Thanks,
Andrew
Member — 13th February 2009 (3 years ago) #
hmm.. I missed a file on Supporters menu
the link pointed to http://mydomain.com/wp-admin/upgrades.php
where is it?
Erstwhile founder — 13th February 2009 (3 years ago) #
Hiya,
"upgrades.php" is a file from the Upgrades plugin, not the Supporter plugin.
Thanks,
Andrew
Member — 14th February 2009 (3 years ago) #
Ho ho...
I need to wipe out other plugins that are conflict.
a list of conflict plugins that can not be used at the same time:
> upgrades
> pay to blog
> supporter
Unfortunately, among the three of the plugin above not once has not been meets my needs. Supporter plugin still needs further development to determine which plugins may be used by the user and free plugin which can be used only for the supporter. The interface to do this classification still darken.
Member — 17th February 2009 (3 years ago) #
I installed your new supporter version 1.0.1 with the plugins code but the plugins menu still shows up for users. Do I need to make any code changes to plugins.php in wordpress for this to work?
Erstwhile founder — 17th February 2009 (3 years ago) #
Which version of wpmu are you running?
Thanks,
Andrew
Member — 17th February 2009 (3 years ago) #
2.7
I see the Supporter option under Site Admin and also see the Supporter Menu tab for users but the plugins menu still also shows up for the users.
Erstwhile founder — 17th February 2009 (3 years ago) #
Hiya,
Are you logged in as a site admin or on the main blog? It's never hidden for the main blog or site admins.
Thanks,
Andrew
Member — 17th February 2009 (3 years ago) #
Yes, I am logged in as the main site admin for the main blog. I can see the plugin which is good.
When I log in as site admin (of the sub-blog) for the sub-blog, I can still see the plugin menu.
So, are you saying that this plugin doesn't block the plugin menu for site admins of sub-blogs? If so, then that is the problem for me. The site admins of sub-blogs are customers of mine and I don't want them to have access to the plugins menu unless they are paid supporters. Isn't that what this plugin is supposed to do?
If not, what code changes can I make to get this behavior?
Thanks for your help Andrew,
Jim
Erstwhile founder — 18th February 2009 (3 years ago) #
Hiya,
I uploaded a new version of the supporter plugin a few hours ago. See if it resolves the problem for you.
Thanks,
Andrew
Member — 19th February 2009 (3 years ago) #
Thanks. The new version worked. The plugins menu no longer appear in the sub-blog site admin's backend. I see there was a change to the filenames using a "-" instead of a "_". Not sure if that made a difference.
However, there is a new issue in that version, probably a quick and simple fix. Now, there is a new top menu on the top of the page that is blank (with just an arrow). When you click on it, there is a link to "Supporter" which would be ok if it went to the page where the user could upgrade to a Supporter subscription but instead, it shows the Supporter options page where a sub-blog admin can change the main admin settings. Can you remove that blank top menu?
Thanks,
jim
Erstwhile founder — 19th February 2009 (3 years ago) #
Hiya,
That's just me switching out underscores for dashes. There's a chunk of code that I use in almost every plugin and I spent some time to update that bit of code a few months ago. Plugins with underscores have the old code and plugins with dashes have the updated code. This plugin accidentally got named with underscores even though it has the updated code. So I just updated the filenames.
I can't see the menu item on either of my test installs. Can you take a screenshot?
Thanks,
Andrew
Keeper of the Dark Chocolate — 20th February 2009 (3 years ago) #
One of my clients raised a pair of issues.
- We would like the option to rename the "Supporter" name and call it something else.
- Leaving some plugins available to the non supporter would be nice. She has one of the anti scrapper plugins available to her clients under her plugin menu. I guess we could move that over to the mu-plugins directory and give it a turn on/off function.
And a reminder about being able to allow those within their free period to go ahead and pay for their supporter status instead of waiting to have that time period run out would be a plus.
edit: Also listing free supporter status, both as a grant and for beginning blogs, within the transaction table would be a plus.
Erstwhile founder — 21st February 2009 (3 years ago) #
Hiya,
This isn't one of the planned additions at this time. For now the best thing to do is to just run a find/replace. Should take less than ten minutes even inspecting each instance for issues.
Unless I've missed something in the plugin page code that's not possible without hacks. If someone can find a simple way to do this just let me know.
We'll look into this.
Not really sure what you mean here.
Thanks,
Andrew
Keeper of the Dark Chocolate — 21st February 2009 (3 years ago) #
Meaning when the site admin gives a grant of supporter status, a record of such is made in the transaction database. Also when a blog is first given Supporter status when first created, a record is made in the transaction table.
Erstwhile founder — 21st February 2009 (3 years ago) #
Hiya,
Records are not added to the transactions table when either of those events happen. The transaction table is just there to keep track of PayPal transactions.
Thanks,
Andrew
Keeper of the Dark Chocolate — 21st February 2009 (3 years ago) #
I realize that. I was suggesting that it may be a good idea to add records for those other occasions. :)
Erstwhile founder — 21st February 2009 (3 years ago) #
Ah, gotcha. Sorry, was a bit confused there! ;)
Unfortunately I won't be making that change as those events aren't actually transactions. That feature is only to help keep track of/look up PayPal transactions. Basically if a user whines about their blog not being upgraded you can look up the transaction without having to gather their info and find it in the PayPal system.
Thanks,
Andrew
Keeper of the Dark Chocolate — 21st February 2009 (3 years ago) #
Actually that's why I was suggesting it. In the case of a user whining about an upgrade that was giving for free either at the start of their blog or by the intervention of a site admin, there would be a record of it occurring.
Member — 22nd February 2009 (3 years ago) #
Seem like I suggest previous above. I want to a free user still using some free plugins.
Keeper of the Dark Chocolate — 22nd February 2009 (3 years ago) #
I guess if you get stuck, you can not use the "Hide the Plugins page" plugin, put the plugins you want for supporters elsewhere within their own subdirectory, and write a dirty and quickly mu-plugin where you do a check against is_supporter() and, if true, use an include to add in those plugins.
That'll probably work with the supporter themes as well.
That's just off the top of my head and three cups of coffee though. I know there's that recent trac ticket on assigning plugins that's still pending.
Erstwhile founder — 22nd February 2009 (3 years ago) #
Hi Guys,
I really need to point out that if you're looking to just make a handful of plugins work only on upgraded blogs then you might want to take a look at using the Upgrades plugin.
Thanks,
Andrew
Member — 17th March 2009 (3 years ago) #
There seems to be a problem with the Admin Menu for Supporter.
Using the link at the *very* top of the Admin panel (http://domain/example1/wp-admin/admin.php?page=supporter.php), WPMU comes back with "cannot load supporter.php".
But when using Supporter -> Supporter, or the link on the bottom left of the Admin panel (http://domain/example1/wp-admin/supporter.php) it works properly and tells the Supporter when their privileges expire. Nothing else seems to fail - just this link. How might we hack the Admin topmost "Supporter" menu link to point to the working link?
Erstwhile founder — 17th March 2009 (3 years ago) #
Hiya,
I'm just going to have to update the plugin to remove the link from the admin bar.
Unfortunately the admin bar was just poorly implemented. It gets way too crowded with just a few plugins tossed in.
Thanks,
Andrew
Keeper of the Dark Chocolate — 17th March 2009 (3 years ago) #
You may want to keep an eye on the mu trac. There's been about a dozen open tickets on that very issue.
Member — 18th March 2009 (3 years ago) #
Two Quick Questions, Please
1. If we have supporter installed can admin GIFT supporter status to certain people (so they don't have to pay)?
2. I think that answer to this is NO, but here is my question:
Can we configure supporter so that some plugins are available to all users, whereas others are only available to supporters. Or do I need a custom hack? If I need a custom hack, how hard would it be for an experienced programmer to do for me?
3. "supporter_write.php - Disables the "Write Post" and "Write Page" pages on non-supporter blogs - Note that the pages are never disabled for Site Admins"
I don't understand this feature. Why would anyone ever want a blog that would not allow them to write a page? It seems weird to allow people to create blogs but not allow them to create a single page unless they are a supporter. Am I missing something?
Erstwhile founder — 18th March 2009 (3 years ago) #
Hiya,
You can extend blogs at "Site Admin > Supporter".
That's not a feature provided. An experienced WP developer should be able to help you out.
A lot of people want users to have to pay to blog.
That feature is also optional.
Thanks,
Andrew
Keeper of the Dark Chocolate — 18th March 2009 (3 years ago) #
Actually that's how the upgrades plugin works. Download that and take a look at the included sample plugins. You'll note that before any of the add_actions are run, it looks to see if the user has the upgrade. Just do the same thing but do it against a check against is_supporter().
Erstwhile founder — 18th March 2009 (3 years ago) #
Didn't think about that!
Thanks,
Andrew
Keeper of the Dark Chocolate — 19th March 2009 (3 years ago) #
Two quick suggestions:
- I would like to see a message on the supporter page showing that if the support is already one, showing them when their time runs out.
- Also maybe a hook or a text area allowing the site admin to include their own message. (ie thanking them for upgrading, showing them a list of benefits for paying the bucks, etc.)
edit: For #2 there, I'd rather see a hook come to think about it. That way, you can include a check against supporter. If true, show them a thank you message, if no, show them a list of benefits. Does that make sense?
Erstwhile founder — 19th March 2009 (3 years ago) #
Hiya,
Already one there.
I'll look into this one.
Thanks,
Andrew
Keeper of the Dark Chocolate — 19th March 2009 (3 years ago) #
Hmmm, strange. Must have been looking at a different blog. I thought there was as well but didn't see one so I pointed it out. Oh well.
Member — 27th March 2009 (3 years ago) #
I am using the latest version, have uploaded the supporter-plugins.php to the correct directory, but I am not seeing an option to enable/disable plugins on the root site admin Supporters settings page and I am still seeing plugins logged in as a sub-site administrator non-supporter blog. I'm clueless at this point as to what's going on, but this is one of my last issues on my list before I can launch my site. Thanks for your plugins and help.
Member — 27th March 2009 (3 years ago) #
Nevermind, it was just an incompatibility with the Plugin Commander. Thanks!
Member — 25th April 2009 (3 years ago) #
What kind of supporter badges do you use? It's not included in the plugin file, so I guess I need to make one myself. But isn't there any sample image files or psds?
Keeper of the Dark Chocolate — 25th April 2009 (3 years ago) #
Best bet would be to make your own. I know on my sites that use this plugin they use the site logo as a background and some sort of "I'm a supporter" message on top of that.
Founder & CEO — 27th April 2009 (3 years ago) #
Here's ours :)
http://fesrlc.edublogs.org/wp-content/supporter_badge.gif
Become a member