CiviCRM Community Forums (archive)

Firstly many thanks to Henry and Donald for their great help, you are doing an excellent job here and I'm only just begining to learn and appreciate how much.

...the work that the team are doing to bring Joomla integration closer is a good thing. Having the capability to enable or disable the functionality is a route forward but I’d like to be giving the devs a clear message that the Joomla community needs this functionality.

Yes I agree - closer links between Joomla and CiviCRM are a good goal, but should not introduce inflexibility. Enable/disable options on linking cms-civi ids automatically would be very desirable

Secondly, you’re matching on firstname + lastname.  How many John Smiths do you know out there? I’m assuming that since you have a manual process of issuing logins that you bypass this issue from a CMS point of view. But how do you sync the UFMatch to pick up the right John Smith if you want to show him some profile? Assuming, as a citizen, I value being a member or associate of your organisation then sharing a single valid email with the org would be acceptable. Especially if you adhere to the Data Protection Act and also publically state that you won’t share / sell details.

This is indeed a problem for me. What I really want is an enhancement to the sync process that allows me to manually accept/reject proposed matches and create/ignore unmatched cms users as contacts. Also a separate tool which allows me to click a button when viewing a contact and be presented with a list of unmatched CMS users and select one to be linked in UFMatch.

In the past I’ve used Community Builder to handle moderated registrations which has worked quite well. I suspect that a level of automation could be built in to redirect applicants depending on their region without too much difficulty.

Yes CB is quite good and I have used it in other places, but didn't match my needs for this one

Ultimately what we really need is for Joomla to deliver a decent ACL.

Actually I disagree. I think that access control to CiviCRM functions needs to be controlled within CiviCRM and independent of the CMS access control. Yes optional links between them might be good, but essentially we have that once a user is matched with a civicrm id. If a CMS user has no entry into UFMatch then it can be assumed that he has no access to any non-public CiviCRM facility.

Joomla's ACL is basic and can be extended as many other extensions have (CB, JACL, JUGA etc). It is almost a philosophical difference - in the Joomla world extensions are written to extend Joomla and add functionality, whereas in the CiviCRM world the CMS seems to be seen as an component of the core application. Just a different way of seeing things.

RogerCO