What do you mean by "take"? Drupal already handles the forms for these details automatically, as it is required by any install profile to have these inputs from the user. Gabor Thanks for answer so quick! When I say "take", I want to say "agarrar" (spanish), :p I want this: The user don't need to fill in the database form, The db user, password and all that will be already known by the installer. Am I now clear? Thanks -- yo@fernandocosso.com.ar http://www.fernandocosso.com.ar

Fernando Cosso wrote:

Thanks for answer so quick! I want this: The user don't need to fill in the database form, The db user, password and all that will be already known by the installer. Am I now clear?

If the database details are already in the settings.php file, the installer will not ask for them. If you ship your own install profile, you can put there a customized settings.php. Gabor

Hi It's me again. I am stuck with profile installation. I've putted the default mysql information in sites/settings.php and it's working fine. The thing now is that I need to set the language of the site, create the admin account and ask the user some questions (meaning forms) in the installation, and I don't really know how to do that. The only thing I know is that I have to do all this in the function myprofile_profile_final() . I reminds you that I started with all this drupal thing yesterday. I am a xoops converted!! Can someone give me a hint? Thanks -- yo@fernandocosso.com.ar http://www.fernandocosso.com.ar

Short answer regarding the forms is that there has been much talk of "wizard" functionality, but I don't know if there is a clear plan on how to do that.

Oh. Wizard is designed and will be coded within, hm, seven days? We will employ a cache_form table to store forms and submitted data as opposed to the current situation where every multistep form function itself needs to store its submitted data in session/hidden whatever. The builder functions will get the $form_values still but they do not need to provide hidden fields to store the information in. What's more, they can't do that because form_builder will *not* get the posted information -- every step is an invidual form and the submit handler gets the array of $form_values keyed by the steps. This neatly solves all possible problems because there are no special cases, every form , #multistep or not, starts its lifecycle as a nonsubmitted form. Most problems currently --validation,checkboxes,whatnot-- arises from the fact that every step begins its life with the burden of the previous POST. For JS guys, the plans are that we will make it possible for JS code to basically do a form_alter, store results in the aforementioned cache_form table and send back the themed form element. I am a bit unsure of who/how will produce the JS but the PHP scaffolding will be in place, soon. Regards, NK

On 20/04/07, Boris Mann <boris@bryght.com> wrote:

Hi Fernando:

The dev list here isn't really the right place to be asking all of these questions. Install profiles are quite new, there is http://groups.drupal.org/distributions where a lot of this is being discussed -- please come join us there.

Okey, sorry for the off topic I have *some* of the functions you mention in my install_profile_api

module / crud.inc, which is referenced in that group.

Short answer regarding the forms is that there has been much talk of "wizard" functionality, but I don't know if there is a clear plan on how to do that.

You can look at some of the language-specific install profiles to see about setting language.

Cheers,

Thanks you so much, but it is a little late, I am moving to XOOPS again, Drupal is really cool, but the admin section is a bit confusing. I also have found some things that I didn't like. I know is far from being a good thing, but I am running out of options. -- yo@fernandocosso.com.ar http://www.fernandocosso.com.ar