- Don't use inline event handlers
- Simplify some of the wording
- Replace the package download list with nice buttons
Design by me & Jonathan, code by me, review by Jonathan and others.
The collection facility was added in
[200~9e70a4e0c32f8db0178f05dac4c1fca7b317e7c5, but no way was added to
view it. To make it a bit more useful, add a static set of info on the
user edit page in /admin/ that shows the last login and number of logins
per site.
Instead of a weirdly located "hover over the checkbox to get a
description" message, put the actual description underneath the
checkboxes. This removes the need for javascript for it, and make the
description a lot more readily available.
This applies only to news tags for now, since that's the only use of
described checkboxes, but hopefully it will make those more clear to
people submitting.
In passing, fix how help_text for multi-checkbox field is shown -- it
was previously shown almost as part of the field name itself, making it
very hard to make out. Now make it look like all other form field help
texts.
Interestingly enough, this showed up because the migration was out of
sync. Normally this means the migration has not been updated, but in
this case it appears the migration is correct and the actual model is
incorrect. Yet both the model and the migraiton were introduced in
commit e2120f0a.
We already set DATETIME_FORMAT, but it makes sense to also set
DATE_FORMAT. In all our frontend templates we were already using an
explicit format, but this will help the /admin/ side.
This is the place to load them to make sure they always load. This means
we can also now remove a hardcoded special varnish purging in the CVE
crawler script, because all saves including those from cron jobs will
now fire the signals and thus the automatic varnish purges.
* Merge all commands into a single text area for ease of copy/paste.
* Add a Copy Script button to each text area to copy the script (without comments and blanks) to the clipboard.
* Centralise the copy/paste code so it can be used elsewhere.
* Always install the database server.
Based on reviews/discussion with Magnus, Jonathan, Daniel and Sehrope.
And dumb as it is they return "200 OK" on the CVE *page* even if the CVE
doesn't exist. So we have to poll both the page and the API call in
order to figure out if it's actually there.
As part of the ongoing effort to make the documentation
both easier to read visually and more friendly for the
PDF building, there have been improvements to the layout
of the reference tables.
This set of changes focuses on the catalog tables that
detail the information in the different PostgreSQL catalogs.
There is also a small adjustment for the function tables, as
one of the CSS classes was renamed in the SGML source.
Author: Tom Lane <tgl@sss.pgh.pa.us>
The new documentation contains a new look & feel for how functions
and operator information are displayed, but this requires some
adjustments to the stylesheet.
This also removes from of the "!important" tags that are used
in top-level parts of the code, as we do not want those to cascade
down to lower layers of the stylesheets.
The web documentation used to suffer from a problem that if a
documentation page were renamed in a newer version, any references
pointing to said documentation would be lost. For example, the feature
known as "Default Roles" was renamed to "Privileged Roles" but caused
a change in the URL.
This patch introduces the ability to create a "DocPageRedirect" by
specifying the previous name of the documentation page (e.g.
"default-roles.html") and the new name (e.g. "privileged-roles.html")
such that the continuity is preserved between versions.
- Debian: Add bullseye and sid
- Ubuntu: Add focal (20.04)
- Add arm64 architecture to each package page
- Modify examples to use PostgreSQL 12
Author: Christoph Berg <myon@debian.org>
Most of our auto-generated emails should not ask for auto replies (like
out of office messages or in particular, "held for moderation" notices
from our own list server), so set this header by default, and also the
header indicating if it's an auto submitted/auto replied message.
Specifically allow auto replies on moderation notices, since that's a
case where it might be really interesting for the moderator to see for
example an out of office message. At least for now that seems like a
good idea.
This helps to ensure readability of the new function table listings
while working around some of the generated code from DocBook
Authors: Tom Lane <tgl@sss.pgh.pa.us> and myself
As the align/valign attributets are deprecated in HTML 5 and as our
documentation generation scripts still spit these out, these selectors
will ensure compatibility, and also fix present alignment issues.
As part of ongoing changes to the structure of tables in the
documentation[1], the HTML property valign is being set to middle
in the table headers, but was not being respected in the pgweb CSS
rules.
This adjusts the table headers to respect the valign property, which
in testing works with both the latest documentation as well as previous
versions (and given most, if not all, table headers to date are not
multi-lined).
[1] https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=e894c61836e4b967f7ec65358fdaed2ba86ed238
This provides information about other projects that people can
contribute to outside of the core PostgreSQL software. Includes
descriptions of each project, how they are used, and how one can
get involved.
Authors: Andreas 'ads' Scherbaum <ads@pgug.de>, myself
With the new django, alerts are raised for everything with status 500,
not juse exceptions. This put a light on a number of places where we
were returning 500 server error code for things that are not actually
server errors. Some should be a regular 200 ok with an error message,
and others should be a permissions error.
Update to django 2.2. Also update a number of older dependencies that
were actually already incorrect before the djago upgrade, and the
deployed versions were newer, but we forgot to update the requirements
file.
