Passster comes with a pretty minimalistic set of options. I hate bloated options pages with hundreds of confusing settings. So instead Passster focussing on a low amount of settings and use clever defaults to maximize the user experience.
Let’s begin with the general options included in Passster.
The first option let you decide if you want to use a cookie to save a users password or not. It’s activated by default cause that’s exactly what most users want.
When a user unlocks your content, the solution is stored in a cookie so the user doesn’t have to unlock it again for the set amount of days in the setting Cookie duration.
Before 3.3 Passster requires a reload of the page after a password was submitted. In some cases, this is still a valid use case for example to ensure compatibility with other third-party plugins or custom coded solutions. To step back in time you can activate this option and deactivate the instant ajax unlock in Passster.
Besides setting the AMP parameter in the shorcode you also have to activate this option. It includes a script for AMP pages to ensure that the button can be clicked and the form submits within AMP.
This is one of the parts which will heavily be upgraded in future versions of Passster. For now, it’s only available for WPBakery Pagebuilder. It’s a custom module to protect rows with Passster. More on that in the following tutorial.
Note: The full-page protection of Passster works quite well in Visual Composer, Elementor (and Elementor Pro) as well as for Beaver Builder (and Beaver Builder Pro). The Divi builder is currently not officially supported.
This should be pretty self-explanatory. It deletes all options, metadata and password lists when you uninstall Passster.
This area of the settings is dedicated to external services. That’s the place where you would like to add all your API keys and secrets to use with Passster. For now it’s only the Google ReCaptcha but that will be enhanced soon.