| 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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
made quite a lot of additions. The most remarkable addition is the
diary server, which I slapped together in less then 40 minutes. Most
of the other changes are however `unvisible' for the user but add much
value to a better maintainability from a developer's objective. Like
always, I fixed quite a number of small bugs that creeped into the code
so we should have a bigger, better and more stable drop.org.
Unfortunatly, some theme update _are_ required:
REQUIRED THEME UPDATES:
=======================
* use format_username() where usernames are used
* use format_date() where timestamps/dates are used
* use format_email() where e-mail addresses are displayed
* use format_url() where url are displayed
* replace 'formatTimestamp' with format_date
* replace 'morelink_*' with 'display_morelink'
[most of these functions are in function.inc or template.inc]
___PLEASE___ (<- this should get your attention ;) update your themes
as soon as possible - it only takes 30 min. to get in sync with the
other themes. Don't start whining about the fact you don't know what
to change ... either eat the source cookie, or ask me to elaborate on
a few changes. Just let me know what's puzzling you and I'll try to
help you out!
TODO LIST FOR NEXT WEEK
=======================
* Add checks for max. text length in textarea's? Is there an HMTL
attribute for this or ...?
* Comment moderation + mojo
* Edit/admin user accounts: block, delete, change permissions, ...
* E-mail password, change password, change e-mail address -> extra
checks and routines to validate such `special' changes.
* Input checking - input filter: bad words, html tags, ...
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
----------------
* 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. ;)
|
| |
|
|
| |
running windows on a good ol' slow modem.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
---------
* 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.
|
| |
|
|
| |
;)
|
| |
|
|
|
|
|
|
|
|
|
|
| |
been fixed yet though, but at least it won't try to load non-existing
themes. That is, you might not be able to select your prefered theme,
but you should be able to surf the pages with the default theme no
matter what. Hence, it semi-fixes the theme problem reported earlier
by UnConeD.
Natrak: make sure the new user system won't suffer the same problem.
Use file_exists(string filename) to check whether the theme
does actually exist. If not, load the default theme.
|
| |
|
