to eventually replace the invisible (but working!) ewiki_eventually_initialize() function, which fills up the database with the default stuff from ./init-pages, when no FrontPage yet was in the database.

The problem here is, while this works greatly and fully automated, it gives the user very little infos (nothing at all) about what's going on. So eventually some peoply won't even recognize, that the Wiki has been successfully installed (even if the current behaviour perfectly suits UNIX folks).

the upcoming InitializationPlugin should provide:

• setup advise
  • warnings for broken php versions (magic_quotes, register_globals, safe_mode)
  • tell about the used database backend, if a SQL database is used or files would get stored into "C:/tmp" because ewiki was not configured correctly
• tell verbosely(?) what's going on
  • print the list of pages, that were read in, like PhpWiki: does (???)
  • "congratulations to buying ewiki"

Another benefit from the extraction of the _init feature into a plugin would be to get that otherwise unnecessary code away (it would be run just once). And also the ./init-pages read-in is redundant because the tools/t_textinsert and the TextUpload plugin already allow to do this (and again: it's only done once). milky