| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
structure changes, some sections are expanded. Take a look at the source
code or ask me to elaborate on certain issues/topics.
|
|
|
|
|
|
|
|
|
|
| |
- Added a basic implementation of comment moderation
- Updated and renamed my 2 themes: I removed redundant boxes and tried to
work towards simplicity.
- Disabled the other themes as they are broken (I gave you sufficent time
to update them).
- Removed redundant files.
- Added security checks with regard to the usage of HTML tags.
|
|
|
|
|
|
|
|
|
|
|
| |
stream-lined and more compact. There are a few parts I like to optimize
prior to heading towards comment moderation.
Please test, report bugs and update the footer()-part of your themes a
bit (see my theme)!!!
-- Dries
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
working on it for about 4 a 5 hours today and I considered it would be
smart (backup- or crash-wise) to commit what I have made so far. I'm
aware of a few bugs and I'll keep workin on it:
- removing bugs
- clean up the code to make it very streamlined
- improve error checking
Once we got a stable comment system, I'll add moderation. But right
now I want to sort out the major problems.
* I made my theme the default theme until the other themes are updated.
* Expanded the database abstraction layer with more goodies.
|
|
|
|
|
| |
reason for doing so is because the database abstraction layer provides
build-in error checking and a debug mode for easy development.
|
|
|
|
|
| |
* Streamlined the database abstraction layer a bit (it's not much yet) and
integrated it in most of the functions of `functions.inc'.
|
|
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* ;-)
|