| Commit message (Collapse) | Author | Age | Lines |
| |
|
|
|
|
| |
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.
|
| | |
|
|\ \ |
|
| |\ \
| | | |
| | | |
| | | |
| | | | |
Conflicts:
config/initializers/alaveteli.rb
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When working locally, it's useful to be able to switch between
themes quickly, which essentially involves:
- Updating the general.yml symlink to point to a theme-specific one
- Updating the public/alavetelitheme symlink
- Making sure that the theme exists as vendor/plugins/<theme-name>
This script lets you switch between themes kept in a directory
which is by default called 'alaveteli-themes' at the same level
as your Alaveteli git repository, or can be overriden by the
environment variable ALAVETELI_THEMES_DIR.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The code that extracted the theme name from each entry in THEME_URLS (in
order to require code from a directory whose leaf name is the theme
name) only supported git URLs that ended in '.git'. However, the
themes:install rake task usefully supports a wider range of git URLs -
for example, all of the following were supported:
/home/whoever/themes/blah-theme => blah-theme
/home/whoever/themes/blah-theme/ => blah-theme
git://wherever/blah-theme.git => blah-theme
ssh://wherever/blah-theme.git// => blah-theme
This commit factors out a theme_url_to_theme_name method,
adds tests for it, and uses that method in both:
lib/tasks/themes.rake
config/initializers/theme_loader.rb
... so that a wider range of theme URLs are consistently supported.
|
|\ \ \ \
| |/ / /
|/| | /
| | |/
| |/| |
rails-3-develop
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
jquery.flot.axislabels.js fails to minify with yui-compressor due to a
bug in it relating to delete being a keyword - we can work around this
by using the ['delete'] syntax instead.
|
| | |
| | |
| | |
| | |
| | | |
Since the rotated public body names on the x-axis may be difficult to
read, it's helpful to have them in a tooltip as well.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The time estimates were confusing on two counts:
- The messages mixed locales
- The estimates were hugely inaccurate, since the import slows
down as time goes on
|
| | |
| | |
| | |
| | | |
Thanks to Louise Crow for pointing out this problem.
|
| |/
| |
| |
| |
| |
| |
| |
| | |
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
|
|\ \ |
|
| | |
| | |
| | |
| | | |
http://seclists.org/oss-sec/2013/q4/118
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Fixes #1104.
|
| |\ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
locale/bg/app.po
locale/fr/app.po
locale/fr_CA/app.po
locale/he_IL/app.po
locale/hr/app.po
locale/it/app.po
locale/nb_NO/app.po
locale/pl/app.po
locale/sv/app.po
locale/vi/app.po
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This task was taking a huge amount of memory, even when fetching
the InfoRequest objects with find_each. With an additional find_each
for public bodies (10 at a time) and reducing the batch size for
info requests to 200 at a time, the memory size of this rake task is
kept down to about 400MB.
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
More maintained version has bugfixes for issue described in #1143.
Closes #1143.
|
|/ / / /
| | | |
| | | |
| | | | |
This causes several specs to fail.
|
|\ \ \ \
| |_|_|/
|/| | |
| | | | |
into rails-3-develop
|
|/ / / |
|
|\ \ \
| | | |
| | | |
| | | | |
rails-3-develop
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We were seeing errors in xapian_create_job that indicated that the
current transaction had been aborted but not rolled-back. It seems
that this happened because sometimes xapian_create_job was called
from within another transaction (e.g. from the transaction block in
AdminIncomingMessageController#redeliver). The default behaviour
of nested transactions in Rails is for them to behave as if all
but the outermost transaction blocks had no effect; this means
that the exception thrown in the inner transaction block in
xapian_create_job wasn't causing a rollback, and it was then being
caught before propagating up to the outermost transaction. Thus
the transaction was never being rolled-back so any subsequent
operation on this database connection would error.
This commit fixes this problem by using the :requires_new => true
option to transaction, which asks ActiveRecord to fake genuinely
nested transcations using SAVEPOINT.
Fixes #1124.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
In a subsequent commit, we will want to wrap an additional section
of code with the addition and removal of a hook that creates a
duplicate xapian job, so it's useful for this to be factored out.
This commit introduces a 'with_duplicate_xapian_job_creation'
method that can be passed a block which will be run with the forced
duplicate xapian job creation.
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
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.)
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This adds a public body called "Åčçèñtéd Authority" in the
Czech locale (cs) so that we can create tests that exercise,
for example, searching based on an initial letter that has a
multi-byte representation in UTF-8.
An old test for "add mass tags" in the admin needed to be updated
since it implicitly assumed that all the public bodies in the
fixtures had translations in the :en locale.
The tests for loading CSV files of public bodies also needed to
be updated, since they were assuming that public body names
only contained letters in [A-Za-z ]. Since Unicode character
classes aren't easily available in Ruby 1.8 and it makes little
difference to the test, the character class is replaced by '.'.
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
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
|
|\ \ \ \ \
| |_|/ / /
|/| | | | |
|