Opened 2 years ago

Last modified 16 months ago

#16853 accepted enhancement

Error 500 when a user has too many sites

Reported by: luuzan@… Owned by: PeteMall
Priority: normal Milestone: Future Release
Component: Administration Version: 3.0.1
Severity: minor Keywords: needs-patch
Cc: edward@…

Description

My installation

3.0.1 multi-site installation with more than 7500 blogs, with one user each. I also have one moderation user that can administer each of the blogs.


The issue

In the admin interface, when I go to Super-Admin -> Users, and when I display the page that contains my moderation user, I get "An error (500 Internal Server Error) has occured in response to this request". The page tries to display all the sites administered by him (around 7500 of them), hence the error.


Updating to 3.1 didn't resolve the problem.


Recommended enhancement

For each user in the list, display only a certain number of sites, with a possibility to see all of that user's sites, if needed.

Change History (11)

have you turned on debugging?
and increased php memory_limit

Turning on debugging didn't help.

Even if I had increased the "memory_limit" setting, I don't think it would be a good idea to display all of the 7000 and something sites on one page at once.

  • Keywords needs-patch added
  • Owner set to PeteMall
  • Status changed from new to reviewing

Yeah, we should paginate this. What's the URL that breaks? Keeping in mind the network admin changes in 3.1.

The admin has changed quite a bit since I have reported this issue (3.0.1). Today I have 3.2.1 running and the URL is

/wp-admin/network/users.php
/wp-admin/network/users.php?paged=x

Last edited 22 months ago by luuzan@… (previous) (diff)
  • Milestone changed from Awaiting Review to Future Release
  • Status changed from reviewing to accepted
  • Cc edward@… added

I don't suppose y'all could include a dump of your db?

Those wanting to help probably don't want to create 5000 sites manually...

comment:8 follow-up: ↓ 9   luuzan@…16 months ago

Unfortunately, with over 8000 sites, we cannot afford that.

Replying to luuzan@…:

Unfortunately, with over 8000 sites, we cannot afford that.

Then I'm not really sure that anyone can "afford" to help you if you're not willing to make it easier for people to find the bug and fix it.

The street goes both ways, eh?

Just do a DB dump, leave the post tables empty, just to give us lots of sites to play with and try to paginate. No harder than that and the dump won't be more than about 250kb big, I imagine.

Then I'm not really sure that anyone can "afford" to help you if you're not willing to make it easier for people to find the bug and fix it.

I don't think anyone reporting a bug should be expected to provide a database dump for that simple purpose.

It's not hard to create many blogs/users/posts in a loop, unless it's a bug related to a specific configuration which shouldn't ever happen, there's no need to take that tone.

Do you really need an 8000 site dump to be able to develop that simple a pagination ?

Note: See TracTickets for help on using tickets.