Chris Wiegman

I just pushed a fix. The issue should only be applicable if you were logging in https. My apologies and thanks for your patience.

@lomar mind contacting me directly on some of what you’re finding? You’ve been most helpful but these forums are less than stellar for keeping track of issues. You should be able to find me by name on nearly any major service.

Thanks for the report. I’m going to do one more bug fix tomorrow before I switch gears for a couple of weeks. I’ll get a fix in there.

The username lockout was changed in 4.2.8 and it will no longer stop the locked out user from logging in on a locked out host.

@lomars Good catch on that, I was so busy with the lockouts themselves that I missed a parenthesis on that display. IF your IP is in the whitelist it should not be locked out either way. Upon the next update it will correctly register under “Is this computer white-listed.”

Currently you cannot block a Country as a whole without knowing the correct IPs to block. This is a feature we are working on for future versions.

The current version has been tested with PHP 5.2, 5.3, 5.4 and 5.5.

That’s actually exactly what it should do. If you want to whitelist the IP you can do so in global settings but keep in mind that if you know you are getting attacked you will have just opened up your system for that ip to keep trying until he gets in.

Took some investigation but for the last year or so the ID on my comment section div was “respond” Looks like that no longer jives with Jetpack.

Hi Tim,

I’m willing to update. Not being a plesk user myself I can see where having plesk set a location for all php could cause issue. Can you contact me directly (Same username on Twitter and nearly every other network) and I’ll get you a version to test?

Update to 4.0.16. The issue was a result of a time zone mismatch that I frankly missed under all my test conditions. 4.0.16 matched the date equalizer to the correct time zone.

Good catch. Just fixed it in our dev version and it will be in our next release early next week.

@billfry Thanks. The contact form is best ??

Backup emails are under global settings. Not only can you send to any email but also to multiple emails if so desired.

@billfry: contact me directly. It isn’t something I’ve seen in testing or beta and would I would love to get to the bottom of it.

The hide backend function was completely rewritten and no longer uses the key. Watch the modal when viewing at the settings. You do have to reset hide backend (if you don’t use wp-login.php to get in).

As much as I would like to say there is a better way to handle the upgrade of this feature the fact is it is just too different from the previous feature. Please use the default until you check your settings.

My apologies. Found the reason thanks to data in another thread and pushed 4.0.2. Thanks to Matt Zak for the data to help me pinpoint the issue.

If y’all find anything further please contact me directly. As much as I would like to say I can test for every combination of config and server it just isn’t possible. With a little patience we’ll have these issues nixed shortly.