skinsets on the preferences page. I don't know if this is a good idea, but with the
current code in site/edit_action it's required, otherwise the site's skinset will be
when saving preferences.
* removed option to get notifications only for new comments
* added check if receipient is identical with the creator/modifier of the modified object
* made use of sendMail function
* Skins are attached to skinset rather than site objects
* Each site can have multiple skinsets
* Skinsets can inherit from each other
* Added subclasses of imagemgr and skinmgr that mount on root/manage
* added flushMailQueue to send mail objects contained in the mail queue (ie. app.data.mailqueue)
* added call for flushMailQueue from the scheduler function
* changed mail.send() to mail.queue() in sendNotification functions
* since site preferences are stored as xml the corresponding code had to be adjusted
* currently, no notification is sent if a story's status changes from offline to online (abuse factor is too high)
* there's only one global notification skin used for the mail body
* the sender is always set to sys_email to avoid the bounce problem we already had with registration mails
- site preferences are now xml-encoded in one property called preferences_xml which is handled by propertymgr
- removed function createImgDirectory() since directories are created on the fly by helma
- changed all preferences related macros since the site preferences are xml-encoded now
- discussions_macro() and addtofront_macro() now don't need an input type hidden anymore to preserve the submitted state
- removed permission checks, this is done in checkAccess() now
- removed checks for req.data.submit, use named submit buttons in skins now
- added try/catch blocks since most objectFunctions will throw an Exception now instead of returning an Error object
Spacing should be better now.
Skins should be easier to understand and customize.
Used <div> tags wherever possibe instead of <span><br>
Checked for XHTML 1.0 Transitional validity.
