• Resolved manakuke

    (@manakuke)


    I had previously run into strange occurrence of a few people not being automatically approved per my previous post on the support forum. To avoid that situation, I imported our active portal user base of about 6,700 users.

    I then experienced two different errors where the only commonality is the large number of users (non of these errors occur on sites with small numbers of users).

    On one site where Authorizer was already installed, anytime I try to make a change in Authorize, then save the change, I get the following error:

    Request Entity Too Large
    The requested resource
    /sub-site/wp-admin/options.php
    does not allow request data with POST requests, or the amount of data provided in the request exceeds the capacity limit.
    Apache/2.4.6 (Red Hat Enterprise Linux) Server at http://www.my-site.edu Port 80

    For this error, we don’t have mod sercurity runing on that machine, so it is not the cause. The php.ini settings had been previously modified to adjust the file upload sizes to be 1024MB using the following:

    upload_max_filesize = 1024M
    post_max_size = 1024M
    php_value max_execution_time 500
    php_value max_input_time 500

    I’ve asked our IT to check the Apache settings. Any additional thoughts/ideas?

    What I believe to be related, another site where I had imported the users first crashes every time I activate the Authorizer plugin on the site. It will freeze up the entire site. I have had to delete from the network, then re-install Authorizer for it to work on other sites and to get the site to display (without Authorizer).

    https://wordpress.org/plugins/authorizer/

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author Paul Ryan

    (@figureone)

    I’d look at the following PHP settings as well:
    max_input_vars

    And these in Apache config:
    LimitRequestBody
    RequestReadTimeout

    From my end, I really need to implement a pager so the entire list of approved users doesn’t load in Authorizer settings. It’s high on my list, and that should help you out.

    Thread Starter manakuke

    (@manakuke)

    IT tried something else, maybe what you suggested. I’ve asked them to let me know what they tried. It did let me save, but the result was that it reset all the settings for the plugin. When I try to re-configure, none of the settings save. I no longer get any error messages, but no settings are saved.

    Plugin Author Paul Ryan

    (@figureone)

    They probably fixed the Apache error (413 Request entity too large), but didn’t fix the PHP error (so PHP isn’t processing all the form fields, resulting in Authorizer saving blank values.

    Let me see if I can make a quick fix for you that resolves the problem with lots of approved users.

    Thread Starter manakuke

    (@manakuke)

    Turns out the did have mod security on and it was blocking it. I’m trying to remove all the users and see if it will let me save the settings again.

    Plugin Author Paul Ryan

    (@figureone)

    I just released version 2.3.4 which includes a quick fix that should address your problem. Basically, the user lists are no longer submitted when you save plugin options, so your server should no longer hit the post size limits.

    Backstory: older versions of authorizer included user lists in plugin options, but I factored them out because we were running into concurrency issues when multiple admins edited the lists at the same time. Now, user lists (pending, approved, blocked) are saved immediately via AJAX when you modify them, and not when you click the Save Changes button. This quick fix just removes all of their data from being submitted to the server when you click Save Changes.

    https://wordpress.org/plugins/authorizer/changelog/

    Thread Starter manakuke

    (@manakuke)

    Thanks a bunch. I guess I should have waited before removing everyone πŸ™‚ This should do the trick. I will test out tomorrow. Gotta go home we’re EST and I’m already running late for home πŸ™‚

    Plugin Author Paul Ryan

    (@figureone)

    Get some sleep and don’t freeze! πŸ™‚

    Thread Starter manakuke

    (@manakuke)

    I like the snow and the four seasons, but having spent an extended weekend for a wedding in Laie, I’d be lying if I sad I wasn’t just a tad jealous of your weather and location right now πŸ™‚

    Got the update running. I re-imported the whole batch of users, but would have to add them to Authorizer one by one in order to fully duplicate the set up to see if any further issues arise. Perhaps a future feature request would be to add some kind of bulk import for the Authorize users. I used another plugin to import into the sub-site to hopefully minimize the likelihood if user duplication.

    After the update on another network install, I tried activating the plugin on the site that was causing it to crash with no luck. I’ve previously tried clearing the plugin data and tables from the database, but the system still thought the plugin was active even though I had deleted it (prior to re-installing). I think I have some other issue possibly going on there.

    I’ll mark as resolved and re-open if the previous issue starts manifesting itself again.

    Plugin Author Paul Ryan

    (@figureone)

    Cool, thanks. I like the idea of a batch import, I’ll add it to the list of features to implement!

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

The topic ‘User Number Limit?’ is closed to new replies.