• Resolved SRD75

    (@srd75)


    Hi,

    I have a site in MU mode.

    Since Thur 4 December, after I login, any clicks to backend features redirect to the login page.

    I’ve tried deactivating all plugins, which didn’t fix things, and. restoring the DB to Wed 4 Dec, but that fails too. Putting Wordfence into Learning mode doesn’t fix things either.

    There is a console error:

    admin-ajax.php 400 error
    load-scripts.php?c=0&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils&ver=…

    Would love some help please.

Viewing 8 replies - 1 through 8 (of 8 total)
  • Hi @srd75

    I hope you are doing well today.

    I see you have mentioned that you have only restored the database. What about a full site restore, including files? Maybe there is some other rule in the htacccess file that causes this issue? Note that such a restore will possibly affect losing uploaded images for example.

    Please review also your wp-config file, is there something suspicious there.

    Note that on December 2 WordPress 6.9 was released and maybe that could cause some issues.

    Kind Regards,
    Kris

    Thread Starter SRD75

    (@srd75)

    Thank you both so much, it is very much appreciated.

    Creating a new .htaccess file with default .htaccess code from WordPress >=3.5 Subfolder Example, the problem was solved (temporally).

    • This reply was modified 4 months, 1 week ago by SRD75.
    Thread Starter SRD75

    (@srd75)

    I see an error in error_log:

    [05-Dec-2025 16:27:06 UTC] PHP Fatal error: Uncaught Error: Call to undefined function wp_is_valid_utf8() in /home/user/public_html/wp-includes/formatting.php:1140 Stack trace: #0 /home/user/public_html/wp-includes/formatting.php(5649): wp_check_invalid_utf8() #1 /home/user/public_html/wp-includes/formatting.php(5591): _sanitize_text_fields() #2 /home/user/public_html/wp-content/plugins/litespeed-cache/litespeed-cache.php(96): sanitize_text_field() #3 /home/user/public_html/wp-settings.php(476): include_once(‘/home/user…’) #4 /home/user/public_html/wp-config.php(58): require_once(‘/home/user…’) #5 /home/user/public_html/wp-load.php(50): require_once(‘/home/user…’) #6 /home/user/public_html/wp-blog-header.php(13): require_once(‘/home/user…’) #7 /home/user/public_html/index.php(17): require(‘/home/user…’) #8 {main} thrown in /home/user/public_html/wp-includes/formatting.php on line 1140

    • This reply was modified 4 months, 1 week ago by SRD75.
    • This reply was modified 4 months, 1 week ago by SRD75.
    Thread Starter SRD75

    (@srd75)

    That fatal error is no longer present after manually reinstalling WordPress 6.9. but the redirect after clicking any link in the backend still occurs.

    Thread Starter SRD75

    (@srd75)

    I tried creating a new admin account in phpMyAdmin.

    I can login to the primary MU site, but if I follow the advice of this page, I still don’t have super admin rights.

    The site_admin field has data a:2:{i:0;s:3:"ABC";i:1;s:4:"ABC2"}

    How do I make this new user (ABC2) a super admin?

    Thanks

    Hello @srd75

    Best and safest solution is to use WP-CLI to create super admin users when you can’t acesss the admin network to make a user super admin but if your hosting doesn’t support it.

    Check in the database: wp_users → user_login and ensure there is an entry is user_login = ABC2.

    Its case sensitive, so please make sure it exactly matches your username. You can find a full guide in this article:
    https://www.wpbeginner.com/beginners-guide/how-to-add-a-super-admin-user-role-in-wordpress-multisite/

    Best Regards
    Amin

    Thread Starter SRD75

    (@srd75)

    Hi Amin,

    There was a username ABC2 in wp_users.

    I’ve used WP-CLI to manually create a new super admin abc4.

    However, no MU network features work, they immediately send me back to the login screen.

    Thread Starter SRD75

    (@srd75)

    Thankfully, my web host was able to resolve the issue. So happy.

    Their message was:

    We had to make a change in one of your database tables, as well as the wp-config.php file in your public_html directory. The issue appeared to be due to a mismatch between the wp-admin loading over www and the specific database table and config file not having www appended to the domain name.

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

You must be logged in to reply to this topic.