| Commit message (Collapse) | Author | Age | Lines |
| |
|
| |
|
|\
| |
| |
| |
| |
| | |
Conflicts:
app/models/track_mailer.rb
app/models/track_thing.rb
|
| |\ |
|
| | |
| | |
| | |
| | | |
wombleton:feature/440_sparkly_admin_css)
|
| | |
| | |
| | |
| | | |
controller when the method doesn't exist in Alaveteli code. See [this comment](https://github.com/sebbacon/alaveteli/issues/320#issuecomment-5711523) for discussion.
|
| |/ |
|
| |
| |
| |
| |
| |
| | |
* 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)
|
|/
|
|
|
|
| |
* Change "email me about stuff" wording to "follow" throughout
* Introduce a new flag that the user can set, which controls if they get email alerts
* Add a new link to a "wall" for logged in users where they can see a feed of all the things they're following
|
|
|
|
| |
after they've "followed" search results. Fixes #487
|
|
|
|
| |
Fixes #454
|
|\ |
|
| | |
|
| |\
| | |
| | |
| | |
| | | |
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.
|
| | |
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| |
| |
| |
| | |
Fixes #446. See issue for details.
|
| |
| |
| |
| | |
Closes #428
|
| | |
|
|/
|
|
| |
Fixes #421.
|
|
|
|
|
|
| |
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
|
| | |
|