The smart way to create password-protected areas in WordPress. Protect pages, posts or parts of your content with one, multiple or hundreds of passwords. Activate, configure and your done.
Protect pages, posts and products with passwords and captchas. Simple to setup and insanely secure. You will never want to use the native password restriction from WordPress again.
Modern PHP and Coding standards and SHA-2 password encryption for the best solution for password protecting content.
We provide technical support for Passster (Premium) – Plugin to Password-Protect portions of a Page or Post through our community forums. Do you need support? Visit this link and post your issue!
FestyBot
Steve
gyurci
allstarswebmasterage
spadetje_17
zerl
greenlinkwebScanning…
This file is currently being scanned.
Version
3.3.8
Status
Last Updated
Published
Downloads
–
Views
112
Demo Content
Yes
Original License
No
Original License
No
Files included
No files included found
Tags
No tags found.
Please update Passster (Premium) – Plugin to Password-Protect portions of a Page or Post 3.3.8 to 4.1. @Steve
Please update Passster (Premium) – Plugin to Password-Protect portions of a Page or Post 3.3.8 to 4.1 @Steve
Please update Passster (Premium) – Plugin to Password-Protect portions of a Page or Post 3.3.8 to 4.1. @Steve
We would LOVE to update to its latest version, but we encountered an issue with the activation with its latest version. We’re unable to bypass the security in its latest version, as it’s making a lot of server API calls. We will update the file as soon as possible once we got a solution for this.
Please update Passster (Premium) – Plugin to Password-Protect portions of a Page or Post 3.3.8 to 4.2. @Steve
Please update Passster (Premium) – Plugin to Password-Protect portions of a Page or Post 3.3.8 to 4.2. @Steve
Hi spadetje_17,
We would LOVE to update to its latest version, but we encountered an issue with the activation with its latest version. We’re unable to bypass the security in its latest version, as it’s making a lot of server API calls. We will update the file as soon as possible once we got a solution for this.
Please read this topic for more information: