Have you checked your error logs on the server? Perhaps PHP is running out of memory (configure it to have more memory) or you’re timing out while loading the page (configure apache to have a longer timeout).
Out of curiosity, what’s the compelling reason to have that many users? If spam management, you might consider (just throwing out an idea) using either Akismet or Spam Karma 2 with Bad Behavior to manage spam instead.
Thanks, it was the php memory setting. I increased it temporarily and can now manage the users.
I have been testing Akismet for a while so I guess now would be a good time to switch over. 🙂
can you tell me how you did the memory setting thing? i am having the same problem
hmmm… i did what it said… but its still not working
here is what the .haccess file looks like now:
# BEGIN WordPress
php_value memory_limit 16M
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /blog/
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /blog/index.php [L]
</IfModule>
# END WordPress
Some hosts may not allow that change in your .htaccess file (as I just read at http://gallery.menalto.com/node/29663) so then you’d need to talk with your host.
Thx man this helped for me too. I got 1000+ users too. I might delete them all and let them post comments without registering!
Is there a downside at the php_value memory_limit 16M option?
We’ve had to set up over 1800 users (local association only wants its members to be able to view board minutes, budget, etc, but wants the flexibility WP provides for most postings and pages). When some admins try to add a user (new member) user.php ends up freezing for some connections (even after waiting 10 minutes for page to load).
We’re using the workarounds via phpMyAdmin and commenting out user.php list of users to try to improve responsiveness. Has anyone developed a plug-in, hack or rewrite of user.php to give admins better and more responsive control over users?
Will try the .htaccess hack. Ideas welcomed.
Well the .htaccess hack caused the following:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, webadmin@//////./// and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.
So I guess we won’t be using that to solve the issue.
