K. Tough

Replace line 21 with:
array( 'PHPInfo_Page', 'display' )

And you did uncheck Store Encrypted Passwords under the General tab? If so, and keeping it unchecked doesn’t change anything, there may be some caching occurring on your host.

If you’re saving the hashes as transients, they’ll rehash automatically over time as your visitors visit pages/posts with Content Protector forms. Hopefully, you first followed the link above where it’s explained that the Standard DES algorithm only looks at the first 8 (eight) characters in generating a hash. That is, any two strings that share the first 8 characters in common – regardless of their actual lengths – will hash the same way in Standard DES and can unlock your content if your password also starts with those characters. This is a limitation of the Standard DES algorithm itself.

Did clearing out the transients work for you?

Hi, cazamic.

I haven’t heard of any; I think that’s browser-specific and nothing you could force server-side one way or the other.

Hi, alschi.

No reason why that shouldn’t work; I take it the link works otherwise? Is the link static, or is it dynamically generated (if it’s built on-the-fly w/ Javascript, there could be a conflict somewhere that messes your link up and causing the 404)?

Are you saving the password hashes? You’ll need to clear out the transients as well, as your password needs to be rehashed.

Hi, comalloy.

Look here first: https://www.ads-software.com/support/topic/first-8-characters-of-password-allow-access-to-restricted-content/

That looks like it should work as you intend. You’re only specifying a year for the Initial Event, the the rule figures out all the subsequent years.

You can make two rules: one that acts on weekdays from 4 – 10 PM, then another rule that starts Saturday 12:00 AM to Sunday 11:59 PM. You’ll have to put the same content in each set of shortcodes.

Unfortunately, there is no way to time your content based on the user’s timezone, only on whatever timezone you set for your shortcode.

Yes, I haven’t updated the screenshots in a while. I probably should. ??

Your email had said the plugin stopped working for you. Did you update WordPress or another plugin around the same time?

Hi, alltheleavesgreen.

The plugin uses a shortcode to set things up (also, it’s for protecting a portion of a Post; WordPress already has built-in capabilities to password-protect a complete Post). The docs you’re looking for are at https://www.ads-software.com/plugins/content-protector/other_notes/, and there’s also a button in the editor that brings up a dialog to help you build the shortcode. Hope that helps.

Hi, jrkt.

You can already protect an entire individual Post using WordPress’s built-in password protection, if that’s what you’re trying to do.

Hi, AmandaEve.

That depends. If you want to post for two specific hours (i.e., between 7:00 and 9:00 on August 22, 2016 in your timezone), then, the [timed-content-server] shortcode will work perfectly. As for changing the Category, you could try hooking into the timed_content_server_hide action, and changing the category if the current time is later than the time in the hide attribute of your shortcode (both post ID and the hide date/time are available to you in your hooked function). Note that this will require writing your own PHP function to hook into the action. There are more details on the actions on the “Other Notes” tab on the plugin page.

Sorry for not getting back to you sooner. First (and obviously), is your browser accepting cookies? What are you using for a shortcode?