No install instructions for SQLite

Moving to documentation component.

here's a very basic starting point.

Don't forget to mention that you need the SQLite extension enabled in php.ini:

extension=php_pdo_sqlite.dll
or
extension=php_pdo_sqlite.so

If not enabled, the SQLite option does not appear in the Database configuration page.

Subscribing.

The problem with installing on sqlite was that I was very confused about the "database name" field. It had a maxlength parameter that wouldn't allow me to put something like "sites/sqlite.drupalhead.local/files/.ht.drupalhead.sqlite" as the database name, which should be ok.

I am attaching a patch that alters the description text for the Database Name field, and the Database User field in install.php to instruct SQLite users on how to correctly configure the Database Name field.

I think I'd prefer if the install.sqlite.txt was added first, and then we work on #346494: DB drivers need to be able to change the configure database form during install to allow DatabaseInstaller_sqlite to form_alter the database settings and remove the username/password fields and modify the descriptions. It seems a more Drupal-way to do things. Plus we'll future-proof future db backends.

IMO this is unnecesasrily bloating the descriptions for 100% of our users, even though only maybe 5% might use SQLite.

I'd prefer to see this extra help moved to INSTALL.sqlite.txt, personally.

CrashTest, would you be willing to spiffy up drewish's patch so that it would've helped you be less confused here, and maybe add a general note to the installer that more specific instructions can be found in INSTALL.databasename.txt?

Ok, not much needed on the INSTALL.sqlite.txt file. I did add one small line to the install.php file to alert people to the fact that there are INSTALL.database.txt files that they may refer to.

BTW, I think it would be much more appropriate to actually link to the INSTALL.dbtype.txt like I have worked on in #346494: DB drivers need to be able to change the configure database form during install, so maybe we should keep that separate.

Actually, after reviewing a concern about the download-ability of the database file, we decided to reword the text file to include some precautions about that.

Noticed the line breaks are not consistent in that patch, fixed here.

Tagging usability.

I think I saw one instance of double spaces between sentences in the INSTALL.sqlite.txt file.

(Also, the INSTALL file doesn't mention what PHP packages must be present before SQLite will work properly. This was an issue for me when I went to install an installation on SQLite the first time, and required both some hunting around and, eventually, asking chx what to do in #drupal.)

I'm not positive people will understand

+      '#description' => st('The type of database your @drupal data will be stored in. Database specific installation instructions may be found in INSTALL.databasetype.txt.', array('@drupal' => drupal_install_profile_name())),

INSTALL.databasetype.txt without an example -- I guess you could use the mysql installation instructions as an example, in italics, here. Also, its worth mentioning in this sentence that the INSTALL* files can be found in the Drupal root directory.

one more tag for the copy writers :)

This might be overkill, but what are thoughts on hiding extraneous information in a slide-down div which is triggered by a link that reads "Need help chosing?"

Fixed the double space, and added requirements for SQLite to the text file. Also clarified the INSTALL.databasetype.txt note.

Great!

One small thing:

+To be able to use SQLite with your Drupal installation, the following require-
+ments must be met: server has PHP 5.2 or later with PDO, and the PDO SQLite
+driver must be enabled.

"To be able to use" can just simply be "To use"

Removed the "be able".

Renamed patch, re-applied.

I committed the help text to CVS, but not the install.php change. There is a better patch for that in the issue queue (see above). Thanks!

Awesome!