Author Topic: differences between using as module for drupal/joomla and standalone (Read 1110 times)

abusabtu · April 17, 2010, 12:54:55 am

i gather i if i'm not using it as standalone, i'd have be very careful when upgrading drupal/joomla. Care to comment or is there any comparison table that i can refer to?

my intention to use civicrm is to manage membership for local Debian users, managing events, sending announcement of future events, managing donation/contribution by members and third-party.

Eileen · April 17, 2010, 01:48:54 am

Standalone is not going to be supported so it is not a good option

I think it's pretty hard to give an objective answer on the Drupal vs Joomla question. Most people are in one camp or the other. I was a joomla user but when I first started with Civi I installed Drupal as a 'shell' for it. Now I'm pretty sold on the other functionality I can get from Drupal but what you are describing sounds like stuff Civi can do without needed extra drupal power.

Generally - joomla = easier learning curve, drupal = more powerful.

Hershel · April 19, 2010, 07:31:35 am

Definitely don't use standalone--it is not supported and will most probably not be updated ever.

I would agree with Eileen's other comments as well.

CiviCRM Community Forums (archive)

News:

Author Topic: differences between using as module for drupal/joomla and standalone (Read 1110 times)

abusabtu

differences between using as module for drupal/joomla and standalone

Eileen

Re: differences between using as module for drupal/joomla and standalone

Hershel

Re: differences between using as module for drupal/joomla and standalone