Control what your users can access and save time, money, and frustrations. Lock down sensitive data in SuiteCRM to specific groups or teams. Supports unlimited assigned users, unlimited group assignments to records, custom layouts for each group, login/sudo capabilities and much more.
#728 - Problem Setting Role permissions
I am using the version of software for SuiteCRM 7.8.1 and am having a problem with assigning permissions on Roles. If I create a new Role and then try and set the permissions it works fine until I have more that 110 modules in the system. What is happening is that the IMPORT permission on the 110th module will not save nor will any permissions from that point onward. If I rename any modules to change the order it still fails at the 110th module. Existing Roles that had permissions after that point are read and displayed correctly but cannot be changed. When I create a brand new Role it creates all the records in the acl_roles _actions table up to the same point of failure. It then just stops creating records. This looks to be some sort of limit in Saving a permission.
I am not sure if this is an issue specific to this add-on but any assistance with this problem would be greatly appreciated.
-
"Thank you so much. Highly recommend the module to work in teams."
Read More Reviews
Larry Rudd
6 years ago
Hi Peter,
This won't be related to SecuritySuite itself, but happy to try to help find the cause. First thing I would recommend doing is to look in your suitecrm.log right after trying to save to see if any database errors are being logged.
6 years ago
Thank you. We eventually found the problem, it is related to the number of modules in our system and a default setting in PHP. There is a setting in the php.ini file that limits the array;
max_input_vars = 1000
We needed to increase that value and then it all worked as expected. The odd part was that there were not errors or anything reported in either the SuiteCRM log or the PHP log.
Best, Peter
6 years ago
Wow! Nice find. I can see now how that could be the culprit. Closing this out, but feel free to open a new case if needed.