Configuration when Package Install

Permalink
Is it possible to have the user provide some configuration values during the package install process.

I looked at the config options in package but I am not sure how to display a form for the user to enter data. My initial thoughts are it would be similar to block edit but i am not sure how to hook the form to the install process.

argvader
 
Tony replied on at Permalink Reply
Tony
this isn't a bad idea, but i don't think theres an easy way to do it right now, at least i haven't seen it on other packages. what most people do instead is to just provide smart default, and then provide a configuration screen in the dashboard so users can set custom options after installing. not sure if this will work in your scenario.
argvader replied on at Permalink Reply
argvader
Thanks Tony.

You confirmed my current approach. I am creating a dashboard page for configuration.
ScottC replied on at Permalink Reply
ScottC
it's coming though
It is in the beta, config gets a third field, pkgID and you access it by getting an instance of your package, then calling saveConfig on that(maybe?) or by getting the package object, getting a config object, passing in setPackageObject($pkg) to the config object then a standard config save.
Fernandos replied on at Permalink Reply
Fernandos
Hi Tony :)

Helpers for such kind of tasks would be a really cool thing. Could you please integrate that into 5.4.1 before it's getting released?

I would like to have helpers for creating such a form during a package installation, so that we have a default and the C5 UX (UserExperiene) stays coherent.

I've two apps that would require an initial configuration because they install 10 or more packages at once. A smart default is possible but not the best choice. In example a Hotel Management App cannot be setup with smart defaults easily.
ScottC replied on at Permalink Reply
ScottC
absolutely. Right now I check config value and redirect them to the appropriate page until they set up defaults.

This isn't a huge deal to do, and in your case with the several package installs based on a package that is a great use case for it, but most package configs will need to have those edited after the fact so the singlepage method or action based form display(or combination of both) is just one of the ways to do this.

But I totally agree with the one time config, especially installing several packages and setting say the return email address of several email newsletter packages or a huge gallery app(like slideshowpro or something)