Skip to main content
Memberful is compatible with almost all themes, page builders, and WordPress plugins. However, once in a while, something just doesn’t want to play nicely. Learn about known incompatible themes, page builders, and plugins, as well as using WordFence, the Advanced Custom Fields (ACF) plugin or Memboroni theme. In this help doc:

​
Known incompatible themes and page builders

Most WordPress themes and page builders are compatible with Memberful. The only requirement is that they must present post and page content using the default WordPress content function. When that isn’t used, the theme or page builder won’t work with the Memberful WordPress plugin.
  • Avia
  • BuddyBoss
  • Oxygen
  • SiteOrigin
  • Thrive
  • Themify
  • Uncode
Even if a theme isn’t compatible with Memberful, you should be able to keep specific pages “theme-less” so that they can work with our plugin. The tradeoff would be that these pages might look and behave differently from the rest of your site. Enabling the creation of these types of pages on a site might require a bit of development work depending on the theme, but some themes like Elementor have this built in.

​
Known incompatible plugins

  • Google Captcha plugin
  • Sucuri Security

​
Using the ACF plugin or Memberoni theme

You can use our Restrict Access tool and memberful_can_user_access_post() in your template file to check if a user should have access to a post. Based on that, you can decide if you want to show them custom content. 
if(memberful_can_user_access_post(get_current_user_id(), $post->ID)) {
  // show content
} else {
  // show something else
}

​
Using the Wordfence plugin

If you’re using Wordfence you might run into some issues with Memberful, although there are ways to make it work properly. Here are some issues that often happen due to WordFence:
  • Your members see a message that says “Your access to this site has been temporarily limited by the site owner”.
  • You receive a “Problem with your WordPress connection” email (although this can happen for other reasons).
Here are two suggestions from the Wordfence support forum which may help:
  • Highlight one of the blocked requests in the live activity log and flag it as safe.
  • Switch to the Learning Mode and test the endpoint: The firewall will “learn” this pattern and cease the blocking activity.
If that doesn’t help, feel free to reach out to us and we’ll do our best to help. Related help doc:
⌘I