Hi - Drupal 7 has been out for a little while -- a lot of folks will be wanting to install Drupal 7 out of the install scripts. This is NOT a big high-priority issue for me since it's plenty easy enough to install it manually, but I know I'll be having clients wanting to do this within the next few months, so I thought I'd bring it up.
While we're at it --- my PERSONAL preference for the Drupal install script would be to:
Not use a database prefix for the database tables -- this is sometimes messy since you occasionally see someone who writes a Drupal module that doesn't quite work right with prefixed tables - yeah, it's the developer's fault, but I don't see any really good reason to use the drupal_ prefix since you're almost certainly going to be using a new database for the Drupal install - just a preference on my part as someone who does a LOT of Drupal.
I'd also prefer that you not set the base_url variable in the settings.php file --- this is hardly ever necessary or useful and it more often causes problems down the line for people. Best practice for this is to leave it unset unless there's a good reason to actually set it, and it can cause some really bewildering behavior in some cases when it is set.
Other than those 2 things I want to congratulate you on having a Drupal installer that actually works and usually even lets people do upgrades with very little grief -- if only Fantastico did half as well.
Comments
Submitted by cruiskeen on Tue, 02/08/2011 - 16:46 Comment #1
Oh - and don't take this as a suggestion that Drupal 6 should go away - it'd be nice to have the choice of 6 or 7 since it's pretty hard to actually build production sites in 7 yet.
Submitted by JamieCameron on Tue, 02/08/2011 - 17:23 Comment #2
Thanks for the heads-up ... I will release an updated installer with Drupal 7.0 support shortly.
As for your other suggestions, it seems that setting base_url is not needed, so I will remove that.
The DB prefix is needed though, as it allows Virtualmin to work out which tables belong to Drupal if installed into a shared database.
Submitted by cruiskeen on Tue, 02/08/2011 - 17:39 Comment #3
well, sure, I understand the issue about using a shared database -- I was assuming that people would not be likely to do that, but I also understand that a lot of hosts like to limit the number of databases available pretty stringently, so --- sure, I understand.
Submitted by Issues on Tue, 02/22/2011 - 18:20 Comment #4
Automatically closed -- issue fixed for 2 weeks with no activity.