| Age | Commit message (Collapse) | Author |
|---|
|
Sync up the "warning button" filtering with that of the alerts, which
means we don̈́'t alert for emails that aren't supposed to be sent yet.
This becomes more relevant as we also stop trying to send emails that
are set to be sent in the future, in preparation for upcoming
functionality to schedule email sending.
|
|
It's wrong to list upcoming events that the user is registered for under
"past events", so split them into two separate groups.
Reported by Devrim Gunduz
|
|
Just like for cfp and cfs, make it possible to specify an exact
timestamp when registration will open and close, if wanted.
|
|
This has been sitting in the corner of legacy for far too long. Rename
to registrationopen to make it much omre clear and consistent with other
entries, and more searchable.
Quite likely one or more places were missed in this commit and will need
to get cleaned up...
|
|
Allows specifying at which time call for papers and call for sponsors
are opened, instead of manually having to flip a checkbox. For the call
to be opened, it needs to *both* satisfy the checkbox and the time
range, unless the timerange is left completely empty (the default) i
which case the checkbox is used along like before.
Fixes #34
|
|
Instead of requiring people to get on IRC, support member meetings in a
web browser. To make this work, there will be a simple websockets based
server (hosted in a separate repository) that will act as a relay,
and a trivial web app to handle the frontend.
Also include a native handling of polls in the system, including
timeouts, being typical actions during these meetings.
Meeting log and handling goes in the database, making it easy to extract
later for generation of official meeting minutes.
Code by me, layout and styling by Ilaria Battiston.
|
|
|
|
Otherwise the main dashboard breaks
|
|
The links in the RSS feeds were correctly updated to know how to do a
conference-specific permalink, but not the Read More button on the
frontpage.
|
|
This will work differently for conferences and non-conferences once we
add proper timezone support, so abstract it out into a separate couple
of functions. For now they both return the same thing, but this will
change in a later commit.
In passing, fix missing datetime.now() -> timezone.now() conversions.
|
|
While refunds could be viewed on the individual invoice that was
refunded, it's useful to also have a global view of refunds on the admin
page (which links to the invoices as necessary).
Button on the frontpage will be highlighted if there are any refunds
that are in pendning state (either waiting for us to issue them or
waiting for completion).
|
|
As a step on the way to better timezone support, use the django function
timezone.now() instead of datetime.now(). As long as we haven't enabled
timezones globally this becomes a no-op and does exactly what it did
before, but once timezones are enabled it will generate datetimes that
are aware of this.
No functionality change but gets a lot of boiler-plate out of the way
making the verification of the rest of the timezone work easier.
|
|
This adds generic support to all managed bank accounts for handling
uploaded files. The idea is that for banks that don't have a working API
to download transaction list, one can be downloaded manually from the
bank and then uploaded into the system, and thereby using the same type
of matching etc.
Each account also gets to set a time limit after which it shows up as
"you should be uploading a file!" in the interface, and a scheduled job
will email a reminder to the treasurer email daily (can be set to 0 to
turn off).
|
|
|
|
This adds a viewer and editor for the mailqueue to the dashboard,
superuser only.
While at it, expose time and subject directly in the queue to make it
easier to determine what is what.
Most of the time this is not going to matter because emails are
short-lived in the queue. But during development and definitely during
debugging, it can be quite useful.
Move the "parsed mail view" out of django admin and into the backend
view so we don't have to maintain it twice. There is very little use for
the admin view anymore, so it's OK to just show the raw data there.
|
|
Initially, bank transactions when there are pending one, and scheduled
jobs if something is broken.
|
|
|
|
This only adds a link to the existing invoice admin system along with an
editor for VAT rates, for now.
|
|
|
|
Previously we'd show it even if the module was disabled, as long as the
user was superuser.
|
|
|
|
Fix some of the minor parts of the backend views/lists that did not work
outside of confreg.
As a demo of it working, add administration views for the membership
module, specifically allow editing of members and meetings.
Create a generic admin dashboard page on /admin/. This one links through
to the /events/admin/ page like before, and also to the new membership
module if the user has permissions.
|
|
|
|
In passing remove some comments that were pointless
|
|
In an effort to close up with PEP8, we should use spaces for indent
rather than tabs... Time to update your editor config!
|
|
Link this to the account homepage. Also consistently talk about events
on these pages, and fix a spelling error.
|
|
In particular for "Legacy Series" this can be useful, especially since a
conference has to be in a series.
The actual series is still viewable for people who have kept their link
around, but not listed anywhere.
|
|
A number of improvements and unifications for news:
* News posts now get authors
* Authors are from NewsPosterProfile:s, which will include a full name
and an "urlname"
* Authors can also be specified as "can post global", which should
give rights to post on the global feed. Right now the global feed
requires superuser access anwyay, but for the future...
* News can now be posted at conference level as well as previous
global only
* Front page of website pulls in a combination of global news and
conference news. Global news can be given a "high priority until"
field that ensure it sits at the top of the frontpage until a
certain date, so conference news can't push it off.
* Each conference gets it's own RSS feed. This one is also available
via JSON for an easy way to pull it into the conference site itself.
* All links to posts in the conference feed goes to the conference
homepage. It's really only designed for transient news.
* Each user also gets it's own RSS feed. This is designed so that it
can be submitted to an aggregator like Planet PostgreSQL which
requires personal feeds. Conference specific news are automatically
prefixed by conference name.
* Each post can individually be toggled if it should be included in
the RSS feed or not
* Re-adds the news archive, with a paginated view
* Each post can individually be toggled for inclusion in the news
archive, so it's possible to create more transient news. News
archive *only* contains news from the global feed, not the
conference feeds.
* Makes the "read more" button on the frontpage only show up if the
entire news post did not fit
|
|
This replaces the base design with something that's a lot more modern,
based on bootstrap etc. Lots of inspiration from the updated main
postgresql.org website. Also is at least attempting to be a little bit
responsive, unlike previous website.
Also restructures the event section completely, to be able to more focus
on the events that we run.
Does not change anything fundamental in the backend systems, and
*should* have no effect on downstream conferences as those templates are
just wrapped in a different otuside now.
|
|
Fallout from a merge failure :/
|
|
Now also confreg, confsponsor, confwiki, newsevents, the old invoice
system and the root.
|
|
This allows us to create news articles which will appear only
when then time is right (and the date has passed that which is
in the database :).
|
|
This adds a /news view with an associate template (though the template
is not terribly well designed, merely functional at present).
Also change the /feeds/news to use the settings.ORG_NAME value instead
of having a hard-coded string.
|
|
Will be removed in Django 1.9, and is spamming the logs
|
|
Seems this was only enabled in one of my feature branches. It should
definitely be enabled, to make sure it protects the forms of the site.
There may be some forms that are now broken - there might be more views
that require @csrf_exempt. We'll have to fix those one by one.
|
|
|
|
Enable admin interface to edit news and events.
Add countries module to reference for events.
Implement RSS feeds for news and events.
|
