CiviCRM Community Forums (archive)

Hi all,

We have civicrm running, servicing our soccer club (galactics.org). As we are now re-organizing we want to split that site into 5 different domains. But we want to have the ability to have civicrm for all membership, event signup and fundraising on that 5 sites.

We are running civicrm 2.0 under joomla! 1.0.15 right now. What is not satisfying is the access control, we have to give the staff members administrator access to the backend which is not a good idea.

We thought about setting up a separate site just for that purpose (separate domain) and have civicrm collect the sign up's etc for all other sites. That way we have all the information on a single database accessible by all staff members who need to.

The questions that came up :
- Would a stand alone version help us here? Considering also that we want the signup site look and feel the same as the other sites?
- Is there a way to track from which site the signup did come (for statistic purposes)?(I have read the part about the multi domain feature, but that would not fit our needs as that would also mean separate databases which is not what we want.)
- Per our information civicrm 2.1 would fix the access control under joomla (1.15 only?), is there an approx. release date for 2.1 (needed for planning purpose)?
- is there a 2.1 alpha/beta which could be used for testing (searched around but could not find anything)?


Thank you for any insights you share

Harry Star

I agree with Dave Greenberg.

For a Dutch fundraising (event) organisation I have CiviCRM running under Drupal5 in a Drupal Multisite setup. CiviCRM is placed as an extranet 'website', only accesable by members of the organisation (Backoffice function). ACL's of CiviCRM and Drupal are used. CiviCRM and his content(!) is completly hidden for robots end the public.
The internet website is also configured with a civicrm setup, civicrm.settings.php is pointing to the same db as the hidden extranet.  You can use all features of civicrm on the website. We only use the public registration pages: for example event registration and newsletter account (Frontoffice). Website users, making content for the website, don't have acces to civicrm.
This is working for 3/4 year now, with civi-event and civi-mail. Conclusion: Making more websites pointing to 1 civicrm db/setup is no problem in Drupal.