Conditionals page or webform client form may exceed PHP max_input_vars and stop functioning

Thanks this may help find some issues. Do you know what causes this kind of thing?

This is one common result I'm getting now:

POST truncated to 22 input vars. PHP max_input_vars is 10000. Increase
max_input_vars.

Where 22 doesn't look > 10000. Any idea how I can find where it's maxing out from?

Thanks I get email log messages when this happens, so I just added $_POST and we'll see what comes of it.

POST truncated to 36 input vars. PHP max_input_vars is 10000. Increase
max_input_vars.


$_POST => Array
(
     [submitted] => Array
         (
             [name] => REDACTED
             [position] => REDACTED
             [business_name] => REDACTED
             [address] => Array
                 (
                     [street] =>REDACTED
                     [city] => REDACTED
                     [state_province] => REDACTED
                     [zip_code] => REDACTED
                 )

             [what_is_your_companys_website_address] => REDACTED
             [email] => REDACTED
             [phone] => REDACTED
             [sign_me_up_for_enews] => Array
                 (
                     [mailchimp_signup] => 1
                 )

             [are_you_the_primary_decision_maker_for_purchasing] => 1
             [type_of_business] => 2
             [how_did_you_hear_about_us] => Array
                 (
                     [N] => N
                     [X] => X
                     [A] => A
                     [C] => C
                 )

             [industry_magazine] => 4
             [how_many_XXXXX_appointments_do_you_typically_schedule_per_day]
=> 1

[do_you_currently_have_a_licensed_XXXXXXXXX_or_XXXXXXXXX_professional_on_staff]
=> Y
             [number_of_staff] => 1
             [XXXXX_only_products] => Yes

[what_type_of_services_do_you_currently_offer_eg_XXXXXs_XXXXXX_XXXXXXX_etc_]
=> XXXXXs
             [how_many_XXXXX_rooms_do_you_currently_have] => 1
             [how_many_years_has_your_business_been_open] => 2
             [what_is_your_time_frame_for_bringing_on_us] => 1
             [does_your_XXXXXXX_have_a_dedicated_retail_space] => Y
             [do_you_have_multiple_locations] => N
             [what_is_it_about_us_that_caught_your_attention] => Array
                 (
                     [B] => B
                     [C] => C
                 )

         )

     [details] => Array
         (
             [sid] =>
             [page_num] => 1
             [page_count] => 1
             [finished] => 0
         )

     [form_id] => webform_client_form_17817
     [op] => Submit
)

Well the record is being saved... and it quite positive the submissions are legit from the content.

It's live enviornment and it seems not so sporatic as pretty much every error email log matches a submission.

No ajax with webform that I know of...

Everything is heavily cached in a number of ways though... so that may be part of it. I have memcache for most bins, redis for the ones that do or could have big items in > 1MB and DB for form and update cache bins.

They are all anonymous user submissions at first glance and very consistent.

I think authcache forms is removing the form_build_id. Do you think not having that key would be part of the issue?

Thanks no more emails since this commit:)

Dan,

I've been having this issue with webform + modal_forms. Sure enough, $form_state['input']['form_id'] does not exist, which is leading to the message from webform.module. I'm going to try to get to the bottom of why. In the meantime, the error message from webform mislead me a little bit. Can you add a conditional to check if max_input_vars really is the culprit, and handle the result accordingly? I've attached what this might look like against 7.x-4.3 as a simple diff. I can provide a patch against 7.x-4.x but figured you'd want to monkey around with it (or reject the idea altogether), so it wouldn't be worth the effort.

Thanks!
Adam

Dan,

Thanks for responding so quickly!

As suggested I tried the 7.x-4.x development branch. The error went away! Nothing happens when I click the "Submit" button, but I'll work through that now. This webform has just two text fields. If I view the full webform node I can submit. If I view the webform in a modal clicking submit does nothing (no watchdog entries, no javascript errors).

Is there a patch (or patches) I can apply to 7.x-4.3 instead of running the development branch? This project will be going live within the next month, so I'd rather be on a stable release. If the answer is "no" that's fine, I'm just curious.

Thank you again!

It looks like I am getting some JQuery warnings when I click the link to the modal webform. I don't believe this is a webform issue, so I'll continue this over in the modal_forms issue queue if needed.

 Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check http://xhr.spec.whatwg.org/.

UPDATE: The form doesn't work for user id #1, but it works for anonymous users and other users I've tried. That javascript warning exists whether the form lets me submit or not. I'll report back when I find out why user #1 doesn't work, in case it helps someone else.

UPDATE 2: The form was breaking because user id #1 had access to Search Autocomplete and all other users (and anon) did not (because I wasn't finished testing this). So, search_api_autocomplete is causing the webform in a modal to not submit correctly. As soon as I disabled autocomplete on my search form uid #1 was able to submit the form. That was an interesting wild goose chase. I'll stop updating this now and will poke around search_api_autocomplete.

Dan,

Thank you for the followup. I just updated my last comment to say that, in fact, the problems I was having were related to search_api_autocomplete/ctools' modal.js. It took a while to figure that out. Sorry to muddy your thread. Uggh.

Thanks for the info re: 4.3 and 4.4.

I am having the same issue with Webform Ajax. The form submits fine, but when I click on the ajax 'Return to form link', I get the 'Post truncated error' (or if I am an anonymous user: 'This form could not be submitted because it exceeds the server configuration. Contact the administrator.').

After updating webform from 7.x-4.1 to 7.x-4.9

I got the following message when I try to save conditionals on a webform:

This form could not be submitted because $_POST was truncated to 874 input vars. PHP max_input_vars is 20000 and needs to be increased.

I upgraded to the devel version, but I still have the same message when I clic "save conditions".

I cannot edit conditionals anymore.

I tried to increase max_input_vars, but it changes nothing.

What am I missing?

Yes, I am using Suhosin Patch 0.9.9.1.

I have check with phpinfo, max_input_vars for this vhost is equal to the value I set.

If I let default value of max_input_vars (1000) then go to the conditional part of the (huge) webform, I can see this message in yellow:

This form contains 1021 input elements. PHP max_input_vars is 1000 and should be increased.

If I try to save, I have this one in red:

This form could not be submitted because $_POST was truncated to 874 input vars. PHP max_input_vars is 1000 and needs to be increased.

If I increase max_input_vars (for 2000, for example), the first warning disappear, but I still have this message when clicking "save":

This form could not be submitted because $_POST was truncated to 874 input vars. PHP max_input_vars is 2000 and needs to be increased.

even if the value has change...

I also have another message telling me:

More than one conditional hides or shows component "NAME"...

But I don't think it is important in this case...

Yes, that was because of suhosin.

What I didn't know is, that in the php.ini file, I need to increase the max_input_vars but those two too:

suhosin.post.max_vars and suhosin.request.max_vars

My form is now working ok again.

Thanks again!

I realize this is a closed issue, but I just want to report that we're seeing a similar message with several websites on a server that has a max_input_vars of 2000 and is not using Suhosin:

POST truncated to 63 input vars. PHP max_input_vars is 2000. Increase max_input_vars

Could we possibly read directly from php://input if Webform detects that the POST has been truncated?