Content Restriction & Password Protect
Puts a page, a section or the whole site behind a password or a sign-in, and keeps what is protected out of search, listings, the sitemap and the public API.
Not open yet No card
Description
Puts a page, a section or the whole site behind a password or a sign-in, and keeps what is protected out of search, listings, the sitemap and the public API.
What it does
- Password-protect site/sections/posts
- Restrict by role/capability
- Login redirect
- Teaser/excerpt display
- Expiry
Stands in for
Password Protected, Members.
These are other companies' products, named only to say what job this module does. WebHD is not affiliated with them.
What comes across
What this module brings over from the plugin a site used before, and what it leaves behind. Each import ends with a report that names anything it could not carry.
- From Password Protected
- Comes across: Whether the whole site is protected, and whether signed-in people or only administrators get in without the password.
- Does not: The password itself, which is stored in a form that cannot be carried over safely and must be set again; the allowed IP addresses; and the remember-me length.
- Not yet verified against a live export: this importer has only been tested on sample files we wrote from the documented format.
- From Members
- Comes across: Which posts and pages are limited to which roles, and the message shown to people who are not allowed in.
- Does not: Custom roles and capabilities, which map to the nearest built-in role only when they share its name; and the private-site setting.
- Not yet verified against a live export: this importer has only been tested on sample files we wrote from the documented format.
- From Ultimate Member (restrictions)
- Comes across: Each post and page Ultimate Member limited to signed-in people: anyone signed in, or the lowest of the roles it ticked, with the post's own message.
- Does not: Pages shown only to signed-out people (named), redirects to another address, restrictions on categories and tags, and Ultimate Member's profiles, member directories, registration forms and site-wide setting.
- Not yet verified against a live export: this importer has only been tested on sample files we wrote from the documented format.
- From WordPress (password-protected posts and pages)
- Comes across: Each published post or page that was behind a password: it is put behind the same password and published. Items that shared a password share one rule, so a reader gives it once. Run after Core's own WordPress content import, which brings these items in as drafts.
- Does not: Passwords longer than 200 characters (the rule is made without one, to be set by hand); items whose password would need a rule beyond the limit of 60 (60 different passwords), which stay drafts; and the cookie that remembered a reader on the old site, so each reader types the password once more.
- Not yet verified against a live export: this importer has only been tested on sample files we wrote from the documented format.
No importer yet for: Restrict Content.
Using a plugin that is not named here? It is built for your site On The Fly. How that works
Changelog
1.3.2 November 18, 2026
Content Restriction & Password Protect 1.3.2: its importers that read a WordPress export now name the WordPress plugins they import from, so a site connected through Migrate → “Connect your WordPress” is offered them only when the old site uses one of those plugins. Nothing else changed. Needs Core 0.1.40.
1.3.1 November 18, 2026
Content Restriction 1.3.1 (needs Core 0.1.34): the WordPress passwords importer reads the protected posts together and goes on in steps, so any number of protected posts fits a host that allows few database queries per request (4 protected posts made 49 queries in one request; now 27 at most per request). Each post is still locked, the lock read back, and only then published.
1.3.0 November 17, 2026
Content Restriction 1.3.0: posts and pages that shared a password on the old site now share one rule. The WordPress passwords importer makes one rule for each different password instead of one for each item, so a site with hundreds of protected posts and one or two passwords is carried over whole (the limit of 60 rules now means 60 different passwords). A reader who gives the password once can read every item that shares it, and the owner changes it in one place; the rules screen shows how many items a shared rule covers and names the first few. A password carried over that is shorter than six characters is still kept, and the rules screen now says so beside the rule until a new one is set. Updating: run the site's migrations (one new table, one new column).
1.2.0 November 17, 2026
Content Restriction 1.2.0 (needs Core 0.1.32): a new importer, "WordPress (password-protected posts and pages)". Core's content import brings such items in as drafts; run this with the same export file and each one gets a rule with the password it had on the old site and is then published behind it, kept out of search, lists, the sitemap, the feed and the public API until the password is given. The lock is put on and read back before an item is published. Passwords are stored as a one-way hash. A password shorter than six characters is kept so readers' password still works, and the report names it; one longer than 200 characters gives a rule without a password; items beyond the limit of 60 rules stay drafts and are named.
1.1.0 November 17, 2026
Content Restriction 1.1.0: an importer for Ultimate Member's post restrictions. A post or page it limited to signed-in people is limited here to anyone signed in, or to the lowest role it ticked, with its own message; pages for signed-out people only and redirects are reported.
1.0.0 November 16, 2026
Content Restriction & Password Protect: protect a page, a section or the whole site with a password or a sign-in, with teasers and end dates. Imports from Password Protected and Members.
Get Content Restriction & Password Protect when WebHD opens
One form on the home page: your WordPress address, then your email.
No card Takes a minute No fake scan