Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter vatnoise

    (@vatnoise)

    Not sure if this is related but wasn’t able to reproduce this on the localhost copy of the same website. And when I try to do the scanning on production server it doesn’t do anything. Can this all be related to permissions? The folders have 755 and files 644.

    Thread Starter vatnoise

    (@vatnoise)

    Ok, now after 30 min it’s all looking okay. I don’t think I did anything!

    I’m confused.

    That’s what the admin looks like when the css fails to load. Wordfence was probably making too many demands at the moment and your server was balking. The WF Scan is pretty demanding, in my case I unchecked a bunch of stuff (for example, no way it’ll ever scan my image uploads, which number in the tens of thousands) and only run it once a week at off-peak hours. MTN

    Thread Starter vatnoise

    (@vatnoise)

    It might be that, although in the “Scan Summary” it doesn’t show anything when I try to run a scan, only if I try to kill a scan. :/

    Although scanning works on the same website on localhost, so not sure what I need to tweak on production to make it happy.

    Thread Starter vatnoise

    (@vatnoise)

    I think adding define('CONCATENATE_SCRIPTS', false); to wp-config.php before the first require_once fixed css.

    Although still struggling with the scan.

    Hello vatnoise,
    if setting CONCATENATE_SCRIPTS to false fixes a problem, it means there is a problem in some script file that WordPress is trying to concatenate (load together with a bunch of other scripts). CONCATENATE_SCRIPTS is only used in WordPress admin.

    To debug this, browse your WordPress admin while keeping a browser console open. You should see some javascript errors there that will give us a better idea of what the problem is.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Admin Dashboard css gone mad’ is closed to new replies.