Hide Backend Custom Error Message

  • There used to be an option to customize the message that was displayed when it was set to not redirect users to a custom url. If I remember correctly the default message was “error”.

    I always change this to be a little more unique so if legitimate users are getting locked out I know what the cause is based on knowing that custom error message, vs some other lockout message or even another security plugin’s lockout message or some other error message.

    Now it looks like this option has been removed and it says it will just throw a 403 error, but it is loading a WordPress styled page that says “This has been disabled.” with a few scripts being loaded. I can only assume that this is using a few more resources than the simple error message. One of the great things about the simple error message is that it could handle brute-force attacks without using a ton of resources.

    Is there some other reason I’m not aware of for removing the custom error message and using a WordPress generated 403 page instead?

Viewing 3 replies - 1 through 3 (of 3 total)

  • Hi,

    Enable the “Enable Redirection” feature then you’ll be able to enter your custom message in the “Redirection Slug”.

    The “error” is the default for user lockouts.

    Thanks,

    Gerroald

    Thread Starter Chris

    (@web2guru)

    Thanks for getting back to me Gerroald, but that doesn’t seem right. The “Redirection Slug” would be the part of the URL after the WordPress URL that determines what page to load, and defaults to “not_found”.

    Okay, I think I just got confused between features for a moment. It would be nice though if we could send them to a similar “error” page instead of redirecting them to a custom url/slug.

    I guess one solution would be for me to create my own simple error page (like the one for lockouts), load it into the root folder and put that file name in the slug area. Not sure if that would work but I might give it a try.

    • This reply was modified 8 years, 2 months ago by Chris. Reason: Gotta give my thanks first
    Thread Starter Chris

    (@web2guru)

    My issue is that the “not_found” slug just loads WordPress’s 404 page, which loads all of the theme and plugin resources, which I’d like to cut out to reduce resource usage during attacks.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Hide Backend Custom Error Message’ is closed to new replies.