jon

This appears to be a Permissions issue on your entire domain, i.e. – above and beyond WordPress. You could probably solve it with FTP or other means, but it is probably best to contact your web host’s support folks as it sounds like something they did.

Before I dig any deeper, it suddenly occurs to me that an easier way to solve your problem would be to use the ‘wp_login_errors’ Filter on Line 861 of wp-login.php and modify the $errors parameter which contains the WP Error object. Do a little testing of the $errors->get_error_code() values and change the ones that you don’t like to ‘incorrect_password’, which will populate the User Name field on line 870.

Let me know if that won’t solve your problem. Thanks!

As explained here http://codex.wordpress.org/Forum_Welcome#Commercial_Products
we cannot help with paid plugins such as Visual Composer in this support forum.

Please contact the folks you bought the plugin from for Support. It was part of your purchase price.

The reason behind this is that we don’t have access to the plugin for our own testing without buying our own copy, so there is no way to help you here.

I’m not a Forum Moderator so I cannot do this for you, but you really need to post this here: https://wordpress.org/support/plugin/wp-super-cache

If you haven’t already, but sure to look through the Support questions and answers there, as well as FAQ and other info for the plugin.

Been there, done that.

Just took a minute to test and I have confirmed that if you delete the Page from Trash, you can then create a new architecture slug.

More confusing than I thought. In the testing I just did, the user name can come from either the browser or WordPress. Here are the three common scenarios:

<p>
	<label for="user_login">Username or Email<br />
	<input type="text" name="log" id="user_login" aria-describedby="login_error" class="input" value="jon" size="20" /></label>
</p>
<p>
	<label for="user_login">Username or Email<br />
	<input type="text" name="log" id="user_login" aria-describedby="login_error" class="input" value="" size="20" /></label>
</p>
<p>
	<label for="user_login">Username or Email<br />
	<input type="text" name="log" id="user_login" class="input" value="" size="20" /></label>
</p>

Two possible answers. I’m not familiar with the Optimizer theme, but this works with most themes: change the Reading Settings to a Static Front Page. https://codex.wordpress.org/Settings_Reading_Screen

If that doesn’t work, post your question here: https://wordpress.org/support/theme/optimizer
as this would become a Theme-specific issue.

Looking back, I see that I have not really answered your question. I should also mention that I think I have been wrestling with the same issue that you are: brute force login attempts.

I initially tried this plugin: https://wordpress.org/plugins/wp-cerber/
It actually does a nice job, but I had to remove it to avoid confusion to other developers on my sites with WP_DEBUG set to TRUE, as it issues some warnings.

I then switched to https://wordpress.org/plugins/wp-fail2ban/

Wanting full coverage of all my sites, I ended up writing my own equivalent of fail2ban because I have some of my Production web sites on shared hosting where I did not have access to fail2ban as I do on my VPS.