Querysets used to populate form fields are more filtered (ie. the default admin is ignored, as the current logged in user).
see #92
More protection against errors that can happen when defining new permissions.
I think the refactoring is over :-) I need to add specifec events that will allow plugins to define their own roles inside the hierarchy.
Otherwise, the graphical part needs some improvment, actually it's not really pretty :p
Work in progress. I've moved permissions management to the new dedicated page. Adding permissions is working but deleting ones. I must also filter the list of users available when creating a super admin because the default admin appears inside :p
wip: #36, using tinyMCE (django-tinymce) to write messages in HTML. Currently, compose a new message is working pretty well. Answering or forwarding a message is still a mess...
perms object is no longer passed to builtins or filters, we use user instead
(it seems that perms content is different with Django 1.2)
#48 : I think I've found a way to include templatetags dynamically, using add_to_builtins.
This is not finished yet. More work than what I expected but the main part is done.
It will need a lot of testing... There is still a bug when activating a new extension
in development mode (ie. with python web server), I think it does not occur behind
a real web server.
Many updates in this commit:
* first work on the webmail plugin, for now only emails listing and folders browsing is supported...
* New login form,
* New graphical layout (still needing improvments)
* code factoring between webmail and quarantine plugins
* etc.
Postfix Autoreply plugin is not a real plugin... I've begun the conversion but it will cause a modification into the SQL schema and I don't know how to handle migrations yet...
this feature).
Back to previous 'locale' location because it's not possible to access
translations that are defined inside the 'templates' directory while scanning
with django-admin.py from the 'admin' directory.
tonio