running. This means people can submit stories, and moderators can
moderate stories. When a submission reaches a certain positive
threshold (currently set to 2) the submission becomes a story and up
it goes. If a submission reaches a certain negative threshold
(currently set to -2) the submission is dumped.
The fact this is all done by our visitors (without our intervention)
makes it truly spiffy imho. The website can live a life on it's own,
fed by the visitors.
Beware, a lot of work need to be done though ... it's just a first
basic implementation with the core functionality. There are quite
a lot of things that I'll need to change, extend and improve. But
comments, suggestions and ideas are - as always - welcomed.
Please read this log message carefully! It features quite a lot of
important information.
To test the moderation, log in, select theme 'Dries' (the other themes
need a small update) and head by clicking the one and only 'submission
moderation' link. Don't be afraid to submit lame/funny/useless
stories for testing purpose ... as soon we go public, we'll wipe out
the story database. ;-)
WHAT'S NEW?
-----------
* Added 2 new operations to user.class.php to set and retrieve the
user's "history". Very evil but required to avoid people voting
twice.
* Moved dbsave() from account.php to functions.php. In addition, I
added a new function to user.class.php called `save()' that ...
well, saves the object back to the database. It's (IMHO) a better
approach compared to dbsave(): it keeps things organized. ;-)
BUGFIXES:
---------
* Fixed a (heavy) memory leak in the constructor of user.class.php:
mysql_fetch_array() returns an _associative_ array which made the
constructor `pollute' the object with a lot of useless variables.
* Fixed the slash-problem on the account pages. :-)
* Fixed UnConeD's theme glitch, alas the warning.
* Fixed the e-mail address not showing in the confirmation email
(upon registration).
* Fixed the typical quote and backslash problems in submit.php.
* submit.php now uses the database abstraction layer.
IMPORTANT:
----------
* You can check the new submission system at:
http://beta.drop.org/submission.php
or by following the `submission moderation' link from my theme.
* UnConeD, Jeroen: you'll need to update your themes to take
advantage of the new function: displayAccount(). This function
will display the `submission moderation' link when a user is
logged on.
* Natrak: you might want to apply the patches in user.class.php
on the other sites using the same user-system.
* Temporary bugfix to fix a problem with UnConeD's theme. Don't worry,
it's because some changes I made ... which should be fixed now.
Note:
* Btw, has someone bothered to scale the calendar.class.php to fit nicely
in IE (Windows)? Please do. ;-)
* Various small changes to account.php including a SQL table movement:
'testusers' -> 'users'. As a result, user.class.php and article.php
needed patching as well. Hopefully I didn't break anyting. ;o)
layer. My new files already take advantage of the abstraction layer
though no attempt is made to port the existing files: this is sheduled
for a future v0.40 release (see http://beta.drop.org/docs/roadmap.php).
Anyway, with the abstraction layer it should be theoretically possible
to run drop on top of every database, even on top of a home-brewed
file-based system. *wink-to-UnConeD* ;-)
system:
- you can add and remove wild-carded e-mails from the banlist.
- you can add and remove wild-carded hostnames from the banlist.
- you can add and remove wild-carded usernames from the banlist.
- you can add and remove wild-carded profanity from the banlist.
- you can browse all bans according to their category: see ban.php.
----------------
* Altered the theming system to follow the naming convention of class files.
theme.class has been renamed to theme.class.php!
* I fixed the default theme and my own theme, but none of the others themes
for your convenience... This means *you* have to rename your theme on CVS
by (a) removing it from CVS and (b) adding it back with a its new name:
'theme.class.php'.
For the clueless:
mv theme.class theme.class.php
cvs remove theme.class
cvs add theme.class.php
cvs commit theme.class.php
* Sorry for breaking things ... try to fix it asap and everything will be
OK. ;)
---------
* Fixed a few bugs in account.php - saves Natrak some time.
I only fixed the obvious, very small bugs reported today.
Enhancements:
-------------
* Made the default theme a setting in config.inc. You can now easily
change the default theme. It's a much nicer approach with more
flexibility. When working on your theme, you set your theme to be the
default theme. In addition, with a small scripting tric in config.inc
we could automatically set the default theme to the most popular theme
(according to the user table), or we could periodically cycle (round
robin) through all themes: say every week a new default theme. I truly
think that's better. :-)
* Adjusted config.inc, theme.inc and account.php in order to do so.
* I have some remarks with regards to config.inc, but I think I'll share
those later in a seperate mail.
rendering a calendar less expensive.
* Added a function displayCalendar($theme, $active_date) to functions.inc.
* Adjusted index.php so it would support URIs formated like
"?date=$unix_timestamp".
* Integrated the calendar in my personal theme: themes/Dries/theme.class.
If you want to include the calendar in your theme, check the code in my
$theme->footer(): global $date and call displayCalendar($theme, $date).
Check the main page at http://beta.drop.org/ with theme 'Dries' to see it
yourself!
browser, but now the Status box show in 9pt too and I dont want that, does
anyone know how to break out a stylesheet so you still can assign font sizes
within the body, without them being overruled by the stylesheet?
Dries Buytaert
Jeroen Bensch
natrak