CiviCRM Community Forums (archive)

Hi,

With Joomla 3.1.5 and civiCRM 4.3.5, when I try to configure global permissions for a user group, I get a 'Internal Server Error' every time I try to save any change made. I can change and save other component permissions okay. Any suggestions for resolving or working around this issue? I need to configure Joomla/civiCRM so that only a very select group of users and access it via the backend without being able to access other components.

Thank you for responding. Here are some additional details. The problem occurs whenever I try to save any change made in the global configuration for civiCRM via the Joomla global permissions panel accessed via Joomla System > Global Configuration > Permissions > com_civicrm or from within CiviCRM via Administer > Users and Permissions > Permissions (Access Control) > Joomla Access Control. Unlike the other components, when I click on CiviCRM, it takes quite a bit of time for the options panel to show up. I would provide a screen shot, but the editor I'm using here doesn't give me an option to insert an image. The problem occurs when I try to save any changes I make. For example, I want to Allow Access to a group that I call civiCRM admin, so I select that group, then change the action Access Component from Inherited to Allowed. I then select Save or Save & Close. At this point in the process, the systems seems to hang, then after a few minutes, I receive an 'Internal Server Error' stating that the system was unable to complete my request. I get the same results when I try this on a localhost system or production server system.

The error is being reported against a script file that's not part of CiviCRM (Motools) which I think is either a theme or component you have installed. You might research that and see what happens if you disable / change themes. Might also search on Motools CiviCRM compatibility.

CiviCRM does *not* use MooTools.
And in Joomla 3.1.x, MooTools is optional (it used to be the primary js engine in Joomla but has since been extracted in favor of jQuery). so you may be able to disable mootools altogether (assuming you don't have other extensions that require it)

joomla plugin manager.
however... although joomla 3.1 does not require mootools, many extensions still use it. after disabling, you will want to review your site carefully to make sure it works as expected.

the acl's are in a joomla table (joomla stores and manages those settings for civi and other components). maybe in the 'assets' table?

lobo