Do this by setting the max width of the lefthand column in the table, so
it doesn't change when the checkbox for community events is clicked.
A better solution would of course be to make the forms properly
responsive, but that's part of a "next generation website", rather than
a quick fix...
Adds the "badged" flag to the Event model in order to distinguish
community badged events from other PostgreSQL oriented events.
Seven total events will be displayed on the homepage, with up to
four community events displayed. If there are no upcoming
community events then, then the header "Events" is shown.
The event submission interface allows a user to opt-in to
listing an event as a "community" event and provide an
explanation for moderators as to why the event should be
considered a community event.
Expands the list of News and Planet PostgreSQL blog entries to 10.
It's too much of a pain to regenerate the images when a header needs to
change in some way, and having text is better for searching too. This
slightly changes the strength of the headers, but mostly things look the
same as before.
Updated the /support/security/ page to contain information about
reported and resolved security issues in the 2017-11-09 release.
Moved security issues that only affect version 9.2 and earlier
to the security archive page (/support/security_archive/)
Updated developer roadmap and call out box for the cumulative
release.
There were per-site configured rules defined but the regexp was slightly
incorrectly defined. However, we should just simply never crawl urls
like this unless they are normalized, so for now just add them to the
hardcoded exclusion rules.
The next upcoming major release would now be 11, not 10, and it's coming
in the third quarter of 2018.
Also, add in the August planned releases to fill out a complete year.
Hopefully by having the minor release dates cover a year it'll be
clear that whenever we do a release set we remove one and add one at the
bottom, instead of randomly adding/removing them at various times.
There was already an ugly hack to handle this, so make it a bit uglier
with even more hardcoded assumptions. Seems to be working for the site
as it is now, but may definitely need further ugly hacks in the future.
We don't want two different accounts to exist with the same email
address only differing in case. This had already happened for a few
which have been manually fixed, since it turns out we only enforced the
rule on new account creation, not when accounts changed email address or
when they were created using oauth. Also add database level constraints to
make sure this cannot happen again if some codepath is missed.
This happens after a git gc which moves this into packed-refs. So when
this happens, look in packed-refs. If packed-refs also cannot be found,
just return a made up value instead of crashing.
We do this by always spidering every repo rpm available (since the ftp
server doesn't know about supported versions), and then filtering which
versions are shown in the dropdown instead. Given the small number of
versions of either kind, this doesn't make a material difference in the
size of the files anyway.
Javascript by default sorts numbers as strings, go figure. So instead,
properly sort them as number, which makes v10 show up at the top as it
should be.
At some point, the PostgreSQL icon used in the press kit changed
from being a JPG to a PNG, so this change ensures that the PNG
is used. This was also applied to previous press kits as the
JPG icon is missing.
Update the PostgreSQL 10 RC 1 download URL to point to the snapshot
area for downloads, as it contains more directions for how to
download the release candidate.
We want to use the noreply@ email address when sending out notifications
to addresses that have yet to be verified, since we can just ignore
bounces to those.
The press contact group for "Europe and Africa" was relabeled and made
into "Europe, the Middle East, and Africa" to follow common conventions.
Additionally, the contact info for Israel was moved into this group.
I had fixed the OAuth process to deal with this case, but failed to
cover the actual new account creation part which still required it. With
this fix, we allow a signup without a name. If the user wishes to set a
full name on the account it can be done on the profile page for the
user, but it's possible to proceed to access restricted resources
without doing it.
Reported by @Smylers2 on twitter, relayed by @TokenScandi
Previously when signing up for a new account in the middle of an
authentication process, the final redirection URL was lost and the user
was sent back to the /account/ page. Instead, we now redirect to the
proper URL (for sending back to the community auth client site) if it's
available in the session, both for successful signup and for
canceled logins.
In the event of a failed password attempt, we'd loose the "next url"
part in community auth, so once the correct password was entered an
error message about unknown redirect would show up.
If no first or last name is given, fall back to the method of using the
email address to suggest only.
In passing, split out the references to the session in own variables to
make the code a lot easier to read.
