| Commit message (Collapse) | Author | Age | Lines |
|
|
|
|
|
|
| |
User testing highlighted that it was easy to mistake "View Requests" for
a Facebook-style wall rather than the list of all requests. [1]
[1] https://github.com/mysociety/alaveteli/issues/1505
|
|\ |
|
| |
| |
| | |
https://github.com/bbatsov/ruby-style-guide#concat-strings
|
| |
| |
| |
| | |
Uses a different flash message to avoid trying to fetch a
non existent user record
|
|/
|
|
|
| |
Intercepts the request and redirects to the homepage if the comment
field is filled in on the public body update form.
|
|
|
|
|
| |
Allow the same params (since_event_id, since_date) for both formats.
There doesn't seem to be a particular reason not to treat them the same.
|
|\ |
|
| | |
|
| |
| |
| |
| | |
includes various code layout fixes
|
| |
| |
| |
| | |
operation
|
| |
| |
| |
| | |
Filters; more 403s, fewer 500s; added logging; less duplication
|
| | |
|
| | |
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Moves the magic 'site_administration' tag logic to the PublicBody
model. Easier to make the string passed to `PublicBody#has_tag?` configurable
if we want to allow this to be set per install.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- SRP: Do one thing. PublicBodyCSV converts a
collection of bodies in to a CSV formatted
String
- Adds some parenthesis around parameters in
PublicBodyController#list_all_csv
- Let the controller handle what records to pull
out for the CSV export
Arguably this doesn't really need to be anything
to do with PublicBody, but it allows us to set
nice defaults.
|
| | |
| | |
| | |
| | | |
The last remaining usage was removed in c1ee22fe
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Stemming returns 'bore' as the word to highlight which can't be matched
in the original phrase.
Also removes duplicates from the results
|
| | | |
|
|/ /
| |
| |
| | |
Picks these up in `rake notes` and adds semantic meaning
|
| |
| |
| |
| |
| | |
Was switched to && for style but in fact for control flow, and is
what we want.
|
|\ \ |
|
| |/
| |
| |
| | |
Fixes #1448.
|
|\ \
| | |
| | |
| | | |
rails-3-develop
|
| |/ |
|
|\ \ |
|
| | | |
|
| |/ |
|
| | |
|
|/
|
| |
Spacing, parenthesis, etc
|
|\ |
|
| | |
|
| | |
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Some proxies seem to be setting the Client-IP HTTP header to 127.0.0.1.
Rails checks that Client-IP is contained in X-Forwarded-For and raises
the error.
We decided to rescue in this individual case rather than adding a
middleware to strip Client-IP
(http://writeheavy.com/2011/07/31/when-its-ok-to-turn-of-rails-ip-spoof-checking.html#well_thats_stupid_can_we_turn_it_off)
so that we don't introduce unexpected behaviour. If we start to do anything
more with request.remote_ip, then we should look at doing so.
See
http://blog.gingerlime.com/2012/rails-ip-spoofing-vulnerabilities-and-protection
for an in-depth look at this issue.
|
|/ /
| |
| |
| |
| |
| | |
will_paginate intentionally throws an ArgumentError when a non-numeric page
parameter is used. Conveniently, they tag it with WillPaginate::InvalidPage,
so here we rescue with a 404.
|
|\ \ |
|
| |/ |
|
|\ \
| | |
| | |
| | | |
ssh://git.mysociety.org/data/git/public/alaveteli into rails-3-develop
|
| |\ \ |
|
| | |/
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If a request is made and path is something like /%d3 we rescue this with
a custom 404 template.
This gets unescaped as {"path"=>"\323"}.
In the case of a RouteNotFound, ApplicationController#render_exception
renders the general/exception_caught template in to the default layout,
which renders the general/_locale_switcher partial.
This partial calls url_for – sending the full params hash as the
argument – so that a user may return to the existing page in their
chosen locale.
The problem is that url_for tries to construct the url with the hash
{:action=>"not_found", :controller=>"general",
:path=>"\323"}.
ApplicationController#sanitize_params re-encodes the path parameter so
that it can be passed through to url_for without trouble.
|
|\ \ \
| |/ /
|/| |
| | |
| | | |
Conflicts:
spec/factories.rb
|
| | |
| | |
| | |
| | |
| | | |
These are full sentences, not composed on the fly, so should be easier
to translate.
|
| | |
| | |
| | |
| | |
| | | |
These notices are complete sentences, not composed on the fly, so should
be easier to translate.
|
| | |
| | |
| | |
| | |
| | | |
These notices are full sentences, rather than being composed of phrases,
which should make them easier to translate.
|
| | |
| | |
| | |
| | |
| | | |
Should have been removed in
https://github.com/mysociety/alaveteli/commit/b236d4f113187b0e5d87867fc6512e5486f9764f.
|
| | | |
|
| |/
|/|
| |
| |
| | |
Intercepts the request and redirects to the homepage if the comment
field is filled in on the contact form.
|
| |
| |
| |
| | |
The UI provides a list of comment_ids and a newstate="visible" or "hide"
|
|\ \
| | |
| | |
| | | |
ssh://git.mysociety.org/data/git/public/alaveteli into rails-3-develop
|