| Commit message (Collapse) | Author | Age | Lines |
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Store the search parameters in the flash when a search is made via the
select_authority_path page. Stores the parameters for both POST and
AJAX typeahead searches.
The presence of stored search params renders the link on the
PublicBodyController#show template.
“keep”s the search params in PublicBodyController#show so that if the
user clicks the browser’s back button the “Back to search results” link
can still be rendered on the next search result they click.
“keep”s all flash keys in ServicesController#other_country_message
as it’s called through AJAX and ends up sweeping the flash. [1]
[1] More details about this:
http://mikenaberezny.com/2007/09/08/keep-the-flash-and-test-it-too/
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Dropped the law_used_full interpolation:
So I think there are two significant bits of context here. One is that the
law_used_full attribute is derived from law_used, which in turn is set on
InfoRequest initialisation based on the tags applied to the public body. So
different requests in a batch could have different values for law_used_full
- some of them might be to bodies that only accept environmental
information requests. So using the value from the batch template is not
really a good proxy for the whole collection.
The second is that, in any case, the distinction between the two types of
request is a UK-specific feature which should be moved to the UK theme
(#2085).
Given these two factors, I think the cleanest thing might be to drop
law_used_full from this descriptive text, and just have it say "Your
requests will be sent shortly", without specifying what law will be used.
– Louise Crow (@crowbot)
|
|/ |
|
|\ |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Seems more logical to make this one method that figures out what to do
based on file type. Plus, incoming message does so many things, it
seemed like having these related methods be separate would make them
easier to read and understand. Also, email, mobile and login
substitution texts weren't being translated. Finally, I think passing
the censor rules and masks as arguments is a first step in some more
decoupling of models.
|
| |
| |
| |
| | |
Use the per_page parameter to limit the results returned
|
|/
|
|
|
| |
Action now supports the `request_from` param as per the Xapian filtering
system to filter search typeaheads by public body
|
| |
|
| |
|
|
|
|
| |
Picks these up in `rake notes` and adds semantic meaning
|
|
|
|
| |
Fixes #1448.
|
| |
|
|\
| |
| |
| |
| |
| | |
Conflicts:
config/general.yml-example
spec/factories.rb
|
| | |
|
| |
| |
| |
| | |
Add or remove all buttons, ajax search as you type.
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Create the batch and associate new requests with it, send the outgoing
messages, and redirect to a page for the new batch.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Add validation, preview as in single request creation. Add comments
noting further work to be done in this action.
|
| |
| |
| |
| |
| |
| | |
Give it basic access control, and add some conditionals to the 'new'
template around bits that use @info_request.public_body so that they
render something different if @batch is assigned.
|
| |
| |
| |
| | |
Should retain a list of selected public bodies across searches.
|
| | |
|
| | |
|
|/
|
|
| |
Make specs a bit more focused, remove view specs - they're not relevant to the new code in their current form and don't seem to merit updating.
|
|
|
|
| |
Fixes #1101.
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| |
| | |
This was disabled for hidden requests as the download was by redirect,
allowing people who have not been authenticated to conceivably access
the download. We'll be moving to send_file instead, so can restore it.
|
| |
| |
| |
| |
| | |
Make it an integration spec so we don't need to touch the internals so
much.
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Add another spec for the same behaviour when an incoming message is
hidden.
|
| | |
|
| |
| |
| |
| | |
Remove expectation of pdf contents - we're looking at the raw file.
|
| | |
|
| |
| |
| |
| | |
They refer to the case where the request itself is hidden.
|
|/ |
|
|\ |
|
| |
| |
| |
| | |
the URL) off by default in model, controller, and helper tests. This means we can supply the locale as a param. Turn it on specifically for a couple of controller tests that test routing, and change other url localization tests into integration tests.
|
|\ \
| |/
|/|
| |
| |
| |
| | |
'openaustralia_github/tests_set_described_state' into rails-3-develop
Conflicts:
spec/models/info_request_spec.rb
|
| | |
|