Cannot Save Joomla Access Control changes

[speedyrob]

HI

I didn't see this in any other post, so I hope I'm not repeating an issue.

If I go to CiviCRM > Administer > Access Control

And then I go to Joomla Access Control, there are no buttons to SAVE or RESET any changes that you make.

[Donald Lobo]

i tried this out on our sandbox joomla server:

http://sandbox.joomla.civicrm.org/administrator/?option=com_civicrm&task=civicrm/admin/access&reset=1

and seems to work fine. Note that the buttons on a joomla page appear at the very top

lobo

[speedyrob]

Hi Donald

Please look at the pictures I attached. I am aware that the main buttons in Joomla 3.0 are at the very top, but I am asking about what I show in the pictures. In the window on top of the overlay does not have any buttons to Save or Reset settings.

Let me know what you think,
Thanks!
Paul R

[Donald Lobo]

as i mentioned in the other post, 4.3 has not been tested with joomla 3.0

would be great if you can take a deeper look at this and other issues and figure out what needs to be changed

thanx

lobo

[lcdweb]

submitted a pull request against: http://issues.civicrm.org/jira/browse/CRM-12096
for this issue.

[Fred]

HI

I didn't see this in any other post, so I hope I'm not repeating an issue.

If I go to CiviCRM > Administer > Access Control

And then I go to Joomla Access Control, there are no buttons to SAVE or RESET any changes that you make.

I'm not having any issues with seeing the menu or buttons with civiCRM 4.3.5 installed with Joomla 3.1.5, but as I posted elsewhere, I can't civiCRM global permission changes to save. Here's my earlier post:

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.

 

[DamonKirkpatrick]

Fred -

I'm having a similar problem.  Instead of an Internal Server Error, I'm rerouted to the site configuration page but I suspect the problem is the same as I seem to be routed to that page each time I should get an error.

I can access the ACL control and set the permissions, but when I click Save, I'm routed as above and no permissions are saved.  I tried the same thing in the sandbox and did not have the same result.  It worked fine there.  I'm on Joomla 2.5.9 and Civi 4.3.

[tso2085]

Anyone have an update on this issue?  It really makes using CiviCRM with Joomla 3.1.5 unusable. 

Further detail on the issue:

1) When I first go into the Joomla Access Control under CiviCRM (which takes you to the Joomla Global Configuration page for Component ACL), the Title for CiviCRM under the component list is "com_civicrm".   When you access the ACL options, it changes to "CiviCRM"  - cosmetic issue it seems.

2) Looking at the joomla 'assets" table, where all other components and their ACL setting are kept, CiviCRM does not have an entry (but perhaps it does not until the first "Save"?)

3) When you change a default ACL and click "Save", you are taken to the main Global Configuration page, and the ACL changes are not saved.

4) Whether you make a change or not, and click "Save" or "Cancel", it takes 30 seconds or so to go to the Global Configuration page.

The Joomla / CiviCRM sandbox works, but Joomla is at v2.5.6 with CiviCRM beta 1 v4.4

If there is anything I can test to help troubleshoot this, please let me know.

Thanks,
Craig

[Donald Lobo]

Check:

http://forum.civicrm.org/index.php/topic,29881.msg127979.html#msg127979

Would be great for the civi-joomla community to help get this resolved.

lobo

[dwfriederichs]

I'm having this same problem with Joomla 2.5.11 and Civi 4.3.5.  I've posted another thread but haven't seen any responses to it. 

I don't remember this being a problem with the current Civi release from last winter. 

If there's not a fix - does anyone have an idea for a workaround?