| Commit message (Collapse) | Author | Age | Lines |
|\ |
|
| |
| |
| |
| |
| | |
This is for the case where there are no results and the user was
explicitly searching for authorities.
|
| | |
|
| |
| |
| |
| |
| |
| | |
The context here is that bodies have merely been included in the search
- it hasn't been explicitly restricted to bodies. So the links don't
really make sense.
|
| |
| |
| |
| | |
Contributes to #1118.
|
| |
| |
| |
| |
| | |
This is the template used when the user is searching for a public body
specifically to make a request to.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In the initial release of public body statistics to WhatDoTheyKnow
a public body only intended for testing ("mySociety Test Quango")
was included in the statistics. This commit causes public bodies
tagged with "test" to be excluded from the public body statistics
page.
Fixes #1115.
|
| |
| |
| |
| |
| |
| | |
This simplifies the statistics action of the PublicBodyController
and makes it easier to test the functionality now in the
simplify_stats_for_graphs method.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We have changed the denominator of the proportion-based statistics
to only include requests that are both visible and not
'awaiting_description'. This would mean, however, that the numerator
could be larger than the denominator. This commit updates the
calculation of those statistics to also exclude any hidden or
unclassified requests.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
The WDTK volunteers pointed out that it's not fair to include
hidden requests in the denominator, since they're typically hidden
for a good reason (e.g. being vexatious, spam, etc.), and we have
no information about those that are awaiting_description (i.e.
unclassified) so they should be excluded as well.
|
|/
|
|
|
|
| |
This counts only those info requests that have prominence 'normal'
(i.e. are not hidden) and are not 'awaiting_description' (i.e. that
they have had some basic status classification).
|
| |
|
|
|
|
| |
These are regenerated with "bundle exec annotate"
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
The 'if data' needs to be earlier to avoid an error if one of the
statistics columns hasn't been filled in by the
stats:update_public_bodies_stats rake task yet.
Thanks to Louise Crow for pointing this out in code review.
|
|\|
| |
| |
| | |
rails-3-develop
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
Now that there are rotated names on the x axis we shouldn't need
to worry about them overlapping, which was the reason for limiting
the number to 8 in the first place.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Now if you click on the bar representing statistics for a
particular public body, it will take you to that public
body's page.
In addition, the bars are highlighted when you hover over
them.
|
| |
| |
| |
| |
| |
| |
| | |
Previously, the JSON included all the columns from the public
body table, which was unnecessary and included the public body's
email address. Instead, just include the name and URL of the
public body.
|
| |
| |
| |
| |
| |
| | |
This commit adds the tickrotor extension to Flot, which allows
rotated labels for public bodies. This extension is licensed
under either MPL 1.1, GPL 2.0 or LGPL 2.1.
|
| |
| |
| |
| |
| |
| | |
This updates flot to version 0c2f6e3, which should be shortly before the
release of 0.8.2. This is required for the tickrotor extension
(allowing rotated public body names on the x-axis).
|
|\ \
| | |
| | |
| | | |
rails-3-develop
|
| |/
| |
| |
| |
| |
| |
| |
| | |
For importing a very large number of public bodies, it's mostly likely
less frustrating to import them from the CSV file using this rake task
instead of using the form in the admin interface.
Fixes #1132
|
|\ \
| |/
|/| |
|
| | |
|
| |
| |
| |
| | |
Fixes #1104.
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | | |
Apart from anything else, we don't want translators to have to worry
about the special case text. See https://github.com/mysociety/whatdotheyknow-theme/commit/2078febca5181ce3b1a9c0fae0123ae5f6448718 for the corresponding change to whatdotheyknow-theme.
|
|\ \ \ |
|
| |/ / |
|
|\ \ \
| |/ /
|/| |
| | | |
rails-3-develop
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In the rare circumstance that someone created a public body
whose name started with a lower case letter outside [a-z]
with Alaveteli running under Ruby 1.8, the letter would not be
upcased correctly before saving to the first_letter column.
This commit fixes that by using a Unicode-aware upcase function.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Under Ruby 1.8, it was previously impossible to use one of the "first
letter" alphabet links on the public body listing page if the first
letter was outside [A-Za-z] since the test for the parameter only
being a single letter wasn't aware of the possibly of multi-byte
characters. In addition, upcasing of letters outside [A-Za-z] didn't
work because String#upcase in Ruby 1.8 isn't Unicode-aware.
This commit fixes these two problems, so that non-US-ASCII first
letter links will work under Ruby 1.8.
(Fixes #1112.)
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Clicking on the "This request requires administrator attention"
label would actually select the "I've received an error message"
option due to the label referring to the wrong input element.
This change corrects the label.
Thanks to Jedidiah Broadbent for spotting this bug.
Fixes #1113
|
| |/ /
|/| |
| | |
| | |
| | |
| | | |
These are only being rendered into a comment, and have been for a long
time. They now appear to be causing problems with non-ascii characters
in ruby 1.9, so drop them completely.
|
|\ \ \
| | |/
| |/| |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
In fact, we do still need to set permissions.
This reverts commit 56ce526acdcb1b5493bc11f14b751b5c3f02f686.
|
|/ /
| |
| |
| | |
Fixes #1104.
|
| |
| |
| |
| | |
Fixes #1101.
|
| |
| |
| |
| |
| | |
This is something you should be able to override without having to take
on the maintenance of your own layout.
|
|\ \ |
|
| | |
| | |
| | |
| | | |
Fixes #1082.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
Gemfile
app/views/admin_request/edit_outgoing.html.erb
config/packages
doc/CHANGES.md
doc/INSTALL.md
spec/models/info_request_spec.rb
spec/models/public_body_spec.rb
|
| | | |
| | | |
| | | |
| | | |
| | | | |
As @mhl points out, this more clearly indicates that they may come back
at some point.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Either rails or the webserver will be sending it, we're not redirecting
anymore.
|