Matt Miller

mikemm01

Did you find this plugin helpful? Please consider <a href="https://wordpress.org/support/view/plugin-reviews/ip-blacklist-cloudflare/" rel="ugc">leaving a 5-star review</a>.
Cloudflare provides security and optimization services for websites all around the internet. WordPress sites are often attacked by bots or hackers and, while Cloudflare has preset firewall rules to help, it doesn’t always filter out all malicious activity.
Cloudflare IP Blacklist allows WordPress admins to add a list of prohibited usernames and if someone attempts to log in with one of these usernames, this users IP address is automatically added to the Cloudflare blacklist. By doing this, the next time this user attempts to load the site, they will be blocked by Cloudflare before their requests get to your site’s server. Add an extra layer of security today to your site!
** This plugin relies on the use of Cloudflare, a third-party service that increases security and performance for web sites and services across the internet. For more information, visit the <a href="https://www.cloudflare.com/" rel="nofollow ugc">Cloudflare website</a> and their <a href="https://www.cloudflare.com/privacypolicy/" rel="nofollow ugc">privacy policy</a>. This plugin is not officially endorsed, built or maintained by the Cloudflare team; rather, we are a development company that uses their services every day! **
<h3>Request</h3>
If you find that a part of this plugin isn’t working, please don’t simply click the WordPress “It’s broken” button. Let us know what’s broken in <a href="https://wordpress.org/support/plugin/ip-blacklist-cloudflare/" rel="ugc">its support forum</a> so we can make it better.

IP Blacklist for Cloudflare

Blacklist IP addresses that attempt to login with a banned username through Cloudflare.

fullthrottledevelopment

Glenn Ansley

This plugin does one thing. If a page that is password protected has children pages, all children pages will be protected with the same password.
If the correct password is entered on the parent page or any of its children pages, all related pages will be viewable to the user.
The plugin protects unlimited levels of grandchildren pages via the $post->ancestors. It uses first ancestor that is password protected.
<h3>Additional Information</h3>
The plugin currently works by looking for parent pages that are password protected and applying the same restrictions the the currently being viewed child page. This means that the children pages do not actually get a password added to the database.
I’m trying to decide if this is the best way to proceeed or if I should take another route (such as adding / updating / removing passwords from children pages at the write or save post screen).
Please feel free to offer any suggestions or report any bugs here: [http://fullthrottledevelopment.com/password-protect-children-pages/]
Thanks!

FT Password Protect Children Pages

Applies the same protection to children pages applied to the parent page.

IP Blacklist for Cloudflare vs FT Password Protect Children Pages