| Age | Commit message (Collapse) | Author |
|---|
|
This changes both the storage location of the files and the URL. This
aligns it up with how (almost) all our other django apps work, so good
for consistency.
|
|
|
|
django-selectable is no longer maintained, and will cause issues in
newer versions of django.
selectize is what we use in the pgeu-system codebase today, so copy the
handling over from there.
|
|
Since the upstream main website now handles secondary email addresses,
centralize the handling to there. This removes the local handling
completely, except that we store them in the database. The new
push-changes API ensures that they are kept in sync with upstream.
|
|
|
|
|
|
|
|
|
|
Seems django 1.11 automatically enables caching template loader, which
of course breaks the ability to make any changes to the pages of a
website without restarting it. And there is no way to turn it off other
than to explicitly configure individual loders (the logic to turn it on
in non-debug configurations is hardcoded and cannot be changed).
|
|
This allows the archivs server to ping the CF app to pick up updates to
mailthreads quicker.
|
|
Change to syntax compatible with newer Django, still works on current
version.
|
|
This has probably been needed since an upgrade a long time ago but got
stuck in a separate branch. Fixes the case where the admin interface
could end up rendering a login form that would then not work, instead of
providing the proper redirect.
|
|
|
|
|
|
Each user can add a secondary email (well, more than one) and then pick
one of those when sending email.
Addresses are validated by sending a token to the newly added address,
with a link to click to confirm it. Only a fully confirmed address can
actually be used.
|
|
It also breaks the RSS feeds
|
|
|
|
On-demand login can be confusing for some...
|
|
|
|
|
|
|
|
May very well do a complete rebase later to get rid of history
|
