problem: Only some blogs did not show the dashboard (but did show all other admin pages). I have left this problem for some time (months) since Googling did not bring up anything relevant and I was too lazy to investigate (and could work around it by logging in, getting a 500 error and then press back and click comments). In my mind were .htaccess changes it did, plugins that drop bad rss feeds etc...but... it was core.

So today I went commenting out all passages in dashboard.php and unfortunately it was Murphy since the problem was with the bottom line...

add_action( 'activity_box_end', 'wp_dashboard_quota' );

In which I commented the line

//$used = get_dirsize( BLOGUPLOADDIR ) / 1024 / 1024;
    // returns: 1418.9275159836

Whereafter my dashboard was so speedy that I got tears in my eyes.

I'm logging this here since I hope people searching for the problem now will shortcut time and recognize the reason. Especially with the combo: 500 and admin dashboard.

Question: I assume that the bigger the uploaddir gets, the slower dasboards will load for blogs. I also assume that this happens for every blog out there since this is a line in core.

Am I correct and could I log this as issue or am i stupid - missing something essential that does not cause this to be problem for every multisite blog with large quota after some time?

Now I connected 500 and getdirsize I found http://trac.mu.wordpress.org/ticket/1175 and http://trac.mu.wordpress.org/changeset/2027 ......

In there a transient check was implemented by james collins. What happened to the transient check? that would resolve this I think.

The transient check as implemented in ticket 2027 is still in place (see Rarst answer below) and disabling the quota completely will also shortcut the 500 error since that is what is checked in wp_dashboard_quota.

So: if you do not disable the quota it means you will get a 500 error eventually if you have a large quota limit. IMHO that could be improved / ticketed or not?

1 Answer 1


The transient is in place just fine, see get_dir_size() source.

Note that if you have enough files for this to cause major performance issues you are probably better disabling upload limit or it might mess up other related functionality like uploads.

  • it means that if you do not disable it ('upload_space_check_disabled') that you get a 500 error eventually so would that be a reason for a ticket or is it considered "ignorant user" grin ? (thanks for the reference to the get_dir_size, i now saw it was still there)
    – edelwater
    Mar 7, 2011 at 22:57
  • 1
    @edelwater it would be my idea that this can't really be solved or fixed. To limit upload space you need to know how much space is spent. To know that you need to count it at some point. The only way to bypass counting (that I see) is to disable limit altogether.
    – Rarst
    Mar 7, 2011 at 23:03
  • sounds valid. so i will leave the question and hope people who run into the same now find it in google so they know what happened. (it is stupid but i really had this open for a long time because i could not find it in the google hits and was too lazy to dive in it).
    – edelwater
    Mar 7, 2011 at 23:30

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.