| Commit message (Collapse) | Author | Age | Lines |
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Under Ruby 1.8.7, you can parse a CSV file with the
following code (Example A):
require 'csv'
CSV.parse('foo.csv') do |row|
puts "got row: #{row.inspect}"
end
Rather confusingly, under Ruby 1.8.7, CSV.parse can also
take a string representation of the contents of the file
as its parameter, so this also works (Example B):
require 'csv'
CSV.parse("1,hello,red\n2,goodbye,green") do |row|
puts "got row: #{row.inspect}"
end
However under Ruby 1.9.3, CSV.parse only expects a string
representation of the contents of the CSV file, so only
Example B works; Example B fails silently (interpreting
the filename as a single cell CSV file, typically).
The import:import_csv rake task unfortunately relied on
both A and B working. This commit fixes this by adding
PublicBody.import_csv_from_file, and refactoring
PublicBody.import_csv to use the newly added class method,
and adds a test to check for any regression in this
behaviour.
(This means that the usage of import_csv in the admin public
body controller's import_csv action could now be changed
to use PublicBody.import_csv_from_file directly from the
uploaded file, which would be more efficient and cope
with larger files without using lots of memory.)
Fixes #1229
|
|\ \ |
|
| | | |
|
| | | |
|
|\ \ \ |
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The subject line wasn't being explicitly specified in
RequestMailer.fake_response and a default of "Fake Response" (somehow
based on the method name) was being used instead; this subject line
would sometimes be visible to users and authorities and caused alarm
to them. Instead, we use the standard subject lines for followup
emails for the InfoRequest.
Fixes #1105.
|
|/ /
| |
| |
| |
| |
| |
| | |
Previously the admin links and permalinks on annotations and incoming
correspondence were reversed, this commit makes the admin link
consistently appear on the left and the permalink thingo appear on the
right.
|
|\ \
| | |
| | |
| | | |
into rails-3-develop
|
| | | |
|
| |/
|/| |
|
|\ \
| |/
|/|
| | |
rails-3-develop
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
rails-3-develop
Conflicts:
Gemfile.lock
|
| |\ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
feature/switch-to-asset-pipeline
Conflicts:
Gemfile.lock
app/assets/images/admin-theme/ui-bg_flat_0_aaaaaa_40x100.png
app/assets/images/admin-theme/ui-bg_flat_55_fbf9ee_40x100.png
app/assets/images/admin-theme/ui-bg_flat_65_ffffff_40x100.png
app/assets/images/admin-theme/ui-bg_flat_75_cccccc_40x100.png
app/assets/images/admin-theme/ui-bg_flat_75_dadada_40x100.png
app/assets/images/admin-theme/ui-bg_flat_75_e6e6e6_40x100.png
app/assets/images/admin-theme/ui-bg_flat_75_ffffff_40x100.png
app/assets/images/admin-theme/ui-bg_inset-soft_95_fef1ec_1x100.png
app/assets/images/admin-theme/ui-icons_222222_256x240.png
app/assets/images/admin-theme/ui-icons_2e83ff_256x240.png
app/assets/images/admin-theme/ui-icons_454545_256x240.png
app/assets/images/admin-theme/ui-icons_888888_256x240.png
app/assets/images/admin-theme/ui-icons_cd0a0a_256x240.png
app/assets/javascripts/admin.js
app/assets/javascripts/admin/jquery-ui.min.js
app/assets/javascripts/application.js
app/assets/javascripts/jquery-ui.min.js
app/assets/javascripts/jquery.flot.errorbars.min.js
app/assets/javascripts/jquery.flot.min.js
app/assets/javascripts/stats.js
app/assets/stylesheets/application.css
app/assets/stylesheets/fonts.scss
app/views/general/_stylesheet_includes.html.erb
app/views/layouts/admin.html.erb
app/views/layouts/default.html.erb
app/views/public_body/statistics.html.erb
config/application.rb
config/environments/development.rb
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
ActionMailer now checks for a 'to' address on sending mail, so supply
one so that we can check exception notification mail sending. Also check
that we have one before trying to call the exception notification code.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Under the Rails hood, using the setters for attributes now involves
calling the getters too, (for a will_change? check), so these calls
became circular - use write_attribute instead.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The need for this was removed in
0ec315c52a731ff149977b9231a15770fa3bd742, and it now causes a
MissingAttribute error.
|
| | | |
| | | |
| | | |
| | | | |
Passing it as an argument is deprecated.
|
| | | |
| | | |
| | | |
| | | | |
Passing it as an argument is deprecated.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
In render calls, that's now deprecated in favour of using the :formats
option.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Following the suggestion to use the sass-rails font-path helper:
http://aokolish.me/blog/2011/12/24/at-font-face-with-the-asset-pipeline/
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
The "font-size: ;" in jquery-ui-1.8.15.custom.css breaks asset
precompilation.
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
We no longer need to run compass to regenerate the admin CSS - it
will be done automatically.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
As far as I can tell, we only use the 'tabs' module in
admin and 'datepicker' on the user-facing part of the site.
The advantage of using this packaging of the gem is that
its assets are in the gem, which simplifies things greatly -
otherwise we'd end up doing something like rewrite the jquery-ui
CSS to SCSS, referencing the image assets via sass-rails helpers
or keep them in their expected paths in public or something.
(Thanks to Louise Crow for pointing out the problem of just
moving jquery-ui's image assets into the asset pipeline.)
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The intention is to stop including our own custom build of jquery-ui
but instead use the jquery-ui-rails gem, which works well with the
asset pipeline. This commit should remove all traces of the old
download of jquery-ui.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
In production mode, the javascript_include_tag and stylesheet_link_tag
helpers seem to fail unless the non-manifest assets are given the
full basename, whereas the manifests, e.g. application.js, can be
referred to as just, e.g. 'application'.
|