Decide who sees what, without a membership plugin
Hide a category from guests, show prices only to logged-in customers, keep a page for one role. Describe the rule; NiroCoder shows exactly what it will change before it does.
What the plan says
For “Hide products from guests, only logged-in customers can see the shop.” NiroCoder writes a plan like this one, in plain language, before it builds anything. Yours is written for your own site.
Members-only Shop
Access rule extension · Medium risk
What I understood
You want visitors who are not logged in to stop seeing products, and to be asked to log in instead.
Will create
- A rule that hides products from visitors who are not logged in
Will change
- The shop page and product pages for logged-out visitors
- Product search results for logged-out visitors
Won’t touch
- Your products and their prices
- Logged-in customers’ experience
- User roles and capabilities
Why this risk level: Changes what visitors can see, but not your data or roles.
Get a better plan on the first try
NiroCoder plans from what you write. A few details up front save a round of changes.
01
Name the content
A page, a category, a product or a path like /members/. Be specific so the rule never covers more than you meant.
02
Name who gets in
Guests, any logged-in user, or a role such as Subscriber or Customer.
03
Say what everyone else sees
A redirect to the login page, a short message, or the content simply hidden. Pick one in your request.
More things to ask for
Same idea, different request. Describe any of these in your own words.
- Show prices only to logged-in users
- Make the “Resources” category visible to subscribers only
- Redirect guests from /members/ to the login page
- Hide the admin bar for everyone except administrators
- Show the “Add to cart” button only to logged-in customers
- Hide the Tools menu from Editors
Questions
No. The local security check blocks code that adds or removes roles and capabilities, or changes the default role and registration settings. Access rules work by filtering what is shown, not by rewriting permissions.
The plan shows who will lose access before you approve it. If a rule turns out wrong, turn the extension off or go back to an earlier version. Try rules on a staging site first.
For simple rules, yes: hide a category from guests, show prices to logged-in users, keep a page for one role. For subscriptions, payments or drip content, use a dedicated membership plugin.
Yes. Name the role in your request, for example “hide the Resources category from subscribers”. The plan lists the roles and content the rule applies to, so you can check it before you approve.
No. A rule changes what visitors see, not your data. Your products, prices and pages stay as they are, and turning the extension off brings everything back.
More use cases
Custom post types & catalogs
Books, events, properties, team members, portfolios, with fields and taxonomies.
Create a Books catalog with author, ISBN and a PDF download, plus an archive and a page for each book.
WooCommerce tweaks
Order statuses, checkout rules, product visibility and order automations.
Add a “Quality Check” order status between Processing and Completed.
Admin tools
Dashboard widgets, admin columns, bulk actions and settings screens.
Add a dashboard widget showing today’s orders and the five newest comments.
Automations
“Email the author when a post is published”, “Create a task when an order completes”.
Email the post author when their post is published.
Shortcodes & front-end features
Shortcodes and small front-end features for your theme.
Make a [notice] shortcode that shows a dismissible yellow notice bar.
Describe it. Review the plan. Ship it.
Free plugin, 7-day trial, 50 credits, no card, no API key. Nothing is built until you approve.