Plugin Directory

My Private Site – One-Click Password Protection for All Your Site's Content

My Private Site – One-Click Password Protection for All Your Site's Content


Allows the Administrator to restrict a WordPress-based web site to viewing only by registered users who are logged on. Any attempt, by anyone not logged, to view any Page, Post or other part of the site will display a WordPress login screen.

Login prompts are provided whenever a non-logged in user (“site visitor”) attempts to access any URL controlled by WordPress on the web site.

Note: If privacy isn’t turned on for your theme, use the Compatibility Mode option on the Site Privacy tab. This is known to apply to Elementor, Oxygen, and Twenty Twenty Two themes.

New in 3.1: REST API Guardian

  • Turn on or off the My Private Site REST API security features.
  • Block REST API access for logged-out users

More Features and Settings

  • Supports WordPress Networks (“Multisite”), with Network-wide Settings planned for a future version
  • A separate Setting is provided for hiding or revealing Site Home without the need to enter its URL
  • Supports Custom Login and Registration pages at URLs different than the standard WordPress Login and Registration URLs
  • Landing Location settings determine what the User sees after successfully logging in
  • Landing Location is set for both automatic Login prompts and the Meta Widget’s Login link
  • New hide-if privacy shortcode allows selective content to be hidden or shown based on login status
  • User Self-Registration settings (varies between Network and Non-Network WordPress) are presented on the plugin’s Settings page for easy access
  • No known Theme incompatibilities, and only known Plugin incompatibility is with the A5 Custom Login plugin
  • Special functionality is included to not hide Login- and Registration-related URLs used by BuddyPress and Theme My Login plugins
  • Remember Me improvements at Login via free companion plugin, jonradio Remember Me, which can be downloaded separately from the WordPress Plugin Repository
  • Overrides WordPress hiding of Network Activated plugins, just for itself; to provide this feature for all plugins, use the free companion plugin, Reveal Network Activated Plugins, which can be downloaded separately from the WordPress Plugin Repository
  • Setting to disable the plugin so that other plugin Settings can be changed when the Site is not set to Private

If you allow Self-Registration, where new Users can Register themselves, you will need to select the “Reveal User Registration Page” setting or new Users will be blocked from seeing the WordPress Registration screen (on WordPress Networks, turning off the Reveal User Registration Page setting on the “Main Site” will prevent Registration from all Sites). For convenience, the WordPress Setting that controls Self-Registration of Users has been added to the Plugin’s Settings page.

Another Setting allows the Private Site feature to be turned off. When the plugin is installed and activated, the Private Site feature is set off by default, to allow the Administrator an opportunity to become familiarized with the plugin’s features and to set the desired settings. A warning that the site is not private appears after first activation of the plugin until the Administrator visits the plugin’s Settings page.

If a WordPress Network is defined, the plugin can be activated individually for select sites. Or Network Activated. In either case, each site will have its own Settings page where the Private Site feature can be turned off (default) or on for just the one site, and a Landing Location defined for each site.

Yes, there are other plugins that hide some or all WordPress content for any site visitor who is not logged on. But when I was searching for a solution for one of the web sites I support, I decided to “write my own” because I knew how it worked and felt comfortable that there would be no way for anyone not logged in to view the site, including Search Engines.

Watch the intro video

Premium Add-ons

  • Public Pages 2.0: Allows site operators to designate certain specific pages, or pages with specified prefix, to be available to the public without login. Now also allows public site, private pages. Watch the video
  • Tags & Categories: Allows you to make pages public or (with Public Pages 2.0) private based on tags and categories. Watch the video
  • Selective Content: Allows hiding, showing, and obscurifying page content through the use of shortcodes. Can also selectively hide widgets and sidebars. Watch the video


This plugin does not hide non-WordPress web pages, such as .html and .php files. It also won’t restrict images and other media and text files directly accessed by their URL. If your hosting provider’s filesystem protections haven’t been set up correctly, files may also be accessed by directory listing.

Support Note

Support has moved to the ZATZLabs site and is no longer provided on the WordPress.org forums. If you need a timely reply from the developer, please open a ticket.

Mailing List

If you’d like to keep up with the latest updates to this plugin, please visit David’s Lab Notes and add yourself to the mailing list.



IMPORTANT: Support has moved to the ZATZLabs site and is no longer provided on the WordPress.org forums. If you need a timely reply from the developer, please open a ticket.

This section describes how to install the My Private Site plugin and get it working.

  1. Use Add Plugin within the WordPress Admin panel to download and install this My Private Site plugin from the WordPress.org plugin repository (preferred method). Or download and unzip this plugin, then upload the /jonradio-private-site/ directory to your WordPress web site’s /wp-content/plugins/ directory
  2. Activate the My Private Site plugin through the Installed Plugins Admin panel in WordPress. If you have a WordPress Network (“Multisite”), you can either Network Activate this plugin, or Activate it individually on the sites where you wish to use it.
  3. Go to the plugin’s Settings page to make the Site Private, and set where the user ends up after logging in: the Landing Location.
  4. If you allow Self-Registration, where new Users can set up their own User Name on your WordPress site or Network, you will want to select Reveal User Registration Page on the plugin’s Settings page.


IMPORTANT: Support has moved to the ZATZLabs site and is no longer provided on the WordPress.org forums. If you need a timely reply from the developer, please open a ticket.

How do I fix Redirect Loops (browser cycles for a long time then gives up)?

By far, the most common way to create a Redirect Loop on your browser with this jonradio Private Site plugin is to specify both Custom Login page and Landing Location on the plugin’s Settings page. Simply setting “Where to after Login?” in the Landing Location section to “Omit ?redirect_to= from URL” should correct the problem.

This problem has been observed when the URL of the Custom Login page is a WordPress Page. It occurs because, for Page URLs, WordPress uses the ?redirect_to= Query keyword for purposes other than a Landing Location.

What happened? I changed my Permalinks and now some things don’t work.

Whenever you change your WordPress Permalinks (Settings-Permalinks in Admin panels), this jonradio Private Site plugin does not automatically change any URLs you have entered in the plugin’s Settings. You will therefore want to make changes to URLs in the plugin’s Settings whenever you change Permalinks.


28 جُون 2023
Added it, set it up to use a custom url, rather then use the url I specified it filled the address bar in with it, as well as about 500 more characters rendering it useless.
28 اپريل 2023
I use the free version. None of the advanced fine-grained access controls. Simply the basic function to lock down your entire website from anonymous users. With this all anonymous requests to any WordPress slug get redirected to the login screen. ✅ Worked fine with classic themes. ❌ Recently I switched to a block theme (Twenty Twenty Three) and My Private Site stopped working. 👉 The fix was quite easy: WordPress Backend Private Site Site Privacy: Compatibility Mode: Change it from “Standard” to “Theme Fix”. I can’t tell whether that’s valid for any block theme in general. But if anyone has the same issue, it’s worth trying to change this setting!
18 جُولاءِ 2022 2 replies
Hi, first of all thank you for the great pluging. I tried registering on your site for support but it says email is incorrect. I have My Private Site plugin installed on a non-for-profit site for members to login privately and be able to request things from the main chapter. The current update is giving the following error: wp-content/plugins/jonradio-private-site/library/cmb2/includes/CMB2.php on line 1553 This errors seems to be blocking updates, deleting plugins and themes and some other functions on the site. Not sure how. I am using the plugins below: All-in-One WP Migration Elementor Elementor Pro User Role Editor Woocommerce WooCommerce Custom Emails WooCommerce Page Builder For Elementor WP Mail SMTP WPForms Lite Please let me know if there is something I can do or if an update will come that can resolve this.
جمع: سڀ 76 تبصرا پڙهو

تعاون ڪندڙ & ڊولپرز

“My Private Site – One-Click Password Protection for All Your Site's Content” اوپن سورس سافٽ ويئر آهي. ھيٺين ماڻھن ھن پلگ ان ۾ حصو ورتو آھي.

تعاون ڪندڙ

لاگ تبدیل ڪريو


  • Added REST API Guardian protection to core plugin
  • Increased size of heading font in dashboard
  • Replaced tags set (login, pages, private, security, visibility, plugin, page, posts, post) with (registered only, privacy, protected, restricted, password protect)


  • Minor compatibility update for WordPress 6.4.


  • Minor update to better support my_private_site_public_check_access_by_page filter.


  • Slight improvement to HTML support pages


  • Fixed a CMB2 type error that popped up from time to time (Thanks, Michael!)


  • Fixed a bunch of over-eager security checks


  • Fixed compatibility switch bug


  • Fixed some security bugs


  • Added more hooks for increased granular control of access
  • Fixed some minor bugs


  • Moved compatibility mode option to Site Privacy tab and added additional theme compatibility fixes


  • Added a compatibility mode option on the Advanced tab which will hopefully finally fix the Elementor issues


  • Possible fix for Elementor incompatibility issues
  • Fixed some small bugs


  • Added Advanced feature allowing users to specify custom password reset page


  • Fixed duplicate header bug found on some systems


  • Minor bug fixes
  • Added uninstall telemetry


  • Complete rewrite with an entirely new, streamlined UI
  • Added the selective content subsystem


  • Minor fix for password reset. Thanks to user o2Xav.


  • Minor support update


  • Force login at ‘get_header’ instead of ‘template_redirect’ Action to be compatible with wpengine.com hosting
  • Allow Custom Login page that is NOT on the current WordPress site, and clean up Settings page validation of related fields
  • Fix double display of Error Messages on Settings page


  • Remove Plugin’s entry on Users submenu on WordPress Admin panels
  • Remove associated Setting, which determined whether Users submenu entry existed


  • Wait until Pretty Permalinks applied before deciding whether to force a login
  • Add an Override Advanced Setting with Warnings on Usage, to allow Landing Location and Custom Login to both be specified.
  • Correct coding error that allowed Landing Location with Custom Login, a potential Redirection error
  • Fix Error Log warning on [mb]strpos Offset parameter


  • Use Custom Login setting, if present, to redirect failed login attempts with blank username and/or password


  • Use Custom Login setting, if present, to redirect failed login attempts


  • Provide a Setting to disable User with No Role behaviour introduced in 2.11


  • Remove forced logout when User with No Role attempts to access a Site (Network/Multisite install), to fix repeated messages when wp_logout is hooked by other plugins


  • In a WordPress Network (“Multisite”), block Users with No Role on the current Site
  • Make Landing Location work when free Paid Membership Pro plugin is activated


  • Add setting to obey Landing Location for users who login via a URL of wp-login.php without a &redirect_to= following


  • Add setting to not display a Users submenu option for the plugin’s settings
  • Conditional logic for Settings Saved update message in Validate function


  • Set Landing Location for logins via Meta Widget link, as well as automatic Login prompts


  • Add Prefix option to Always Visible URLs
  • Automatically use mb_ Multi-Byte string functions, if available


  • Add Custom Login URL setting


  • Older versions of WordPress require a parameter be passed to get_post()


  • Detect and make visible Login-associated Pages created by the Theme My Login plugin


  • Allow other URLs to be Always Visible with new Setting


  • Reveal BuddyPress /activate/ Activation page when Reveal Registration selected


  • Fix bug in URL matching for Root, where one URL has a trailing slash and the other does not


  • Handle BuddyPress’ redirection of Register URL in Reveal Registration


  • Add Setting to Reveal Home Page on a Private Site
  • Fixed Problems with wp_registration_url function in WordPress prior to Version 3.6


  • Add the WordPress User Self-Registration field to the plugin’s Settings page
  • Add the Settings page to the User submenu of Admin panel, too


  • Add a settings checkbox to reveal the Register page for User Self-Registration


  • Add Settings page, specifying Landing Location and turning Private Site off and on
  • Warning for new default of OFF for Private Site until Settings are first viewed
  • Add Networking Settings information page
  • Track plugin version number in internal settings
  • Replace WordPress Activation/Deactivation hooks with Version checking code from jonradio Multiple Themes
  • Add Plugin entry on individual sites when plugin is Network Activated, and Settings link on all Plugin entries


  • Change Action Hook to ‘wp’ from ‘wp_head’ to avoid Modify Header errors when certain other plugins are present


  • Add readme.txt and screenshots
  • Add in-line documentation for php functions