Currently OpenCivic requires site developers to go through an installation process that entails clicking check boxes and hitting a submit button repeatedly to install components after the installation profile itself has completed. This is different from the standard Drupal installation process and makes installation more time-consuming than it needs to be.

This installation procedure was created as a temporary workaround to deal with timeout issues that were preventing OpenCivic from installing completely during the standard installation profile process. As a prerequisite for arriving at a beta 1 version of OpenCivic, this temporary workaround should be replaced with a more standard, easier installation process similar to the process for installing distributions such as OpenOutreach or Panopoly.

Comments

pmackay’s picture

Version: 7.x-1.x-dev » 7.x-2.x-dev
Issue summary: View changes
socialtechno’s picture

I apologise for not documenting this when I tested it last summer, but I noted four different issues:

1 An option that had to be run first.
2. Options that you could add and remove in a loop.
3. An option to check to say "I'm done now, stop looping".
4. Some options had sample data available.

I'd recommend a single flow that works thusly:

1. Just run this option, unconditionally. Test whether the code needs to be run, but don't ask the user's opinion, cos they don't make the choice, the program does.
2. Do what Panopoly, Outreach, Julio et al do. A single list where users can check as many as they like.
3. If we apply 2, this is not necessary and becomes like 1.
4. We should only allow users to choose sample data if they choose the function that uses the data.

Number 4 can be handled by UI logic ('greying' out the option to select sample data, unless the function is chosen) or execution logic (ignore the user's answer on sample data, unless blah blah blah)

I agree that Panopoly and Open Outreach are good models of best practice. Also look at Commerce Kickstart, which has sample data, but does not use the 'Apps' architecture.

Commerce Kickstart also has an option to erase the sample data after you've had a play with it. But, to my horror, it drops the entire database and reruns install.php. Not recommended.

Carlos Miranda Levy’s picture

Currently, I got timeout errors if I checked all options, so I install it like one or two features at a time.

Sheldon Rampton’s picture

Assigned: Unassigned » Sheldon Rampton

This boils down to eliminating the "ocsetup" functionality that runs post-installation and getting it to run during installation instead.