| Commit message (Collapse) | Author | Age | Lines |
| |
|
|
|
|
| |
be sent
|
| |
|
|
|
|
| |
admin interface (requires adminbootstraptheme).
|
| |
|
| |
|
|
|
|
|
|
| |
* Allow users with `super` admin level to use the administrative interface.
* Allow bootstrapping these users with an Emergency User over HTTP Basic Auth
* Introduce new `SKIP_ADMIN_AUTH` setting to allow all admin auth to be bypassed (used by mySociety)
|
|
|
|
| |
after they've "followed" search results. Fixes #487
|
| |
|
| |
|
|
|
|
| |
Fixes #454
|
|
|
|
| |
purge.
|
|\ |
|
| |
| |
| |
| | |
collection (e.g. `@user.info_requests.each`)
|
| | |
|
| |\
| | |
| | |
| | |
| | | |
Conflicts:
spec/controllers/request_controller_spec.rb
|
| | |
| | |
| | |
| | | |
Next step: making it asynchronous, e.g. with a queue of things to purge via a cron job.
|
| | |
| | |
| | |
| | | |
Closes #428
|
| | |
| | |
| | |
| | | |
Fixes #421.
|
| |/
|/|
| |
| |
| | |
Add the facility to filter the public body feed by event type
using a query string parameter, e.g. event_type=sent.
|
|\ \
| | |
| | | |
Small fixes
|
| | | |
|
|/ / |
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| |/
| |
| |
| | |
Fixes #446. See issue for details.
|
| | |
|
| | |
|
| |
| |
| |
| | |
Fixes #446. See issue for details.
|
| | |
|
| |
| |
| |
| | |
Closes #428
|
|/
|
|
| |
Fixes #421.
|
|
|
|
| |
Closes #415.
|
|
|
|
|
|
| |
Don't change logged-in user from an admin when visiting a auto-login URL.
Closes #306.
|
|
|
|
| |
Fixes #407.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Issue #409 seems to be another problem of the same type as #408,
though with the important difference that the bug in this case
is in the test suite rather than the code under test.
RequestMailer sends alert emails warning of overdue requests.
However it does not specify the order that these messages are
sent in, but runs over the overdue requests in whatever order
they are returned by a database query (that does not have an
order by clause). Therefore it is not safe for the test code
to assume that the alert mails will have been sent in a particular
order: just as with #408 it seems that they were *usually* sent
in the order assumed by the test code, but occasionally not --
which would result in sporadic test failures.
Closes #409.
|
|
|
|
| |
Really, what was that about?
|
|\
| |
| |
| |
| | |
Conflicts:
locale/app.pot
|
| |
| |
| |
| | |
Corrected diagnosis, test & fix for issue #351. Fixes #351.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The ad hoc specification of fixtures has been an ongoing source
of bugs in the tests. The straw that broke the camel’s back is
that 7c6eb09 requires the fixtures to be loaded in order (i.e.
children before their parents), and it would have been a painful
process to reorder all the dozens of different fixture lists,
but the test system ought to be more reliable this way.
|
|\ \
| |/
|/| |
|
| |
| |
| |
| | |
the tin
|
|\ \
| | |
| | |
| | |
| | |
| | | |
Conflicts:
config/general.yml-example
doc/CHANGES.md
|
| |/
| |
| |
| |
| | |
I am not sure why the tests anyway passed with this mistake, but
clearly those trailing .should's ought not to have been there.
|
| | |
|
|/
|
|
| |
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.
|
|
|
|
| |
Test that duplicate requests are coalesced on the front page.
|
|
|
|
|
|
|
| |
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.)
|
|
|
|
|
|
| |
Add some more test data, and fix the tests to accommodate both this
new test data and the fact that raw emails are now correctly loaded
into the test environment.
|