Thread

This question may be related to a resolved thread.

I have the exact same issue with a site that has multiple member groups and runs MSM with 14 sites. This definitely is an issue with the number of groups/sites and is a real problem. This error now shows up even if not making any change to the member group by just hitting the “update” button. After this error takes place all of the member groups loose their channel assignments and the entire DB has to be restored.

We’ve approached engine hosting about the array size solution mentioned in #9 of the related post [above], however, our original assumption, that there isn’t an array size configuration in Apache was affirmed and this solution was not realistic.

We run dozens of websites, most on MSM and have never run into this.
This site is fully updated to the latest 2.4 with the latest MSM etc…

Please help.

Hi Fuel,

We’ve approached engine hosting about the array size solution mentioned in #9 of the related post [above], however, our original assumption, that there isn’t an array size configuration in Apache was affirmed and this solution was not realistic.

The configuration is not in Apache, but php.ini

Adjusting the amount of data allowed in the POST array is the solution. When editing members in MSM, the Control Panel loads basically *everything* for *everything* and the POST array grows rather large.

If you make the adjustment in php.ini, do the errors clear up?

Cheers,

We’ve tried increasing the post size from 16MB to 32MB before the original post, however before we rule this solution out completely I just asked to double it again to 64MB (which should be large enough for anything). Hopefully we’ll have it done and tested within the next few hours and I’ll post another update.

Thank you for your efforts so far.

Didn’t work. After increasing the POST size to 64MB (started at 16) the problem remains exactly the same. Any other ideas, this is a real issue and will severely impact decisions on using MSM

Hello Fuel,

That is odd. That usually works, this is the first time I have seen it now work.

I am not sure if this is really going to help, but it’s a good place to check.

Can you check these settings out? Max Exec is the one I am curious about.

[b]memory_limit[/b]
This sets the maximum amount of memory in bytes that a script is allowed to allocate.
Default size 5.3 in is "8M"

[b]post_max_size[/b] (must be greater than upload_max_filesize)
Sets max size of post data allowed. This setting also affects file upload.
Default size in 5.3 is "128M"

[b]upload_max_filesize[/b]
The maximum size of an uploaded file.

[b]max_execution_time [/b]
This sets the maximum time in seconds a script is allowed to run before it is terminated by the parser.
Default setting in 5.3 is "30"

Thank you,

memory_limit 128M
post_max_size 64M
upload_max_filesize 10M
max_execution_time 90

Don’t think these are the issue at all.

Hi Fuel,

We want to get a hands on look at this. Be expecting an email from us.

Cheers!

Hello Fuel,

Did you get the email from EllisLab?

Cheers,

Just posting a note here to let onlookers know that we’re working with Fuel privately on this for the time being. I’ll post an update back here once we have something to share!

For anyone with a similar problem, the fix was entirely on the hosting side. Much appreciation to the ExpressionEngine guys for taking their time to help with this.

fix:
max_input_vars = 3000
suhosin.post.max_vars = 3000
suhosin.request.max_vars = 3000

Those settings were at 1000 which was cutting off the array.

Hey Fuel,

I am glad to hear it! And thanks for posting the fix.

If you need anything else, please just let us know by opening a new thread.

Have a great weekend!

Cheers,