rcbaguio
Forum Replies Created
-
Was finally able to resolve the problem and in the process learn more about using an alternate approach for the /wp-admin suffix.
The solution is to issue a variant of the /wp-admin access, by-passing all of the errors. This can be done by using: http://www.mydomain.com/wp-login.php?redirect_to=http%3A%2F%2Fwww.mydomain.com%2Fwp-admin%2F&reauth=1. In my case, it was http://www.rcbaguio.org/wp-login.php?redirect_to=http%3A%2F%2Fwww.mydomain.com%2Fwp-admin%2F&reauth=1. This allowed me access to the WP Log In, just like there were no errors.
As I logged-in, the first three errors which were causing the inability to log-in again were displayed– in the WordPress backend. In my case it was the misbehaving staff-directory plugin. Further investigation proved that it was indeed the plugin–or probably some incompatibility with the theme I was using. Deactivating the plugin made the three error messages go away; so it is conclusive that the errors were being caused by the plugin.
Now I know the solution to any wordpress site that misbehaves (won’t allow log in access to the WP backend) when using the /wp-adin suffix is the simple use of the above-given “by-pass” code.
Hope this helps others…
Forum: Plugins
In reply to: Pluggable Line 866This one worked very well for me. I was able to log into my previously inaccessible backend.
In my case, it was the misbehaving staff-directory plugin that was causing the login error.
Thanks a lot to JerryOdom.
Also cannot login (http://rcbaguio.org/wp-admin). Am also very suspicious that my site is being hacked.
I am getting a very similar error message; with the “Warning: Cannot modify header information – headers already sent by…” coming in as the fourth line error.
To triefy: I have just tried to log-into your site and wp-admin suffix already works. Your site is now working properly. If you have worked out a solution, please do share it with me. I will be very thankful.