You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So we've just noticed an issue with the hosting provider of a client.
The default value for max_input_vars in PHP (>=5.3.9) is set to 1000 and cannot be overwritten with a custom php.ini file nor is the hosting provider willing to change the default value. This essentially restricts the number of input variables that can be made per request.
Now, in the OC Admin when adding a coupon, if you click a category it will populate the products field with all products in that category. If the number of products is over 1000 (less if you include the other input vars that need to be posted on the same page) then a PHP error is generated and all extra input vars are truncated. Usually resulting an error like this:
Notice: Undefined index: date_start in /.../www/admin/model/sale/coupon.php on line 17
Are there any proposed solutions or work-arounds for this?
Is it possible to have a "coupon_category" table to deal with category level discounts instead of populating the "coupon_product" table with all products of a given category?
The text was updated successfully, but these errors were encountered:
So we've just noticed an issue with the hosting provider of a client.
The default value for max_input_vars in PHP (>=5.3.9) is set to 1000 and cannot be overwritten with a custom php.ini file nor is the hosting provider willing to change the default value. This essentially restricts the number of input variables that can be made per request.
Now, in the OC Admin when adding a coupon, if you click a category it will populate the products field with all products in that category. If the number of products is over 1000 (less if you include the other input vars that need to be posted on the same page) then a PHP error is generated and all extra input vars are truncated. Usually resulting an error like this:
Are there any proposed solutions or work-arounds for this?
Is it possible to have a "coupon_category" table to deal with category level discounts instead of populating the "coupon_product" table with all products of a given category?
The text was updated successfully, but these errors were encountered: