| Commit message (Collapse) | Author | Age | Lines |
... | |
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Between rails 3.2.0 and 4.0.1rc4, timestamps were constrained to be
non-null. As globalize creates the public_body_translation table with
timestamps, this means there are errors in the tests when trying to
insert the fixture data, which doesn't have timestamps. These errors
were only appearing on Travis because locally the test database is
cloned from the development structure rather than being created by
running the migrations.
|
|\| | |
| |_|/
|/| |
| | |
| | |
| | |
| | | |
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.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
If activesupport isn't present, the mail gem will load it's own version,
and when rails is eventually loaded in this script, the warning
"warning: already initialized constant VALID CHARACTER" is written to
standard error.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
The remaining deprecation warnings are for the plugins, and they
interfere with incoming mail handling by producing output on stderr.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
The new name value doesn't escape a double quote within single quotes,
which seems more correct.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
As suggested in http://guides.rubyonrails.org/3_2_release_notes.html
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
As described in step 1.2 of
http://guides.rubyonrails.org/3_2_release_notes.html.
Rails to latest 3.2 - 3.2.15
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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.
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
An attempt to get image-path to work in sass files.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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 jquery-rails documentation for the latest version now recommends
using the jquery-ui-rails plugin instead. To avoid the possible
confusion of having two copies of jquery-ui in different gems, update
jquery-rails to the version that doesn't contain jquery-ui.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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.
|