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.
#1967 - Users cannot see module after install 7.11.4
SuiteCRM 7.11.4
Security 3.1.115 (7.11.4)
We have completed this upgrade and this version is locking out the 'AOS Quotes' module for a number of users
Even though their role states they can view, edit etc Even if the user is then changed to an admin
The error is the ajax one Turn ajax off - module fails for the user
This is only happening on certain users, other users the module works fine
Please can we connect to discuss in more detail Thanks
-
"The add-on itself was already a must for my SuiteCRM, which was missing this very important security feature. However, what surprised me the most was ..." - Davint
Read More Reviews
Larry Rudd
5 years ago
I haven't heard of anything relating to SecuritySuite for this type of error before. Do you see anything in the server logs or crm log around that time? Anything in the browser console for the response of that request when that error happens?
Seems unlikely SecuritySuite related, but perhaps any answers to those questions may change that.
5 years ago
the following request fail using ajax ui
ttps://staging.XXX/index.php?module=AOS_Quotes&action=index&parentTab=All&ajax_load=1&loadLanguageJS=1 Status Code: 500
RESPONSE:
Enrolments
https://staging.XXX.co.uk/cache/index.php?entryPoint=getImage&themeName=SuiteP&imageName=dashletclose.png Status Code: 403 RESPONSE: server specific 403 error page.
When viewing index.php?module=AOS_Quotes directly without ajaxUI only the module header is printed within the pagecontent element.
no footer.
no messages are logged within the suitecrm log default located at suitecrm.log or within the server error log
5 years ago
Looks like a potential issue with AOS_Quotes. I suggest reaching out on Github to the SuiteCRM project about this issue. If it were SecuritySuite related I would expect some errors in the logs around the securitygroups tables.