- Modified conf_init() to use default.conf if nothing else can be found.
- Added some comments to hostname.conf to reflect the changes and
  provide more information on how to rename the file.

TODO
- The Drupal handbook should be updated once the CVS version is released.
- Should try to remove the remainder of info from hostname.conf and go for a
  completely web-based administration if possible.
- Does having all the settings in a SQL database make Drupal add more
  overhead than including a .conf file? If nobody knows for sure some tests
  should be done. If yes, concider having the admin interface generate an
  include file in addition to saving to the database.

- Modified conf_init() to use default.conf if nothing else can be found.
- Added some comments to hostname.conf to reflect the changes and
  provide more information on how to rename the file.

TODO
- The Drupal handbook should be updated once the CVS version is released.
- Should try to remove the remainder of info from hostname.conf and go for a
  completely web-based administration if possible.
- Does having all the settings in a SQL database make Drupal add more
  overhead than including a .conf file? If nobody knows for sure some tests
  should be done. If yes, concider having the admin interface generate an
  include file in addition to saving to the database.

- Fixed an error in module_rehash_blocks() that didn't handle '-symbols.
- Removed some module depencies. Drupal will now run (sorta) even if there
  are no modules installed.
- Changed theme_link() to check if certain modules are installed before
  offering a link to them.

Todo
- Check all SQL queries to make sure they are addslashes'ed correctly.
- Check the effects of changing the PHP magic_quotes setting.
- Make the theme_link() function to be customizable either via the admin
  page and/or in the module itself.

- Fixed an error in module_rehash_blocks() that didn't handle '-symbols.
- Removed some module depencies. Drupal will now run (sorta) even if there
  are no modules installed.
- Changed theme_link() to check if certain modules are installed before
  offering a link to them.

Todo
- Check all SQL queries to make sure they are addslashes'ed correctly.
- Check the effects of changing the PHP magic_quotes setting.
- Make the theme_link() function to be customizable either via the admin
  page and/or in the module itself.

  to the newest. It would try to change tables that had not yet been created
  causing major problems to the node module. (NOTE: if you are doing a x.xx
  update to another x.xx version you might have to force MySQL to perform it
  using the -f flag. Remember to always backup your data before making
  changes).
- Prevented 2.00-to-x.xx.php from executing. It would simply give a PHP error
  and not execute. Will wait for Dries to return before attempting to make it
  functional or remove it.

- Fixed bug when node-navigation-combobox wouldn't select the correct item if drupal was run from a sub-directory.

- Added "custom" date/time format... to allow user-timezone-adjusted custom date formats. I didn't add special logic to translate parts of it, but it's not really needed, as this is only meant for internal usage (e.g. checking if timestamp A is on the same date as timestamp B).
  Some modules (such as diary) should be changed to take advantage of this function, as they are now still using GMT+0 dates in some cases (e.g. the recent diary entries box).

*** UnConeD wrote:
> - Fixed security issue: unchecked form-data in a db-query (line 82)
> - Fixed bug: the module now checks only against other *stories*
>   (instead of nodes) with the same title.

- Took out the duplicate title check; after the story module has
  been "nodified", duplicate titles are no longer a problem.

- Fixed two more </TD</TR>'s.

- Fixed bug: the module now checks only against other *stories* (instead of nodes) with the same title.

- Fixed date problem in calendar module (reported by Remco).

- Addition: added a "promote" field to the node table, which
  makes "promoting nodes" to the main page possible.  Stories
  and reviews could be promoted by default, but - on accasion
  a good book entry could be manually promoted too.  Thus all
  existing content types can be shown on the main page, not
  just stories.

  Requires a SQL update, see 2.00-to-x.xx.sql!

- Addition: implemented "auto-post new submissions" feature
  to disable or by-pass the moderation queue in addition to
  "moderate new submissions".

  TODO: admin moderation versus registered user moderation.

- Addition: added category and topic support to page.module.

- Addition: made it so that comments can be enabled/disabled on
  a node per node basis, rather then on a category per category
  basis.  The default settings for each individual category can
  be changed though.

  Example: it can be setup so that - by default - all stories
  posted to the category "article" will have comments enabled
  but stories submitted to "announcement" not.

  Different configuration schemes can easily be added later.

  Requires a SQL update, see 2.00-to-x.xx.sql/database.mysql.

- Addition: made submit.php only use categories that users can
  actually submit new content to.

- Addition: added 2 new functions check_mail() and check_name()
  to functions.inc useful for resp. verifying an e-mail address
  and username: currently used by account.php - but reusable by
  Julian's refer.module for example (prepares integration).

- Addition: added a new function "module_hook($module, $hook)" to check
  wether a module implements a certain hook or not.

- Addition: added new "cvs.module" to display and mail drupal's
  CVS log messages.  Our additional Perl script that hooks into
  the CVS repository is also provided in ./scripts.  Requires a
  SQL update, see 2.00-to-x.xx.sql.

- Updated CHANGELOG and fixed a few typos.

- Updated CHANGELOG and fixed a few typos.

- Updated CHANGELOG

- structure.inc: added category_name($cid) and topic_name($tid).
  They both return a linked string with the respective category,
  or topic name.  Updated all themes to use these new functions.

- (stripped tabs from emsa files, nevermind)

  They both return a linked string with the respective category,
  or topic name.  Updated all themes to use these new functions.

- (stripped tabs from emsa files, nevermind)

- fixed bug in page.module: $theme->header() got called twice.

I also applied UnConeD's remark about the PHP_SELF. And remover jeroen2.theme, added yaroon.theme and commit it now. Dries, if you have 5 minutes, just move the jeroen2 directory to yaroon.

Jeroen.

- fixed sub-directory problem reported by UnConeD

I updated my theme, and changed something about the update Dries did. I think you left a <a href> there... But now it's OK. Also when I first looked at my theme it looked real ugly in NS .76, but then after some fiddling around, but restoring everything I changed it looked OK again. Weird. I haven't changed a thing. We'll see, if anything else happens make sure to let me know.

- updated the forgotten theme: theme Jeroen doesn't render 100% correct in Netscape btw - it is certainly not due to my changes.  I have this feeling that there is an unclosed tag somewhere.

- all these themes are getting a pain to maintain but I guess nothing we can do about it.  Hopefully the theme API is about to stabalize soon.  In future, we should certainly keep the number of "supported" below 10 so as so we have, say, 11 themes I suggest to kick out the one that is less interesting.  It will then become an "unsupported theme" available through drop.org/drupal but maybe not in prime condition.  It think we'll have our hands full with 10 themes already.  It is really the max IMHO.  Comments/suggestions/noding heads?

- improved interface a bit

Another big update so please read this carefully because there is important information hidden in it.

Made it so that we can disable/enable comments on a category by category basis. In order to accomplish this I had to make a few (*temporary*) changes.

I moved all comment code from the "module level" (eg. story.module) to the "node level".  It was nothing but the logical next step in nodifying drupal.  This enables us to add comments to all existing content types including book entries.  But also for book entries, this to can be toggled on and off. :-)

Moreover module writers don't have to worry about the complex comment logic: it is "abstracted" away.  This implies that story.module got smaller, faster and easier to comprehend. :-)

In order to accomplish this, I had to update ALL THEMES, which I did - and on my way I updated Goofy, Oranzh and UnConeD - with the previous changes.  All themes are up-to-date now!  I also had to remove the [ reply to this story ] links, and temporally re-introcuded the "Add comment" button in the "Comment control".  Tempora lly that is, UnConeD. ;)

I plan to upgrade drop.org either tommorow or wednesday so test away if you have some time to kill. ;)

Oh, I also fixed a few bugs and made various small improvements.

This should be it. For now... I applied most of the remarks you told me to. Only the seemingly floating squares... well let's just say they add to the mysteriousness of the page. I can't delete them. I don't think my site would look without them. We'll just see what the users think of it shall we? I can ask them abou the squares once it's released. So, all there is now is the fat vertical bar in NS 4.76. I also don't know what it looks like in Opera... and UnConeD, does it show a bit OK in IE? I polished the navigation box' algorithm a bit. Even more stable now.

I do have one remark Dries. When submitting something you don't have to choose story or book anymore but you have to select one of the categories. Is this OK? But wouldn't it be more logical to choose what type of thing you are going to submit. I don't think you will be placing an Announcement in the book. By the way how do you add a page to the book now? I can't find it... Or do I have to create book and story myself... Ahh heck Dries it's just broken OK? ;)

For the rest. Oh yes, I am not going to work with the categories. The squares in front of a $story->title represent the topic the title is under (e.g.: linux, science, Media, Announcements) But not the category (I see them as a some sort of sub-folder in each topic) I haven't found a good way to display it yet. I still have to find how to import it in the lay-out so it wouldn't mess up. I already liked the fact that I don't have text-links for the former categories anymore... We'll see what happens...

Jeroen.

- updated database.mysql file

- a few changes which might help overcome Jeroen's redeclartion problem
  (or might not)

- removed departement code

- forgot to disable some debug information

Large commit, read it carefully, and make the required changes to
your theme:

- corrected some missing translations in story.module.  Oops!
- grealty simplified the "moderation threshold mechanism"(tm) so
  that module writers don't have to worry about this.  As a result
  story.module and book.module became a bit smaller and easier to
  grasp.
- greatly simplified new "category" and "topic" code which is soon
  going to replace the "section" code.  Needs more work though so
  hang on thight.
- includes/section.inc and modules/section.module are replaced by
  includes/structure.module and modules/structure.module.
- beautified example.theme a bit without adding HTML complexity:
  it is a good example but still useful as a theme
- made theme example use "categories" and "topics"
    --> TAKE A LOOK AT IT AND UPDATE YOUR THEME
- made theme marvin use "categories" and "topics"
    --> TAKE A LOOK AT IT AND UPDATE YOUR THEME
- added 2 new "story listings" to administrator interface of
  story.module to verify story integrity.
- optimized comment table a bit (work in progress)