title: PHP Warning: Unknown: Input variables exceeded 1000
body: <p>I am getting a new php warning when a POST data from a form on my page to my server. The warning is as follows:   </p>
  
  <blockquote>
    <p>PHP Warning:  Unknown: Input variables exceeded 1000. To increase the limit change max_input_vars in php.ini. in Unknown on line 0, referer: <a href="https://mywebsite.com/index.php" rel="noreferrer">https://mywebsite.com/index.php</a></p>
  </blockquote>
  
  <p>The thing is that my form does not have near 1000 input variables, so I am baffled as to why this is appearing. As a side note, I have not had this problem until recently and I suspect that when I ran <code>yum update</code> something changed/was installed that is causing this. Any advice or answers are appreciated.</p>
  
  <p>EDIT 1:
  So I did <code>var_dump($_REQUEST)</code> and got ~1000 single character strings. The first couple items in the array are what they should be, but then a bunch of stuff that I don't need submitted is broken down into single character strings. Thoughts welcome.  </p>
  
  <pre><code>array(1001) { 
      ["action"]=&gt; string(10) "step1_show" 
      ["submit"]=&gt; string(6) "Step 1" 
      [0]=&gt; string(1) "a" 
      [1]=&gt; string(1) "c" 
      [2]=&gt; string(1) "t" 
      [3]=&gt; string(1) "i" 
      [4]=&gt; string(1) "o" 
      [5]=&gt; string(1) "n" 
      [6]=&gt; string(1) "=" 
      [7]=&gt; string(1) "l" 
      [8]=&gt; string(1) "o" 
      [9]=&gt; string(1) "g" 
      [10]=&gt; string(1) "o" 
      [11]=&gt; string(1) "u" 
      [12]=&gt; string(1) "t" 
      [13]=&gt; string(1) "&amp;" 
      [14]=&gt; string(1) "p" 
      [15]=&gt; string(1) "r" 
      [16]=&gt; string(1) "o" 
      [17]=&gt; string(1) "p" 
      [18]=&gt; string(1) "e" 
      [19]=&gt; string(1) "r" 
      [20]=&gt; string(1) "t" 
      [21]=&gt; string(1) "y" 
      [22]=&gt; string(1) "=" 
      [23]=&gt; string(1) "3" 
      [24]=&gt; string(1) "7" 
      [25]=&gt; .....     
  </code></pre>
  
  <p><strong>ANSWER</strong>: It ended up being a problem with my submit handler. Thanks all for your input.</p>