Limit user site creation and integrate with Membership and/or Pro Sites

0

Greetings,

I am setting up a premium level in my test network using pro sites. I want to limit this premium level to being able to only create up to 5 websites in the network. I don’t see an option for that in pro sites. How can I do that?

thanks

  • Patrick Cohen
    • Technical Docs Wrangler

    Hi @Danny

    That cannot be done with Pro Sites as it designed to enable/restrict features per site.

    What you are trying to accomplish requires restricting capabilities of a user role.

    That is beyond the scope of this plugin, sorry.

    The only one I’ve found (there may be more though) is this one:

    http://wordpress.org/plugins/limit-blogs-per-user/

    Although not updated lately, it does appear to work according to this post:

    http://buddydev.com/buddypress/limit-blogs-per-user-plugin-for-wpmu/#comment-221339

  • Danny
    • The Incredible Code Injector

    Can you add this feature? this seems to me to be a pretty standard requirement that most networks would want to do. Does EduBlog or WPMU Dev limit the number of sites that can be created for a level? If so, how?

    thanks

  • Patrick Cohen
    • Technical Docs Wrangler

    Hi again @DannyDanny

    It really wouldn’t make sense to add that to Pro Sites because the plugin is designed to enable your users to upgrade their sites, and it acts individually per site.

    This would perhaps be a feature more suited to the Membership plugin as it acts at the user level, and grants or restricts their capabilities.

    Or maybe even a standalone plugin that could integrate with either Membership or Pro Sites (or both) if they’re active on a site.

    Hmm… it is an interesting idea.

    How about I move this topic to the Features & Feedback forum to give it more exposure in the community and maybe drum up some discussion. The more member support a feature request gets, the more motivated we get to develop it. :slight_smile:

    I also modified the title to pique interest in the feature :slight_smile:

  • Danny
    • The Incredible Code Injector

    Thanks. From my perspective it should be a pro sites function since pro sites is used to assign available functionality to different levels, ie plugns and themes. I don’t want users to be able to create unlimited sites but they need to be able to create more than one for the cost of a premium network membership. As I understand this so far, network levels controlled by Pro Sites are different than Memberships controlled by the Membership plugin on my primary network site. right?

    It seems logical that this could be function with both pro sites and membership as you suggest.

    thanks

  • Patrick Cohen
    • Technical Docs Wrangler

    @Danny

    There still appears to be a bit of confusion around this issue. Let me see if I can clarify a bit better.

    As I understand this so far, network levels controlled by Pro Sites are different than Memberships controlled by the Membership plugin on my primary network site. right?

    That is correct. Pro Sites enables users to upgrade individual sites (that they have created) to paid packages with additional features and functionality.

    The Membership plugin has nothing to do with their sites, as it only restricts or grants access to content that is directly available on the site that Membership is active on.

    You can however, make Membership a premium plugin that can be included in a Pro Site upgrade package. So users who do upgrade their site can create their own membership site in your network. The access levels and subscription plans they create on their site would apply only to content directly available on their site. Cool huh?

    pro sites is used to assign available functionality to different levels, ie plugns and themes

    That part of the statement is correct. Pro Sites is used to assign functionality to different levels, but only for the site that the user actually upgrades.

    I don’t want users to be able to create unlimited sites but they need to be able to create more than one for the cost of a premium network membership.

    There you have actually touched upon my main point. What we are discussing is granting or restricting the user’s capabilities (site creation) depending on their premium membership level on the main site of your network.

    I hope this helps clear up the differences between Pro Sites and Membership. :slight_smile:

  • Danny
    • The Incredible Code Injector

    No it doesn’t clear it up. So, pro sites and membership are not integrated at all. Is that correct? When someone signs up for a pro site, they are not added to membership on my primary site. That doesn’t make sense. It sound like I have to have two memberships for members: one is network level for pro sites to restrict access to plugins, themes and other functionality; and the other is membership level on the primary network site where I can restrict access to content on that site. Access levels for those two are unrelated.

    I don’t like how this works, or doesn’t work in this case. The primary site IS the membership site for my network. So for my primary site, pro sites and membership should be closely integrated so that someone can sign up for a pro site and become a network member, managed from my primary site. For all other member sites on the network, pro sites should not be integrated at all since the membership plugin is a separate instance for each member site.

    I don’t see how this issue has not been raised countless times before now. Or, I am completely misunderstanding this functionality.

    Let me rephrase this and maybe you can direct me to a solution.

    I want visitors to come to my site, sign up for a pro site membership, be limited in how many sites they can create under that membership as well as restrict access to themes and plugins. They should only have to sign up once and also be a member of my primary site, which is the main website for the entire network and where there may be additional restrictions on site content depending on the membership level. Does that make sense. Seems like a pretty standard way to do this.

    One more thing. It seems to me that pro sites should use the same access levels used by membership to control access to themes, plugins, etc. And it doesn’t work that way.

    thanks for your help. I am still in test mode on a test network learning how to use everything but I am burning daylight here to get this going in a production mode.

    Big Smile

  • Patrick Cohen
    • Technical Docs Wrangler

    @Danny

    One more thing. It seems to me that pro sites should use the same access levels used by membership to control access to themes, plugins, etc. And it doesn’t work that way.

    That is correct. That type of intimate integration is not possible at the moment.

    It is however a much requested feature, and our dev team is investigating the best way to code that integration to ensure compatibility with future updates, feature releases, etc.