| Commit message (Collapse) | Author | Age | Lines |
|
|
|
|
| |
Add the facility to filter the public body feed by event type
using a query string parameter, e.g. event_type=sent.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously the "log in as" function after 3b6e5a692b852a88f55b21a7210f60a6f7cfc24b
would attempt to log the admin user out before issuing the redirect. Unfortunately
this approach does not work on WhatDoTheyKnow, where the admin pages are served via
a different domain (secure.mysociety.org) and so do not share session information with
the rest of the site.
This commit changes it to mark the PostRedirect with circumstance == "login_as",
which signals the user controller to log out the previous user even if they are
an admin. In other words, the user is logged out on the main site rather than the
admin site, skirting this problem.
Closes #450.
|
|
|
|
| |
Just trailing whitespace & one comment.
|
|
|
|
| |
Fixes #446. See issue for details.
|
|
|
|
|
|
| |
Don't change logged-in user from an admin when visiting a auto-login URL.
Closes #306.
|
|
|
|
|
| |
Include information about what the per-day limit is, and when the
user can next make a request. Fixes #412.
|
|
|
|
| |
Fixes #407.
|
|
|
|
|
|
|
| |
The variables last_request_id and last_body_id were not used
by the view, so it’s clearer to make them local variables so
it’s obvious from the controller code which values influence
the rendering.
|
|\
| |
| |
| |
| | |
Conflicts:
locale/app.pot
|
| |
| |
| |
| | |
Corrected diagnosis, test & fix for issue #351. Fixes #351.
|
| |
| |
| |
| |
| |
| | |
This *ought* to fix the problem with the alert-tracks daemon
opening more and more copies of the xapian db till it exhausts
the available file descriptors.
|
| |
| |
| |
| |
| |
| |
| | |
If a user cannot make new requests because they are
rate-limited, and they compose a request whilst logged
out, include the text of the request in the message
that explains about the rate limit so it is not lost.
|
|\ \
| |/
|/| |
|
| |
| |
| |
| | |
the tin
|
| |
| |
| |
| | |
URL helpers seemed to fix things up
|
|/
|
|
| |
At the same time, cause the tests not to rely on WDTK data. Fixes #396
|
|
|
|
|
|
| |
Add the capability to specify a limit to the number of requests a
user can make per day, which can be turned off for specific users
in the admin interface.
|
|
|
|
|
|
|
| |
Put the most-recently-answered first, rather than the
most-recently-reclassified. This is inspired by issue #370,
though it does not fix all the issues raised in that ticket.
(The wording is still outright misleading in some cases.)
|
|
|
|
|
| |
So, well, I found this change when I ran git diff; and the truth
is that I just prefer it aesthetically. Is that so sinful?
|
|
|
|
|
| |
This is a test for what I thought issue #370 might be. However this
test is passing, so it isn’t that.
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| | |
Conflicts:
app/controllers/request_controller.rb
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|/
|
|
| |
the exception constructor are wrong.
|
|
|
|
| |
large databases, the sorting of such large batches causes an extreme slowdown).
|
|\ |
|
| | |
|
|/
|
|
|
|
|
| |
(If DEBUG_RECORD_MEMORY is enabled)
This is useful for tracking down bugs that cause Rails to go into an infinite or very long
loop, as the recent Xapian wildcard bug does.
|
|\ |
|
| |\ |
|
| | |\
| | | |
| | | |
| | | |
| | | | |
Conflicts:
app/views/public_body/_search_ahead.rhtml
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
fails.
|
| | | |
| | | |
| | | |
| | | | |
didn't call "integrate_views", so the rendering part was mocked by RSpec instead of executed.
|
| | |\ \
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
app/controllers/application_controller.rb
|
| | | |/
| | |/|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Wildcard searches in Xapian can expand uncontrollably, consuming
all available RAM and crashing the server. This has been a real
problem on WhatDoTheyKnow.com. The underlying issue is tracked
in http://trac.xapian.org/ticket/350
This changeset imposes a limit on wildcard expansion. The type-ahead
search will first try a wildcard query, and if that fails because
of too much expansion will fall back to a plain non-wildcard search.
|
| | |/
| |/| |
|
| | |
| | |
| | |
| | | |
Another temporary patch to protect the live site.
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Do not use FLAG_WILDCARD or FLAG_PARTIAL anywhere, because wildcard
searches can crash the whole server as per http://trac.xapian.org/ticket/350
(e.g. http://www.whatdotheyknow.com/body/search_ahead?query=app will
crash the server prior to this commit.)
This is a temporary fix while we investigate the possibilities of
the set_max_wildcard_expansion() method, which should make it possible
to alleviate this issue.
|
| | |
|
|/ |
|
| |
|
|
|
|
| |
errors ad hoc as I find them that result from the workaround code. Fixes #328 (for good, I hope).
|