I'm a non-native english writer, please excuse any errors and funny words.
If I'm allowed to dream, I would wish a drupal site setting system that can be configured in a browser. And I do dream that the site settings are stored already in a database. Huh.
It might be logical from the trail of development, that the drupal configuration is splitted between a text file and a browser based part. But in the humble opinion of a dump user it would be great to have only one front end.
A install and upgrade script would be good, that simply does what you say we must have to do for an upgrade. Perhaps a little bit different folder system would help? Why is "sites/default", modules (added) and themes (added) within the update folder? Could there be a more genius setup? Where I can link only one "shared" folder an have at once a running and updated system (perhaps with broken modules and themes of course)?
Is it really impossible to have an (admin) accessible page where the current drupal version number (including those internal version numbers that are asked when doing the update.php) is displayed? Perhaps some other system information too?
Sorry for jamming your trot, go on with it ;-)
Comments
There is work happing
Hi Ralf
There is work happening in that area. How soon it comes, and how good it will be, I don't know. With a powerful and flexible system, it is hard to automate everything.
Wordpress is easy, but I can't use it for much except my daughter's blog. :-)