Removed useless fields (full_address) and added associated migrations. SQL queries used by postfix or dovecot will need to be updated. (as the documentation)
see #103
Big refactoring of objects creation and edition. (javascript cleanup, forms factoring, etc.)
At last something that works pretty well under firefox and with multiple selection possible (using Mootools HtmlTable.Select). There are some problems with IE and Chrome (the position: relative on td elements is not well supported).
Mootools update (1.3)
close#109
Checking limit when creating/updating a mailbox.
* Added domain aliases delete,
* Permissions are not implemented yet.
see #103
* New generic create and remove buttons,
* New javascript confirmation module,
* Fixed a lot of problems about objects relations removal,
* Simpler interface (no more dropdown menus),
* Multiple removal support.
Work in progress:
* New domains admin page, all menus are now at the same level,
* Views, models and forms partial refactoring (better code organization).
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
I've started to separate permissions from the settings panel. It will be availab
le inside the Admin menu for users who are granted the "view_permissions" permis
sion.
new: parameters module refactored. The API is more simple now, there is no need to provide a module name anymore, this last is automatically guessed. Also, a new 'label' field can be provide when declaring a new parameter. It will be used instead of the name.
new: email parsing refactored. My first attempt was really ugly. I did not really studied the various RFC describing how messages are formatted or what IMAP fetch queries can do. Now, I hope this new code will face better unknown types. At least, It will be simpler to update.
* The bigger one concerns fixtures. As django 1.2 resolves it by implementing natural keys, it's becoming a requirement.
* There was also problems 0002_auto__del_field_alias_mbox, my bad...
* It was possible to create aliases that point to addresses of other domains!
* Some path problems in the stats module.
* Some path problems with the autoreply.
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.
Antoine Nguyen