Simple Membership Plugin › Forums › Simple Membership Plugin › Full page protection and custom message redundancy
- This topic has 2 replies, 2 voices, and was last updated 11 months, 3 weeks ago by
Doblo7.
-
AuthorPosts
-
August 25, 2025 at 5:22 am #31341
Doblo7
ParticipantGood morning,
I apologize to disturb you again.
I am having an issue with the free add-ons “custom message” and “full page restriction.” When pages are protected, messages from both add-ons appear simultaneously: the default message from full page restriction (“PleaseLoginNot a Member?Join UsYou need to login to view this content.”) and the custom message I wanted to display.
I have performed the prescribed tests and carefully read the documentation. In a test environment, this is visible on the WordPress Twenty Five theme. On a blank WordPress instance, once SWPM is installed with the two add-ons, the protected sample page still displays both messages…
Does anyone have a solution?Thank you in advance.
Kind regardsAugust 25, 2025 at 11:40 pm #31343The Assurer
ModeratorHi there! It looks like you’re running into a known limitation of how the free Custom Messages and Full Page Protection add-ons interact in the Simple Membership Plugin. Here’s what’s happening—and how you can address it.
What’s Going On
By design, when both the Custom Messages Addon and Full Page Protection Addon are active, both messages appear because the custom message replaces only parts of the output, but the full page protection’s default message still renders as well
Membership Plugin
WordPress.orgFrom a support thread:
“If you use the custom messages addon to override the standard protection message of the plugin then the login addon can’t add the extra parameter … You can’t get both.”
Membership PluginWhile that comment specifically referred to compatibility with the After Login Redirection add-on, the same principle applies here. Essentially, the replacement performed by the Custom Messages addon doesn’t fully suppress or replace the default output of the Full Page Protection addon, so you end up with both messages stacking.
What You Can Try
Option 1: Use Only One Addon* Remove or deactivate one of the add-ons to avoid duplicate messaging. If you’re aiming for a customized, clean message experience, prioritize the Custom Messages Addon and deactivate Full Page Protection.
* Or, vice versa, rely solely on Full Page Protection’s default message and disable the custom one.
Option 2: Customize via CSS
If you’re comfortable with CSS, you can hide the default message by targeting its class or wrapping element. For example:
/* Example CSS: adjust class name as needed */
.swpm-fullpage-protection-msg {
display: none !important;
}This will hide the message output by Full Page Protection and only show your custom one. Be sure to inspect the page (using browser dev tools) to identify the exact CSS class being used.
Option 3: Override Templates or Hooks (Advanced)
If you’re a developer or comfortable with code:
- Look for filters or template files in the plugin or the Full Page Protection add-on that output the default message.
- Override or remove that part using your theme’s functions.php (e.g., by removing action hooks or adjusting logic).
- This approach gives you full control—though it’s more technical and requires familiarity with the plugin’s structure.
Recommendation
If your priority is to display only your custom message, the quickest route is either to deactivate Full Page Protection and rely entirely on the Custom Messages Addon—or to use CSS to hide the unwanted duplicate. For full control, diving into hooks or templates is the most flexible (though advanced) solution.August 27, 2025 at 9:53 am #31389Doblo7
ParticipantThank you very much, Sir !
Kind regards -
AuthorPosts
- You must be logged in to reply to this topic.