WP Max Submit Protect

  • Resolved DavidMHall

    (@davidmhall)


    9 years, 8 months ago

    Hi,

    I am having problems in adding Variable records. I have been analysing this problkem for awhile and if I add 10 records at a time everything is good until I add another 10 to make 50. The update process starts to disable a few records. I came across your plugin (and I am very grateful for you making it available) however all is not going well or I do not understand something. I had previously updated the max_input_vars = 4000 in the php.ini file (it is currently set at 2000) and I ran your program while updating 50 records. The message from your plugin advised me that there was too many fields (1159) and that the max was 1000. I was not sure if this 1000 max was on the Server or in your plugin. I edited your plugin to change protected $default_limit from 1000 to 2000. However I get the same result i.e. max is 1000.

    You can read my confusion php.ini is definitely set at 2000 as is your plugin. Can you advise. I maybe niave on this matter.

    Many Thanks. David. P.S./ I have been working on the variable update problem for a few days – getting desperate.

    https://www.ads-software.com/plugins/wp-max-submit-protect/

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter DavidMHall

    (@davidmhall)

    Hi,

    I have done a little more reading and can i ask whether your plugin would work on a Shared Web Hosting site? I ask this as I am not sure if i should be making the changes to the .htaccess file or the php.ini file.

    It would be useful to me to know which file your plugin works with to identify the max_input_vars.

    Thanks.

    Plugin Author Jason Judge

    (@judgej)

    Hi David,

    The plugin will work on any hosting – dedicated or shared. What may not work, however, is your ability to change the max_input_vars for your site – that may be restricted by the hosting.

    If you run a phpinfo(); script in your home directory that will tell you what all the server settings are. If you have changed it above 1000 in php.ini or in .htaccess, and it is still showing 1000 in phpinfo(), then either this is a setting that you cannot change on that hosting service, or your changes are maybe not done in the right place.

    If you do a Google search for “how to set max_input_vars” there are plenty of tutorials around that show you how to set it, how to check it has worked, and what restrictions there may be on various hosting services. There are many ways hosting can be provided, so I can’t give you a single solution that will always work – a tutorial specific to your situation would be the best thing to try and find.

    Good luck, and let us know how it goes ??

    — Jason

    Plugin Author Jason Judge

    (@judgej)

    BTW It looks like future versions of WC will be taking a more AJAX approach to variations, so this may be a problem that is solved in a very different way in the future. We’ll keep our fingers crossed.

    Thread Starter DavidMHall

    (@davidmhall)

    Hi Jason,

    Many Thanks for your reply. I really do appreciate the work you and others do to help the novices. I did run a phpinfo script that confirmed the value (max_input_vars) as 1000. I then “chatted” with my Provider who asked that I submit a formal ticket ato the Developers as this matter was beyond his ken. When i have a firm answer I will update.

    Best Wishes.

    Thread Starter DavidMHall

    (@davidmhall)

    Hi Jason,

    Well it took a while – 1 week – but my Service Provider came through and increased the max_input_vars to 6000 and we have been humming along pretty good ever since (see below). Your input helped me articulate the problem sucessfully. Many Thanks.

    looks like you were missing the call from the .htaccess file to your php.ini file, so I added the following to your .htaccess file:
    <IfModule mod_suphp.c>
    suPHP_ConfigPath /home/dmhall
    <Files php.ini>
    order allow,deny
    deny from all
    </Files>
    </IfModule>

    Your max_input_vars were successfully increased.

    Plugin Author Jason Judge

    (@judgej)

    Glad you got it working, and managed to catch this potential problem before it resulted in a loss of data ??

    — Jason

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘WP Max Submit Protect’ is closed to new replies.