FOP2 Extension Buttons not saving Group Tag

sam76

PiaF 2.0.6.2
FreePBX 2.9.0.12
Asterisk 1.8.8.0
Latest FOP2 and latest FOP2admin module for Freepbx

The issue I am having is when trying to add group information to the extensions buttons some of the buttons do not keep the information.

For example I have 139 extensions. After I add the group info to the buttons and submit only the first 125 extension keep this information. The remaining extensions do not show the group info.

nicolas

There is a limit in php.ini that will prevent submiting more than 1000 variables via post, I think you are reaching that limit.

look for max_input_vars in php.ini and try increasing the value.

I will change the design in the module to use ajax in place editing to avoid this silly limit.

Best regards,

sam76

I tried adding 'max_input_vars = 5000' to /etc/php.ini saved it and restarted fop2_server
Still cannot save group to buttons.
The php.ini file did not have a 'max_input_vars = 1000' so i added it.

sam76

Got it working.
Had to restart the httpd service and fop2
Thanks for your help.

jrecho

I was not able to find max_input_vars = in php.ini in /etc/

nicolas

php.ini could be located in several places, depending on your specific distribution/install and versions of everything.

You can find documentation about this issue, that is NOT specific to fop2admin but to php settings in several places in the internet:

http://anothersysadmin.wordpress.com/20 ... big-forms/

http://www.php.net/manual/en/info.confi ... input-vars

You can also upgrade fop2admin to the latest version that has edit in place for the extension buttons, so the value is saved just after edition.

jrecho

I am using elastix 2.3 with FreePBX 2.8 and when I do locate php.ini all I find in one file locates in the /etc/ directory

I simply added the line to the end of the file and it fixed my issue of labels. Now my next question how to I link FOP@ to the recording so that I can use it to listen to recorder calls.

nicolas

A 100% working solution is available on the next fop2 release, the current release will work when you record on the leg of the call that matches the uniqueid that is generated in the CDR (problem is that if you chose the other leg, then the recording is done but not linked to the CDR). So, you will have to wait to the next fop2 release (in any version, you have to edit fop2.cfg and set monitor_exec=recordings_elastix.pl), this script is for the recordings to show in the ELASTIX recordings interface, not in the FOP2 recordings interface. If you use the recordings_fop2.pl file, then it will work in the native recording interface in fop2 (that is disabled in the elastix version), and that works for any recording no matter direction or leg.

Best regards,