Home › Forums › Product Support Forums › Ajax Search Pro for WordPress Support › Can't save advanced options – save gets cut off
This topic contains 3 replies, has 2 voices, and was last updated by Ernest Marcinko 7 years, 9 months ago.
- AuthorPosts
- November 30, 2016 at 11:35 am #11037
We have one more problem- we cannot save advanced options on our installation. We can type in them but whatever we do they are not getting saved.
Even if we change their value in MySQL the value of the input in the backend does not change.
For example when we want to change Advanced Title Field (default: {titlefield}) in Advanced settings the value of the field always stays the same.
Please advice.
November 30, 2016 at 11:53 am #11039This might indicate a server related issue, but impossible to tell without actually seeing the code.
I remember someone had a similar problem a long time ago, and it was caused by an incorrect configuration in the php.ini, where the max_input_vars PHP directive was set to a low number, and not all the options were posted.
You can try adding the following lines to the .htaccess file in your root directory, but it might not work:
php_value max_input_vars 3000
You will probably have to check and change the php.ini configuration file on your server as well, to confirm if the max_input_vars value is indeed set to a lower value as the default 3000.
Best,
Ernest Marcinko
If you like my products, don't forget to rate them on codecanyon :)
November 30, 2016 at 2:10 pm #11053I’ve added some options to php.ini but nothing seems to help. I used phpinfo() to make sure the changes went live and they did.
Values i tried to change:
max_input_vars = 50000 (tried also 3000, 5000 and 10000, default was 1000)
max_input_nesting_level = 256 (default was 64)
post_max_size = 128M (default was 8M)Can you give me any other clues?
November 30, 2016 at 2:18 pm #11054I honestly don’t know. It is possible that the POST array is still cut off for some other reason, or there is an error message returned either when processing or saving the options. There is also a tiny chance that another plugin or code is conflicting for some reason. My guess is that this is something unknown yet, as the max_input_vars would have perfectly explained it.
Best,
Ernest Marcinko
If you like my products, don't forget to rate them on codecanyon :)
- AuthorPosts
You must be logged in to reply to this topic.