Thread Starter
LSBK
(@lsbk)
Other conflict
Running 404page in compatibility mode together with SecSign will inhibit logins…
Thread Starter
LSBK
(@lsbk)
Second complaint solved, as “www.xy.net/login” will produce an error, use …./AP-Admin instead…
Thanks for pointing to that. After taking a look at the iThemes Security code I can say that their 404 error logging obviously can not work. The iThemes Security 404 error detection runs after 404page has loaded the page to be displayed as 404 error. Loading the page clears the 404 error, so it’s not possible to detect it. Yet I have no idea how to solve this, but I’ll think about it…
Peter
Thread Starter
LSBK
(@lsbk)
What about an error-404 log list?
because that’s needed anyway to correct errors/mistakes.
iThemes Security has a feature to ban IP addresses that cause 404 errors to protect the site. Therefore 404 logging has to work. That’s why I prefer to solve the problem instead of avoiding it.
OK, I think I’ve found a solution.
Are you willing to test it? You can download the current development version of the plugin from https://downloads.wordpress.org/plugin/404page.zip. Activate the new “Force 404 error after loading page” feature.
Please note that this version is still in development, so not everything may work properly.
Peter
I’ve finalized version 3.0 just now. Please let me know if it works for you.
Peter
Thread Starter
LSBK
(@lsbk)
SUPER!
It works fine now.
I checked the “Force 404 error after loading page” and “Disable URL autocorrection guessing”. I get my “page not found page” and a usable log entry.
Thanks!
