Installing & Configuring our Beaver Builder Add-on

This documentation will show you how to install and use the Beaver Builder add-on for MemberPress which is available on all MemberPress plans.

Installation:

To install the Beaver Builder add-on, you can go to MemberPress menu and click on the green Add-ons link.

Next you will scroll down and find the Beaver Builder add-on. Then click on the Install Add-on button. This will automatically install and activate the add-on.

You will also need to install the Beaver Builder plugin. The integrations works with both the Lite version and the standard version of Beaver Builder.

Configuration:

Once you have both the Beaver Builder installed and the Beaver Builder plugin installed and active, you can go to the content you would like to protect content on and launch Beaver Builder:

Once you have added the content to a page, post, etc. you will want to create a rule in MemberPress > Rules page so that you can protect it: Rules Overview.

After creating a rule, you can go back to the content and click on the Row Settings and then click on the MemberPress tab: 

Then you can set the MemberPress Rule to the rule that you created earlier so that the content will be protected. Most likely the type of rule you will want to use is Partial so that you can protect different parts of the page, post, etc.

Once the rule is selected, you will then want to choose from the dropdown for the Unauthorized Content field. You can choose from Default, Hide, or Display Message.

Default: This option shows your default unauthorized message which can also include the login page.

Hide: This option hides the content from unauthorized views so that no content is shown when viewing the content.

Display Message: This option allows you to show a custom unauthorized message. You will need to type in your custom message in the Custom Message field below the Unauthorized Content field.

Click save and your content should now be protected from unauthorized viewers.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.