Chad Bush

I’m seeing this error on dozens of client sites, and they think there’s an error. Please fix ASAP.

Hi @lopo,

Thank you! I’ll change my star rating and update my review. It’s great to see such responsive attention from plugin developers.

Hi @lopo that’s great news! I’ll revise my star rating when that’s done. Thanks again for providing all this useful functionality in a free plugin.

I have the current version of Members on an all-current install, and this forced ad still shows on EVERY block in the editor for all users.

As soon as I started seeing this obnoxious up-sell, I immediately deactivated the Members plugin in all 100 of my clients’ websites. Fortunately, I can activate the plugin, set user roles as needed, then deactivate to avoid this forced advertising that’s confusing to clients who don’t have any desire nor need for restricted content at all.

This has already proven extra confusing for clients who already run Restrict Content Pro or some other non-MemberPress membership plugin. The extra, unwanted up-sell competes with the legitimate restriction controls and is totally unacceptable.

MemberPress, you’ve got a great core product and it’s a shame to see this sort of lowball tactics in this wonderful plugin of which you’ve taken ownership. I’m grateful that you’ve taken on Justin’s Members plugin with plans to continue expanding and improving it. It’s been part of my dev toolkit for years. But I’m disappointed and a bit shocked that a company that produces such good stuff would stoop to this level.

Unless this Permissions setting is removed from the Block controls for sites that are not using any add-on functionality, I’ll keep deactivating Members on production sites and/or including CSS to hide this (I don’t like having to resort to such hacky tactics). Bummer.

• This reply was modified 4 years, 7 months ago by Chad Bush. Reason: Added an additional point

I had this problem, and clearing the cache in the browser didn’t fix it. But the sites I’ve had the problem on use a CDN, and after clearing that cache, then the browser’s again, the problem has resolved itself. It looks like a JS function in this version of the plugin got a new name, and if the browser is trying to load the cached version it throws an error and the Tour and Update notifications don’t get dismissed.

The issue in this post is discussed in more useful detail here: https://www.ads-software.com/support/topic/start-tour-bug?replies=23#post-7056126

In that post, the plugin authors have joined the conversation and things are being resolved.

I’ve found that the solution is to clear the cache — any server-side caching and CDN cache needs to be cleared as well as the browser cache. After that, the problem is resolved.

Thank you for being on top of this! I had a hunch it might be a problem at www.ads-software.com, but I wanted to bring it up just in case nobody else did.

Thank you for this fantastic plugin!

Greetings @daveshine,

I just noticed the same error. I’m using the plugin on a single site, and the error only appears when I uncheck the Help, Documnetation and FAQ option in the plugin’s settings. The error disappears if I re-check that option, and the other options don’t seem to affect it either way.

Hopefully this helps you to debug this plugin.