The Post Password Token plugin allows readers to access protected posts without having to enter a password by creating secret token urls for the post.
Not much. After you install the plugin all you have to do is set a password on a post using WordPress' standard Password Protection Functionality. After the password is set and you've saved the post there will be a new meta box on the post edit screen (in the center content area, below the post-content editor) that will present you with a full URL to the post including the token. Distribute this URL to give people automatic access to your post.
Yes, this still functions as normal.
Accessing a password-protected post by its standard url will still show the expected password dialog, but when a reader accesses a password-protected post by its secret Password Token url, they will be automatically authenticated and be able to see the full content.
No. Since the tokens aren't stored but instead generated when needed there's no need to to do anything but navigate to the post edit page for your protected post to retrieve your token.
The url itself lasts forever, unless you change it. Additionally, accessing a post by its secret url will set an authentication cookie for the user that lasts for 10 days.
If you need to revoke the secret urls for an individual post, you can simply change the post password. Once you save the post it will create new secret urls and invalidate the old ones: the old url will no longer automatically log readers in and they'll be asked to enter a password if they use that URL.
You can also revoke all secret urls site-wide (the "nuclear" option). To do so, go to the plugin admin page and change the password salt.
Yes. The token in the URL triggers a unique cache. Be aware that this does create a potential security risk. Not huge, but potential. If you don't want these pages cached then use the settings in your caching plugin to keep urls with
ppt= in the url from being cached.
If you've run into unexpected behavior while using the plugin, please file a bug report at http://top-frog.com/contact.
Requires: 3.0 or higher
Compatible up to: 3.6-a
Last Updated: 2013-5-19
1 of 3 support threads in the last two months have been resolved.
Got something to say? Need help?