Plugins That Cause Problems

The following is a list of plugins that can cause issues when configured or used in certain ways:

Cache Plugins

All cache plugins should be used with caution and with the knowledge that they will have to be configured in order to not cause major problems. Keep in mind that when a cache plugin performs correctly it will cause issues with MemberMouse. This is a result of the nature of caching itself which takes a snapshot of pages and other resources the first time they're loaded and then on future requests pulls them from the cache instead of grabbing them from the server. This works great for static pages and resources but if a page has any sort of dynamic functionality, like a lot of your pages will when you're using MemberMouse, you'll end up delivering an incorrect experience to your customers.

Here are some cache plugins to use with caution:

If you're going to use a cache plugin make sure you configure it such that:

  • MemberMouse core pages are not cached.
  • Pages with GET parameters (i.e. ?x=y at the end of the URL) aren't cached.
  • Pages that use MemberMouse SmartTags are not cached. If you're using SmartTags in a widget that appears on multiple pages, you'll need to exclude all of these pages from being cached.

Visual Editor Plugins

Using visual editor plugins, such as Visual Composer, for the most part, won't cause issues. However, issues can be introduced when using certain SmartTags spread across multiple blocks of a visual editor. Specifically, any [MM_Form_...] SmartTag must be contained within a parent [MM_Form]...[/MM_Form] SmartTag as follows:

[MM_Form type='checkout']
First Name:
[MM_Form_Field type='input' name='firstName' customAttributes='placeholder="First Name"']

In this case, if the [MM_Form_Field] SmartTag were used outside of the [MM_Form]...[/MM_Form] SmartTag, it would not work. With visual editors you can create multiple blocks of content in order to assist in laying out your pages.

All [MM_Form_...] SmartTags must be included in the same visual editor content block as the [MM_Form]...[/MM_Form] SmartTag in order to work. For example...

Correct Usage
This will work...

Incorrect Usage
This will not work...

Broken Link Plugins

There are several plugins that are designed to comb through your site and locate broken links, or links that take users to pages that are no longer active. While not only placing a lot of strain on your WordPress database and slow down your site, these plugins can cause your SmartTags to not function properly.  You will likely see an error like the one listed below:

<a href="Invalid SmartTag Configuration: The 'type' attribute 'footPassword' is invalid for SmartTag MM_CorePage_Link." class="mm-forgot-password">Forgot Password</a>

And your SmartTags will not function. If you have this issue on your site, try deactivating:
  • Broken Link Checker
We understand that Google suggests checking for broken links on your site. A safer (and less taxing) alternative is a site like, which is not a plugin, and wlll provide the same results.

Feedback and Knowledge Base