Linux 软件免费装
Banner图

My Private Site – Make Your Whole Site Private, Force Login & Block Registration Spam

开发者 dgewirtz
更新时间 2026年6月29日 11:34
捐献地址: 去捐款
PHP版本: 5.4 及以上
WordPress版本: 7.0
版权: GPLv2 or later
版权网址: 版权信息

标签

recaptcha registration spam force login restricted access private site

下载

3.0.2 3.1.0 2.4 2.6 2.6.1 2.14 2.14.1 1.1 4.1.1 2.11.2 2.11.3 2.13 2.14.2 2.2 2.3 3.0.9 2.6.9 2.7 2.8 3.0.11 3.0.12 3.0.3 3.0.5 3.0.8 2.12 2.9 3.0.0 3.0.13 1.0 3.0.1 3.0.6 2.5 2.10 2.10.1 2.4.1 3.2 4.0.3 2.0 2.11 2.11.4 2.4.2 4.0.4 2.1 2.11.1 3.0.10 3.0.14 3.1.1 4.1.0 4.2

详情介绍:

My Private Site makes your WordPress site private so only logged-in users can see your content. With one click, you can restrict access to all posts and pages, automatically redirect visitors to the login screen, and keep your site visible only to people you trust. Unlike full membership or subscription systems, My Private Site focuses on strong privacy without unnecessary complexity. It is ideal for family sites, schools, clubs, client previews, or development environments where you want to share content with a trusted audience without managing payments, profiles, or custom roles. Ideal Use Cases Digital Fortress protection My Private Site helps protect the “front door” of your private site with built-in safeguards for login and user registration, including registration spam protection and optional reCAPTCHA support. If spam accounts already exist, the Spam Account Cleanup tool helps preview, export, and batch-delete suspicious basic user accounts with protections for online store customers and confirmations. It also includes AI Crawler Defense to discourage automated collection of your site’s content. Key Features Built-in Registration Spam Guard Fake registrations can quickly fill your user list and trigger a flood of notification emails. My Private Site includes Registration Spam Guard controls that help block automated signups before they become user accounts: * Registration reCAPTCHA: Adds an optional reCAPTCHA challenge to the WordPress registration form and rejects unsolved or unverifiable submissions. * Honeypot field: Adds an invisible registration field that normal visitors do not fill in, but many bots do. * Gibberish username detection: Blocks long, randomly mixed usernames often generated by registration bots. * Reserved administrator usernames: Blocks self-registrations that impersonate common site identities such as admin or webmaster. * URL-like username detection: Blocks usernames that look like domains or URLs, including phishing-style hosted page addresses. * Crypto scam phrase detection: Blocks usernames that carry common bait phrases such as balance checks, transfer notices, or withdrawal prompts. * Excessive email dots: Blocks email addresses with unusually dotted local parts commonly used in bulk fake accounts. * Suspicious Gmail plus aliases: Blocks Gmail plus-address aliases with random-looking tracking codes often seen in automated spam bursts. * Digit-dominant and gibberish email checks: Optional default-off checks for mostly numeric or random-looking email local parts. * Missing MX records: Blocks registrations when the email domain is not configured to receive mail. * Disposable email domains: Blocks common throwaway email services, including matching subdomains. * StopForumSpam lookup: Checks registrants against the StopForumSpam database. Each Registration Spam Guard option can be enabled separately, and registration reCAPTCHA can be enabled independently from login reCAPTCHA while sharing the same keys. When enabled, reCAPTCHA protects the standard WordPress registration form, and selected spam checks also block suspicious unauthenticated account-creation attempts from other public entry points, such as REST API, XML-RPC, admin-ajax, and custom registration forms. Blocked attempts are logged in the Spam Log area for quick review. Spam Account Cleanup If a site has already been hit by fake subscriber accounts, My Private Site includes a staged Spam Account Cleanup tool in Advanced settings. It previews basic users, applies hard protections for detected EDD and WooCommerce customers, store-order accounts, content authors, site managers, recently active users, and uploaded mailing lists, exports the exact dry-run queue to CSV, and only deletes after a backup acknowledgment and typed confirmation. Deletion runs in resumable browser-driven batches, reassigns any unexpectedly found WordPress content to the current admin instead of deleting it, and includes an optional orphaned usermeta sweep for metadata rows that no longer belong to any user. Built-in AI Crawler Defense The internet is rapidly changing, with AI crawlers and bots harvesting content without consent. My Private Site helps you defend your work with integrated AI Crawler Defense features: * NoAI and NoImageAI tags: Automatically add meta tags and headers that signal compliant AI systems not to use your text or images for training. * Block GPTBot: Add a robots.txt rule to prevent OpenAI’s crawler from accessing your site. * Really Simple Licensing (RSL): Publish a machine-readable license that explicitly prohibits AI training on your content. These protections are included free in the core plugin, easy to enable with a checkbox, and designed to safeguard your site without affecting normal visitors or search engines. You can use them even if you're not using any other site privacy features. Watch the Video Overview and Demo https://youtu.be/jry3DHD-OB8 Premium Add-ons Premium add-ons turn My Private Site into a comprehensive privacy suite, giving you enterprise-style layered security defenses, smarter oversight, and flexible access, without the complexity or cost. Advanced AI Crawler Defense, Visitor Intelligence, and Block IP provide protections regardless of whether you're using any site privacy features. https://youtu.be/B6s8O9VZLc0 Limits 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.

屏幕截图:

  • Site privacy mode enabled
  • REST API, registration spam, reCAPTCHA protection
  • Plugin welcome and overview
  • Landing page redirect options
  • Public homepage visibility settings
  • Shortcodes for content privacy
  • Membership and registration options

升级注意事项:

2.14 Support wpengine.com hosting and off-site Login pages 2.13 Reduce WordPress Admin panels Menu clutter by removing plugin Settings from Users submenu 2.12 Correct handling of www. in a URL by waiting until Pretty Permalinks applied before deciding whether to force Login 2.11.3 Correct Failed Logins when Custom Login selected 2.11.2 Add Setting to control User with No Role 2.11.1 Fix User with No Role errors on Network/Multisite 2.11 Improves Multisite security and supports Paid Membership Pro 2.10.1 Landing Location obeyed for direct access with wp-login.php URL 2.10 Allow deletion of Users submenu entry for plugin settings 2.9 Meta Widget logins now go to Landing Location 2.8 Support Prefix URL for Always Visible pages 2.7 Support Custom Login page 2.6.1 Support Theme My Login plugin with older versions of WordPress 2.6 Support Theme My Login plugin 2.5 Allow many Always Visible pages 2.4.2 Reveal BuddyPress Activation page 2.4.1 Home Page better URL matching for Root Home Pages 2.4 Support BuddyPress 2.3 New Setting to display Home Page on a Private Site. 2.2 Display WordPress Self-Registration field on plugin Settings page. 2.1 Allow User Self-Registration by "revealing" the Register page to those not logged in. 2.0 Create a Settings page that defines where the user ends up after logging in 1.1 Should eliminate Modify Header errors due to conflict with other plugins 1.0 Production version, updated to meet WordPress Repository standards

常见问题:

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

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. By far, the most common way to create a Redirect Loop on your browser with this 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 My 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.

更新日志:

4.2 4.1.1 4.1.0 4.0.4 4.0.3 3.2.1 3.2 3.1.1 3.1.0 3.0.14 3.0.13 3.0.12 3.0.11 3.0.10 3.0.9 3.0.8 3.0.7 3.0.6 3.0.5 3.0.4 3.0.3 3.0.2 3.0.1 3.0.0 2.14.2 2.14.1 2.14 2.13 2.12 2.11.4 2.11.3 2.11.2 2.11.1 2.11 2.10.1 2.10 2.9 2.8 2.7 2.6.1 2.6 2.5 2.4.2 2.4.1 2.4 2.3 2.2 2.1 2.0 1.1 1.0