Support » Plugin: WordPress Page Builder - Beaver Builder » Revised review (DOWN) Why no multisite compatibility?

  • Hi there,

    Again, revised this review. Having seen the recent critique of this plugin by Pippin Williams, and his noting the issue with multisite, it seems the developers chose not to provide multisite functionality after all.

    Multisite is part of core WordPress. Penalizing those who choose to use multisite is just the wrong way to market. I don’t support plugins that charge to have multisite functionality.

    Thank You !!!

    • This topic was modified 2 years, 6 months ago by  Dot 07. Reason: Developers didn't follow through with making the free version multisite compatible
Viewing 5 replies - 16 through 20 (of 20 total)
  • When I talk about WordPress Multisite configuration. I talk of the WordPress Multisite configuration. That is without third party plugins which enable domain mapping. There is a significant difference between the two.

    I realize the complications of multi-network plugins and domain mapping plugins. That is customization of multisite and is not what WordPress default types of Multisite are.

    So, you are talking about multiple WordPress sites vs WordPress Multisite. Multisite is contained on one domain. It is a configuration of one site which dynamically creates multiple sites via db manipulation. Very different from your example.

    One way many developers get over their fear of people using their plugins and themes on configurations which involve multiple websites is to require the plugin or theme to be used on one domain if it is to support WordPress Multisite. That’s about all I have to say on that.

    Making a distinction in your mind and in practice between what you described and what default WordPress Multisite is would probably help with your concerns about those conflicts.

    Why does the paid (Standard) version not include multi-site compatibility, but the free (Lite) version includes it?

    Multi-site functionality is a core feature of WordPress and should be included in all fairness, especially in a premium plugin (even if it’s the lowest tier).

    Paying double the price just for an additional Class file seems unfair…

    Are you planning on including it in further updates for your Standard version?

    Edit: I’ve re-read the previous posts and see now why it is that much more expensive when it comes to multi-site; it’s all because of the support. Then why not include multisite in the Standard version but with no support? That way, all versions of the plugin will allow multisite but only the highest tiers will include support for it. That way, everyone wins? Besides, the assumption was that only advanced users install multisites, so they probably wouldn’t need support for it. Everybody happy.

    The unfortunate part about this and many other projects is the fact that the developers themselves don’t seem to fully understand multisite as a core feature of WordPress.

    I refuse to support anyone who doesn’t include multisite functionality in all of their versions. And I recommend those who use multisite to refuse to support such projects.

    Multisite is a part of the core of WordPress. Therefore, punishing people by forcing them to pay (in this case outrageously) for utilizing it warrants protest. IMHO

    There is nothing wrong with WordPress developers offering multiple versions of a theme or plugin. Even though it might seem unfair, it’s totally understandable. They run a business and they gotta make a profit. Supporting multi-site is a tedious task because it requires an elaborate workflow to resolve issues, which takes up a lot of resources.

    However, in my opinion, such developers are shooting themselves in their own foot. Limiting a theme or plugin will only frustrate users. Create enough frustration and dissatisfaction and they risk someone else forking their theme or plugin. Just like WordPress themselves forked b2/cafelog or when WooCommerce forked Jigoshop, open source levels out the playing field and optimizes the quality of the software.

    There is a better way to approach this problem (which is a business problem at its roots) and that is to offer the theme/plugin with all the features, but with different tiers of support. That way it will attract more users (more purchases) and when the lowest tier users will demand support for a multisite installation they will be required to upgrade to the next tier.

    Or perhaps another simpler way with much less effort for Beaver Builder would be to publish a tutorial (that breaks the support/upgrade warranty) on how to add multisite functionality onto the Standard version. Here, I can help out:

    Step 1) Download the Lite version from
    Step 2) Copy the classes/class-fl-builder-multisite.php file onto your wp-content/bb-plugin/classes folder.
    Step 3) Add the following code in your wp-content/bb-plugin/fl-builder.php file:
    require_once 'classes/class-fl-builder-multisite.php';

    Perhaps this simple modification can be forked onto an independent plugin that will not break further updates of Beaver Builder?


    Since I was reviewing the free version of this plugin, I think I will refrain from going further than I have. I hope your suggestion helps someone.

    Since the free version does support multisite now, I have no further issue with it. Further critiquing the business model here would be pushing the limit on what WordPress allows.

    I will say this, I wouldn’t pay for something I can find free alternatives for on that do as much or more.

Viewing 5 replies - 16 through 20 (of 20 total)
  • The topic ‘Revised review (DOWN) Why no multisite compatibility?’ is closed to new replies.