manythings

No it has not been resolved. See the question in the very first line – no one has mentioned it, much less answered it.

However I realized just this second that the thread title and body text got hopelessly garbled (parts missing and cut off) when I copy-and-pasted it from the main www.ads-software.com How-To forum, where I originally posted it and a responder said it belonged here.

So, because this forum doesn’t allow edits, unlike all other forum sites on the planet, I am going to start a new thread and while I’m at it I will reword the whole post for clarity.

Got it, thanks – I understood your original post about Time Length of Lockout. I was branching out to related questions about other lockdown options and user accounts. Sorry if that wasn’t clear. If necessary I can put those into a new thread.

Great, thanks.

These are my current values. Shouldn’t I make them a lot stricter (fewer attempts, longer time period)? No one else is ever going to need to log in to my blog. I should probably just disable user accounts altogether if that’s possible, apart from my own. I don’t even know what they’re for – running a blog with multiple authors? I won’t ever be doing that.

Max login attempts: 20
Login retry time period: 10 min

It depends how small your Time Length of Lockout value is.

Where is that? Not under settings where it should be so I went through everything else but couldn’t find it. Obviously it must be in there somewhere.

My plugins are:

Email subscription
Subscribe Button by AddToAny
WordPress Importer
WP Statistics
WP Super Cache

Akismet but it is not activated. I don’t know why. I never would have deactivated it unless some specifically said I had to because it there was something wrong with it or it conflicted with something more important.

OK thanks, didn’t know that forum existed.

All In One WordPress Security and Firewall 3.8.9

Terrific, thanks

I spent an hour and a quarter on the phone with the hosting service (so they’ll be losing money on me for the next 6 months!) and they said they’d never seen anything like it. They wiped the cache clean, moved things around, removed all the posts and all the themes, then imported ‘clean’ posts and themes from another blog.. you name it. Still the problem returned after reinstalling the theme in question.

The problem occurred only in IE, Firefox and Opera. Chrome would refresh the page properly. This held true both for me at home and for the hosting service help desk. – and like I said, not for another blog with identical posts, theme and settings.

Whatever it was, was buried deep within WP or the servers and for all practical purposes the damage was irreversible. So I had to delete the corrupt blog entirely then re-create it.

OK thanks. I can log in now. The problem turned out to be that the web host address I added at my domain registration service took a couple of hours to propagate and until that, wp-login.php was taking me to the generic “this domain has been registered” page. I thought there must be some some other setting I didn’t know about but there isn’t.

Yep, that should do it. Thanks. I’m a bit scared away by the statement that local installs are for ‘development’ but fingers crossed it will be usable by a non-developer such as me.