Not Authorized to View This Page

That’s cold.

Verify all file and folder permissions are correct via FTP. Usually 755 for folders and 644 for files. You might try 775 and 664 if the more restrictive doesn’t work.

In any case, that sounds like a mod_security message, of which only your host can manage its rules. You may need to move your site to your host’s WP implementation. Or change hosts? ??

Have been thinking about changing hosts. Will give your permissions a try and see if that helps. I appreciate your response. If I find out an answer, I will be sure to update the topic. Thanks again!

After turning on debug, this is the message we see when going to the login page:

Warning: call_user_func_array() expects parameter 1 to be a valid callback, function ‘admin_account’ not found or invalid function name in /services/webpages/util/b/e/bet337.attwebspace.com/bethelmethodistcolumbia.com/public/wordpress/wp-includes/class-wp-hook.php on line 286

Warning: Cannot modify header information – headers already sent by (output started at /services/webpages/util/b/e/bet337.attwebspace.com/bethelmethodistcolumbia.com/public/wordpress/wp-includes/class-wp-hook.php:286) in /services/webpages/util/b/e/bet337.attwebspace.com/bethelmethodistcolumbia.com/public/wordpress/wp-includes/pluggable.php on line 1251

Warning: Cannot modify header information – headers already sent by (output started at /services/webpages/util/b/e/bet337.attwebspace.com/bethelmethodistcolumbia.com/public/wordpress/wp-includes/class-wp-hook.php:286) in /services/webpages/util/b/e/bet337.attwebspace.com/bethelmethodistcolumbia.com/public/wordpress/wp-includes/pluggable.php on line 1254

We have already installed a fresh copy of the /wp-includes directory. Is there anything else we can do to resolve the ‘admin account’ not found message?

Thanks so much!

Good call with debug. Odd that that results in not authorized. The error message file trace is misleading because hooks are involved. The cause of inappropriate content being sent is usually faulty theme or plugin code. Just stray whitespace outside of <?php ?> blocks on non-template code files can be the cause. Use FTP or the hosting file manager to temporarily rename the plugins folder and rename your current theme’s folder as well. There must be a twenty* theme in /themes/ for WP to fall back to.

You should be able to log in afterwards. You’ll have the wrong theme and no plugins active though. Restore the renamed folders. You can then restore your theme and reactivate plugins. WP should refuse to activate any faulty theme or plugins. Errors can sneak in from the update process or by uploading altered files when the module is already active, but WP can catch them with new activations.