For example, while a link to "/docs/release/9.1.0/" would work,
going to "/docs/release/9.1/" would not; in this case, it would
show the release details for "9.0.1". While the probability of
someone modifying the links to see the different release notes
is low, we would still need to take action on what is an
incorrect link.
Instead of returning a 404, this transposes the major/minor
version to point at the canonical version number and render the
expected page. This is set up to work for the 6, 7, 8, 9 series.
Reported by: Nikolay Samokhvalov <samokhvalov@gmail.com>
In this case, I had forgotten to update this bio in the first
pass. I'll ponder that perhaps we should put something in the
database to manage this in the future.
The addition of the fieldsets did not account for the fields
themselves from being removed from the new organisation form.
The OrganisationForm now removes the appropriate fieldset when
the fields are not available in this form.
This is changed to reflect the committee for the 2020-2021 term.
This also changes the "Past Members" structure to list out
names and which terms they served.
* Turn main links into buttons
* Have a link from the archive back to the upcoming events, not just in
one direction.
* Write a paragraph about submitting events, similar to what was
recently done for news.
This hasn't been used for a long time but was left over in a template.
It would render a link with a space in the title and missing the word
"events"...
If an email is already added as a secondary address to one account,
don't allow creating a new account using that email, unless it's
removed. Otherwise we end up with the same email address attached to
multiple different accounts, which can cause big problems downstream.
This should never have been allowed of course, but was missed when
support for secondary emails was added.
* Add a fa icon for tags to the buttons that are clicked for news tags,
to make it more clear what they are.
* Show a badge with the tag on each item when browsing the list.
* Change the buttons to be badges when viewing an individual item, and
move them to the top of the page instead of the bottom for consistency
with the listing.
In passing, add some spacing between the header and the text when
viewing a news item, because it looks a lot better.
For now we do 10 items per page, but that's easy to adjust.
Paginate based on the date (so create an index on the date field to
simplify this), making page rendering and load a *lot* faster.
While we don't use the github workflow for our development, it doesn't
hurt to get a post-commit notification when somebody forgot to validate
things pre-commit (using the hook we have). This hook also runs with
exactly the version of python/pycodestyle that we are using in
production, which might help someone.
At some point the code to drop down parts of the list broke for version
numbers that had a dot in it, meaning all versions prior to 10.
Unrelated to the release today. Fix is to just render 96 instead of
9.6..
Bug spotted by Stephen Frost
An annual review of general content on the website, including adding
in new tidibts of information based on the new PostgreSQL release,
in this case for PostgreSQL 13.
This also includes a change in the descruption of the BSD
family of packages to use the term "operating system", which
is the preferred language for describing the different BSD
options.
Author: Daniel Gustafsson <daniel@yesql.se>
This installer is only supported up to PostgreSQL 10 and based on
the overall outbound traffic numbers to the installer, it makes
sense to remove it instead of carrying the overall maintenance
burden.
This provides a much more concise and accurate description of
what is on this page, as well as an ordering of the installers
based on the measured popularity of them.
The measured traffic patterns indicated that people wanting to
build from source were not getting to the source tarballs from
the Linux package pages, rather a) people on the package pages
wanted the pre-built packages and b) people who wanted source
code went directly to the source code from the main downloads
page.
Change the subject to use the title of the object instead of the id, and
include a link to the moderation page. There's surely more to be done,
but this is a decent start.
This will trigger the same reset-your-password email as a user initiated
one, but it'll cut out one step and be a bit more user friendly...
Also, if this is done with an OAuth connected account, it will be
converted into a regular one (something we don't allow the end user to
do, for support reasons)
This also adds an entry to the user editor in the admin view that shows
if the user *is* an oauth user or not, or if they might have an old
"unmigrated" password.
