BugWP logo BugWP
Back to Community
Home / Community / Plugin → Members – membership & user role editor plugin

Why Your Members Plugin Shortcodes Aren't Working (And How to Fix Them)

22 threads Sep 7, 2025 Plugin → Members – membership & user role editor plugin

Content

Many WordPress users turn to the Members plugin for robust user role and capability management. A common point of confusion, as seen in multiple community threads, is the plugin's shortcode functionality. Users often expect shortcodes for registration or account management, only to find they don't work as anticipated. This guide will clarify what the Members plugin can and cannot do with shortcodes and provide solutions for the most common issues.

The Core Issue: Understanding Members Plugin Shortcodes

The primary misunderstanding stems from the scope of the plugin. The Members plugin is designed for managing user roles, capabilities, and access control on the backend of your WordPress site. It is not a front-end membership portal solution.

Based on community support interactions, the plugin officially provides only one shortcode: the [members_login] shortcode for displaying a login form. Threads clearly show that requests for account or registration shortcodes are met with the response that "Members does not have any account or registration shortcodes." These functions would need to be provided by another plugin, such as a dedicated membership system.

Common Shortcode Problems and Solutions

Problem 1: The Access Control Shortcode Doesn't Show/Hide Content

Some users find code snippets for shortcodes like [members_access] that are designed to show or hide content based on a user's role. If this shortcode isn't working, it could be for a few reasons:

  • Incorrect Syntax: Double-check the shortcode format. A typical example is: [members_access role="administrator,editor"]Show this content to administrators or editors only.[/members_access].
  • Plugin Conflict: Another plugin on your site might be interfering with the shortcode's functionality.

Problem 2: The Login Form Shortcode Has Styling Issues

Another common issue is that the [members_login] form appears but has poor styling, making input fields hard to see. As one user reported, "I can insert if I go with mouse near, and I find where I can write, but is not quickly to find."

Solution: This is almost always a theme conflict. Your active theme may not provide default styles for the form's CSS classes. You can easily add custom CSS to fix this. Add the following code to your Appearance → Customize → Additional CSS panel:

.members-login-form form input[type=text], 
.members-login-form form input[type=password] {
  border: 1px solid #e4e9ef; /* Adds a visible border */
  padding: 10px; /* Adds spacing inside the field */
  width: 100%; /* Makes the field a standard width */
}

.members-login-form form input[type=submit] {
  background: #394650;
  color: #fff;
  padding: 10px 20px;
  border: none;
}

Adjust the colors and sizes (values in # and px) to match your website's design.

What to Do If You Need More Shortcodes

If your goal is to create a full front-end membership experience with registration forms, user accounts, and protected content, you will need to extend your site's functionality. The Members plugin is an excellent tool for defining the rules of access (the roles and capabilities), but you will need an additional plugin to enforce those rules on the front-end and handle the user interaction.

Look for plugins that are specifically designed for front-end membership and that are compatible with the standard WordPress roles and capabilities managed by the Members plugin.

Conclusion

Understanding that the Members plugin is primarily an administrative tool for roles and capabilities is key to solving most shortcode issues. For the built-in login form shortcode, a little custom CSS can resolve most display problems. For more advanced membership features, you'll likely need a complementary plugin to work alongside Members.

If problems persist, a standard troubleshooting step is to deactivate other plugins temporarily to check for a conflict, as was suggested in several community threads regarding other issues.

Related Support Threads Support