Posted by mitchell on January 4, 2009 at 7:17am
Yes
88% (50 votes)
No
5% (3 votes)
Other solution (specify in comments)
7% (4 votes)
Total votes: 57
Would you use the Profile Wizard module if it's ported to 6.x?
Comments
I'm just starting
I'm just starting with installation profiles, and found this thread about this profile wizard module: http://groups.drupal.org/node/5002
In this thread there is also a link to http://drupal.org/project/profile_generator
Dont have experience with this modules, but tatien (author of profile wizard module) says profile generator is more advanced.
Mitchell, are you thinking of migrating this module?
Profile wizard needs revamping
More than just porting, profile wizard needs an overhaul. And, I'm kicking it out of install_profile_api -- it's not the right place for it. Now that install profile API is a module, the wizard can depend on it, but it should be its own module.
Collaborating with the profile generator module so that a D6 version works with install_profile_api would be one route to go.
I'm happy to help support efforts in this area.
I would definitely use it.
I would definitely use it. Creating the actual DrupalMU distribution is now taking a lot of time. Knowing that Drupal 7 won't be released any time soon convinced me to actually go through with it but having the Profile Wizard would be a great addition. So I'm definitely up for beta testing.
Yes, I am going to repeat
Yes, I am going to repeat myself ;-P :
Take a look at the port module proposal on http://groups.drupal.org/node/14395 - I think it is the way to go. It creates a common base for generating code from configuration that can be used not just for generating install profiles from existing sites (= wizard), but also for configuration version control and deployment etc.
Port module is so far only available in 5 but it would be easy to upgrade.
http://www.twitter.com/lx_barth
http://www.twitter.com/lxbarth
As I said before...
Figure out where config lives. Right now you're pitching port as competition to install profile API. Install profile API is now a module, so I'm suggesting it become the lowest level of wrappers around db_query etc. Port and Profile Wizards can depend on install profile API module.
It's been great to see dww and moshe and others jump in and add bits and pieces to install profile API. I see other install profile creators kicking the tires on it, too. Next is adding more bits of code and/or getting some of the core D7 stuff to have CRUD functions so we don't need to wrap them.
So ... install profile APIs mission is:
* to wrap core and contrib db_query that don't have clean CRUD
* provide helpful tools to make writing code for install profiles easier (but stopping short of wizards...)
As such, I can see port absolutely doing import / export stuff. Depending on port for some install profiles is going to be a great thing. And really, it sounds like port could BE the new profile wizard.
Right now you're pitching
I think that's a misunderstanding... I am not seeing port competing with install profile API:
The part that port contains but install profile api does not contain is the export/import symmetry, an ad-hoc registry of functions pairs that export/import the same data. The part that install profile api contains and port does not (should not) contain are installation helper functions - short hands for programmers.
There is overlap of course and I think this overlap would have to be eliminated.
Yup, I'm under the same impression.
http://www.twitter.com/lx_barth
http://www.twitter.com/lxbarth
Right
Right -- so, it's all about defining the overlap. If you could have a look at the current 6.x release of install profile API and give some thought to what would make more sense in port, let me know.