| Commit message (Collapse) | Author | Age | Lines |
| |
|
|
|
|
|
|
| |
As suggested in the release manager's checklist, this is to
preserve the updated translations against the old set of
msgids. Note that there were some problems with locale/cy/app.po
which I've fixed on the rails-3-develop branch, but I haven't
added those fixes here.
|
| |
|
|
| |
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
|
| | | |
|
| | | |
|
| | | |
|
| | |\ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Precise is now the long term maintenance version, and has a more
up-to-date package of rubygems available.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Version 1.8.15 from backports should not have the Syck bug described
here:
http://stackoverflow.com/questions/9004804/invalid-gemspec-illformed-requirement-yamlsyckdefaultkey0xb5f9c990-3
http://blog.rubygems.org/2011/08/31/shaving-the-yaml-yak.html
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
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.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
So that files attached to different messages with the same name and
url_part don't get overwritten.
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
Versions of factory_girl after 3 are not compatible with ruby 1.8.7
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Add the 'Actions' to the incoming message admin - now that this has both
this and the prominence form, it seems like the logical place to link to
from the main request page.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Make old_unclassified_params method consistent with
last_public_response_event and associated methods.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
get_last_response_event and get_last_outgoing_event are used in various
places to determine which events to link to, use in queries etc.
Restrict them to refer to the last publicly visible event of the
relevant type, and rename them to make that clear.
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
Add some tests that it's working on the outgoing message model.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
app/views/request/_incoming_correspondence.html.erb
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
At least some of the logic for incoming and outgoing message prominence
is going to be identical, so move it to a module they can both include
and use.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Add some sequences to make sure that we don't get validation errors on
unique fields.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
spec/integration/view_request_spec.rb
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
We want to be able to authorise access to it.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Use send_file to send zips. Also adds 'all_can_view_all_correspondence?'
- is this request completely cachable, or do we need to cache different
versions for different levels of privilege?
|