Posted by PedroC-1 on March 26, 2008 at 3:21am
How to disable "Configure site" in an installation profile for D6?
The installation should run without stops.
Thanks in advance.
How to disable "Configure site" in an installation profile for D6?
How to disable "Configure site" in an installation profile for D6?
The installation should run without stops.
Thanks in advance.
Comments
I'm also interested in
I'm also interested in seeing if anyone has come up with a solution for this.
What are the data fields
What are the data fields that are filled in during that step?
The super user has to be set up with user name and password, part of it is the database variable -> site_name.
Set up all the variables assigned to the database at that point then have a look at this from install.php
<?php/**
* Verify if Drupal is installed.
*/
function install_verify_drupal() {
// Read the variable manually using the @ so we don't trigger an error if it fails.
$result = @db_query("SELECT value FROM {variable} WHERE name = '%s'", 'install_task');
if ($result) {
return unserialize(db_result($result));
}
}
?>
you could easily tweak that to declare the whole thing finished. but first I suggest that you see if you need to. The Drupal installer usually only prompts for information when it can't find it.
There isn't really a good way to do this
There isn't really a good way to do this without hacking install.php.
The installer needs quite a bit of love in this and a few other key areas.
You say hacking I say
You say hacking I say tweaking.
I was thinking about filling in the fields required, then changing variable {install_task s:4:"done";}
I'm sure it'd work but much like yourself I doubt it is a quality way to do it.
I've been ploughing though
I've been ploughing though install.php a lot today.
It struck me that my above assumption is (amazingly) correct. One the assorted variables are set, install.php sets the
install_taskvariable to the next value.Importantly,
install_tasks()uses a series ofifstatements to sort out what to do next. Because of this, if the preceding statement has checked everything successfully it sets theinstall_taskvariable to the next value, and the installer just trucks along to the next thing without pause. Not really beautiful code, but well thought out.A possible improvement would be to remove the variable
install_taskand set the stop points based on the variables that had been set. A solution that could be good or awful.