Skip to end of metadata
Go to start of metadata

List of Joomla things we'd like to address preferably with CiviCRM 2.1 in Joomla v1.5 or v1.6

1. How do we make the installer process succeed more often. A couple of issues:

  • Our civicrm.xml file is HUGE (240K, 3367 lines, 3315 files!). Only works with "install from directory" option. I think all files are copies twice: from director ==> com_installer ==> administrator/components/com_civicrm (most of the files go there). Large number of people dont get past this step. One potential idea that I have is to use the "install from directory" location as the civicrm root location and only transfer the "joomla" specific files to administrator/components/com_civicrm and components/com_civicrm. This will make minor upgrades much easier (since its then an untar)
  • Upgrade is painful (sad) . Its an uninstall followed by an install. This is even true for minor in-version upgrades. Due to permissions etc, i dont think folks can just untar / copy stuff over since the web server owns the files
  • Better integration with registration OR is our only option building a new registration component? Thats not great since a component like CB also uses that and then the user needs to pick and choose (IMO)
  • Would be good to have "api" calls for things like the above. Right now when we create a user, we basically just write into the joomla db (which we picked from the joomla reg code)
  • Enable ACL capabilities for Joomla installs (may need to wait until ACL in Joomla 1.6)
  • Ability to control frontend access based on user membership status (may not be unique to Joomla)
Labels
  • None
  1. Mar 14, 2008

    On upgrading --

    I have done the untar/overwrite process on upgrades a couple times, with pretty good success. If it's possible to easily generate a package that follows the Joomla directory structure, it would be great to have that available as an option. Also, I believe that the Joomla 1.5 component install xml structure has an option: method="upgrade" which allows you to install on top of the existing component (overwriting files, thus upgrading). I recently used an extension employing this option, and was surprised that I was able to install on top of the existing installation. I couldn't find any topics on the Joomla forums that dealt with it, but it would be worth looking into.


Creative Commons License
Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-Share Alike 3.0 United States Licence.