Viewing 15 replies - 1 through 15 (of 25 total)
  • Plugin Author Jason Judge

    (@judgej)

    That is very strange – not sure how WordPress would affect that, unless it is a JavaScript change.

    In the header of the admin page containing your form, do you see the code that defines the max-submit limit? It should look something like this:

    <script type=”text/javascript”>
    /* Plugin: WP Max Submit Protect */
    jQuery(document).ready(function($) {
    $(‘form’).maxSubmit({
    max_count: 2000,
    max_exceeded_message: “This form has too many fields ({form_count}) for the server to accept (max {max_count})\nData may be lost if you submit. Are you sure you want to go ahead?”
    });
    })
    </script>

    If you can’t see that, then the form checker would fall back to the default 1000 fields.

    I’ll take a look tonight to see what could be happening, and fix it ASAP. I suspect you are not seeing that code, because something has changed in the way JS is added to page headers.

    In the meantime, either ignore the warning it gives when submitting (just hit “Okay”) or disable the plugin.

    Thanks for reporting this.

    Thread Starter Michael Petschek

    (@mplaidlawgroup)

    That code is actually showing up except it has the stock 1000 instead of the correct max input number, in our case 8000, so is it still safe to save these or should I wait to make any edits?

    Plugin Author Jason Judge

    (@judgej)

    If you have 8000 set on the server (and are absolutely sure 8000 is working) and you have not had any warnings from this plugin so far, then it should be safe to submit the forms.

    If you are *actually* submitting more than 8000 fields and it is just the pop-up message that is wrong, then be careful.

    Perhaps first test this by raising the field limit to 10,000 and see if the error goes away.

    Plugin Author Jason Judge

    (@judgej)

    The plugin will check these values on the server, and take the smallest of them, ignoring any that are not set:

    max_input_vars
    suhosin.get.max_vars
    suhosin.post.max_vars
    suhosin.request.max_vars

    If you can run phpinfo() on your web space, do you see the values for these?

    Plugin Author Jason Judge

    (@judgej)

    …except, of course, you are seeing 8000 in the header of the page, so we know the right value is being picked up.

    Probably a JS issue.

    Thread Starter Michael Petschek

    (@mplaidlawgroup)

    My settings in php.ini are as follows

    max_input_vars = 8000
    max_execution_time = 300
    max_input_time = 600
    memory_limit = 256M

    When I check the phpinfo here https://laidlawsandbox2.com/rakksstore2014/phpinfo.php

    It’s showing max_input_vars as set to 1000, what could have caused this issue?

    Plugin Author Jason Judge

    (@judgej)

    Ah, yes, sorry, I misread an earlier note. The JS is in the header, but the limit it wrong there.

    Okay, if phpinfo() is showing 1000 (in the “local settings” column”) then that is is what the limit will be in operation. If you submit a form with more than 1000 parameters, then you *will* lose data.

    Plugin Author Jason Judge

    (@judgej)

    So, as well as WordPress, what else got upgraded? Do you use the Plesk control panel? PHP gone up a version? Anything else that may have chnaged?

    Plugin Author Jason Judge

    (@judgej)

    Did you get any further with the investigation?

    What we know so far, and correct me if I am wrong:

    * The max limit is set to 8000 in php.ini
    * phpinfo() tells us the local limit is set to 1000
    * The plugin tells us the same as phpinfo()
    * Only WordPress has been updated on the server – or has anything else changed?

    I have a WP 3.9.2 instance, and the max fields of 2000 is being picked up from php.ini

    Thread Starter Michael Petschek

    (@mplaidlawgroup)

    I have tried changing a few fields from php.ini and none of them are being picked up despite having gone in and manually set the php.ini location in .htaccess. Would you have any idea what’s causing this?

    Plugin Author Jason Judge

    (@judgej)

    No, sorry, it’s a bit of a mystery.

    So long as the plugin is reading the same value as phpinfo() is showing, then the issue is going to be in the apache configuration. If the plugin differs from phpinfo(), then I would look further into the plugin.

    Plugin Author Jason Judge

    (@judgej)

    I’m assuming this problem has gone away, since there have been no updates for a while. If it is still an issue, then feel free to re-open.

    I did just have this plugin not working on a site of mine, then realised I had forgotten to put in the “=” for the max_input_vars setting. Adding that, it worked. So my advice is *do* double-check the syntax of the settings and check the settings using phpinfo().

    feelgoodgear

    (@feelgoodgear)

    I am having the same issue, Expect my phpinfo.php does reflect the 5000, but the WP max Submit is displaying 1000 as max.

    feelgoodgear

    (@feelgoodgear)

    My ini has 5000, my phpinfo relfects the 5000. I have a dedicated server as well.

    Plugin Author Jason Judge

    (@judgej)

    @feelgoodgear if you would like to send me a copy of your phpinfo() output, I’ll see if there are any clues in that. There is more than one setting that can limit the number of posted fields, and this plugin takes the view that “smallest wins” to be on the safe side.

    Mail me on jason at academe.co.uk if you prefer not to post the output or link here.

Viewing 15 replies - 1 through 15 (of 25 total)
  • The topic ‘Field limit not reflectin php.ini’ is closed to new replies.