• 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 8 years, 5 months ago by Dot 07. Reason: Developers didn't follow through with making the free version multisite compatible
Viewing 15 replies - 1 through 15 (of 20 total)
  • Plugin Author Justin Busa

    (@justinbusa)

    Hey Dot 07,

    Thanks for your candid review. It’s not too often that we see real feedback in negative reviews in the repo forums, so that is much appreciated.

    We talked about it and we think the lite version should support multisite. If someone installs it from the repo in their dashboard, it should just work, regardless of what version of WordPress they are on.

    We never intentionally wrote it to be incompatible with multisite. We actually had to write code to make it compatible with multisite. The reason that never made it into the lite version is because the lite version is a fork of our standard paid version that doesn’t include the multisite support code.

    Since the paid versions came before the lite version was in the repo, it never occurred to us to include the multisite support code until now.

    We’re not planning a new release of the lite version for another week or two, but when we do, we’ll make sure to include the multisite support code. In the meantime, it would be awesome if you could change your review to reflect our response, but no worries if not. We appreciate the feedback.

    Justin

    Thread Starter Dot 07

    (@dot07)

    Being I use multisite almost exclusively, I wouldn’t be able to provide a modification of my review without actually having tried the plugin on multisite.

    Since the version I am reviewing still doesn’t support multisite, there wouldn’t be an “in the meantime” adjustment. I will, however, install the free version again and wait for the update to be released.

    Presuming it is as good (for me) as those who praise it say it is, then I will be most happy to change the review and the rating. So, in the meantime that is the best I can do.

    Plugin Author Justin Busa

    (@justinbusa)

    Sounds good! I’m looking forward to having you try out Beaver Builder ?? I’ll be sure to post back here when the update is live.

    Thread Starter Dot 07

    (@dot07)

    I appreciate that. Thanks

    Plugin Contributor WebMan Design | Oliver Juhas

    (@webmandesign)

    Hi guys,

    Just stumbled upon this review and the issue discussed.

    @dot 07
    I’ve build a plugin called WebMan Amplifier which actually allows enabling Beaver Builder Lite Version even within WP multisite environment. But you need to enable WebMan Amplifier plugin first. There is a chance that it will work with any theme though the plugin was primarily created for theme developers. If you would like to test it I suggest using one of my themes, such as Auberge.

    @justin Busa
    Great to hear you will support multisite directly in Lite Version! You are really the best guys! Thanks for that!

    Regards,

    Oliver

    Plugin Author Justin Busa

    (@justinbusa)

    Thanks, Oliver! Really an oversight on our part going from premium to the repo. That update should be out very soon ??

    Justin

    Plugin Author Justin Busa

    (@justinbusa)

    Hey Dot 07,

    We just pushed version 1.6.4 that includes multisite support for the lite version. We’re looking forward to having you try Beaver Builder!

    Thanks,
    Justin

    Plugin Contributor WebMan Design | Oliver Juhas

    (@webmandesign)

    Very cool, Justin! Thank you for the plugin update!

    Thread Starter Dot 07

    (@dot07)

    If you reread my review, you will see I have adjusted it. And you made the update within the time you suggested. Thank you very much.

    Plugin Author Justin Busa

    (@justinbusa)

    @dot07 thanks so much! ?? We’re always open to feedback on how we could improve, so don’t hesitate to let us know if there is anything else you run into.

    @webmandesign you’re welcome! ??

    Plugin Contributor RobbyMcCullough

    (@robbymccullough)

    All right! Thanks @dot07 for the original suggestion and for updating the review. ??

    vamonos

    (@vamonos)

    Don’t you think that 200 bugs are a bit too much to get your PRO-plugin with multisite-support?
    Someone downloads the Lite-Version for free, test it on his multisites..think it’s useful.. and then he have to pay 200 bugs to get “Full”.
    I you choose the “Standard”, you will pay 100 bugs, but you also will loose the multisite-functionality…??

    Plugin Contributor RobbyMcCullough

    (@robbymccullough)

    Hey Vamonos! I saw your message come through on my phone, and the part that caught my eye was the “200 bugs” part. Scared me, lol!

    We tried to make it very clear on our pricing page that the Standard package doesn’t include multisite functionality, so hopefully there’s no confusion there.

    Our pricing is based on our ability to maintain a sustainable business, provide excellent support, and continue developing new features!

    We look at most of our features as “time savers.” Most things that are doable in the Pro/Standard versions would be doable with the lite version of Beaver Builder, but it will save you a lot of time using the premium features.

    Again, we’re making some educated assumptions here, but most folks running a multisite network presumably aren’t “beginner” or “hobbyist” WordPress users. That was some of the reasoning behind the pricing decision there.

    Hope that helps clear it up a bit. Happy to expand on that if you have any other questions.

    Thread Starter Dot 07

    (@dot07)

    Hi vamonos and RobbyMcCullough,

    So, since you have chosen to converse in my review, I find it interesting that the logic being used here is based on the presumption that multisite users are not beginners or hobbyists. Therefore, (I must make some of my own “educated assumptions”) the developers of this plugin believe multisite compatibility should be charged for because, if a website builder (developer) isn’t a novice they should pay for the resources they use.

    I would call your attention to the fact that many plugin and theme developers use a model that promotes both free and paid support rather than to over charge for what many people believe should be reasonable and more often free code. (Not necessarily my point of view).

    It troubles me when I see someone take advantage of users of a configuration which is becoming more widely known in this “Free” platform of WordPress, which is called “multisite”.

    I have to tell you, I didn’t begin with multisite as an experienced or professional user of WordPress. I was, at the time a novice (a few years ago). My problem was, I just got tired of poorly coded plugins that created conflicts if they ran under the same site configuration with other plugins. After some time of learning about multisite, I chose to use it more often than not for multiple reasons.

    The choice to require a large investment in a single plugin to run it in the multisite environment is (in my opinion) the choice to scalp WordPress users. And that is an opinion shared by a number of people.

    Having said all of that, I have chosen not to use this plugin because of the logic used by these developers. And there is the fact that a free plugin hosted here on www.remarpro.com does just fine with multisite.

    I don’t make it a practice of giving links to other plugins, but anyone doing a search for page builders or similar keywords will take them to multiple options. And some of them are completely free.

    And, please, if you have a review about this plugin (the free version) please take the time to start one of your own. Okay, vamonos?

    Plugin Contributor RobbyMcCullough

    (@robbymccullough)

    Hey Dot! Thanks for sharing your opinions. I’ll be the first one to admit that I’m not always right with my assumptions! =) Just like the first time around, hearing your thoughts and opinions is making me think twice. Thanks for taking the time to write them out.

    FWIW, multisite configuration introduce more potential conflicts and they can be more time consuming on our end to provide support for. Multisite installs generally are running multiple themes and are often are using the domain mapping plugin to run each site on a separate domain. This makes it very difficult to have a proper staging/development environment, and it also makes it very difficult for us to recreate and debug issues.

    I really don’t want you to think we set our pricing in an attempt to “scalp” WordPress users. That’s not how we run our business. Along with the thought that many multisite users put a high value on their time, quite frankly, multisite support costs us more.

    Happy to chat more about it. Feel free to shoot us an email, too. =)

    @vamanos, we’d be happy to continue the discussion, but let’s go ahead and do it on a different channel. Feel free to shoot us an email: [email protected].

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