| Commit message (Collapse) | Author | Age | Lines |
|
|
|
|
|
| |
Since https://github.com/mysociety/alaveteli/commit/80ad2d4c31075ffc994e8c48ea25e6e3c486c364
no themes have been loaded by tests unless explicitly specified, so I think it's safe to
remove the code added in https://github.com/mysociety/alaveteli/commit/3dfc53f6b82b3c5da79a4c710d45b859f61f4f5f
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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)
|
|/ |
|
|\ |
|
| | |
|
|\ \ |
|
| | | |
|
| |/
| |
| |
| |
| |
| |
| | |
Grepping the git logs didn’t bring up a good reason for this to be
excluded. Seems like it came along after the app was initially created
so it never got fully added for fear of regressions. The specs pass for this
commit.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |
|
|
|
|
|
|
|
| |
User testing highlighted that it was easy to mistake "View Requests" for
a Facebook-style wall rather than the list of all requests. [1]
[1] https://github.com/mysociety/alaveteli/issues/1505
|
|
|
|
| |
Picks these up in `rake notes` and adds semantic meaning
|
|
|
|
|
| |
Was switched to && for style but in fact for control flow, and is
what we want.
|
|
|
|
| |
Fixes #1448.
|
| |
|
| |
|
|
|
|
|
|
| |
Calling simple_date threw an exception as it uses a helper internally.
Only LinkToHelper is included in to the controller, so the underlying
helper was not available.
|
|\
| |
| |
| |
| |
| | |
Conflicts:
config/general.yml-example
spec/factories.rb
|
| |
| |
| |
| |
| | |
Otherwise they get marked as fuzzy in .po files and lose their existing
translations.
|
| | |
|
| |
| |
| |
| | |
We're going to want to actually create and send the requests later.
|
| | |
|
| |
| |
| |
| | |
Add or remove all buttons, ajax search as you type.
|
| |
| |
| |
| |
| | |
Seems like you have to specify a limit with xapian. We'll probably want
to document the limit somewhere on this page.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
They're not finding by the existing object, they're finding an existing
object.
|
| |
| |
| |
| |
| | |
Create the batch and associate new requests with it, send the outgoing
messages, and redirect to a page for the new batch.
|
| |
| |
| |
| |
| |
| | |
This duplicates what's done in the new action, but I can't currently
think of a way of sharing functionality that doesn't seem overly complex
and/or risky.
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
It doesn't make logical sense that they would. However I am preserving
the ability to make batch requests as a separate thing from not having a
daily limit - I think batch sending requires a (perhaps marginally)
bigger level of trust.
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Add validation, preview as in single request creation. Add comments
noting further work to be done in this action.
|
| |
| |
| |
| | |
Reuse it for the batch request page.
|
| |
| |
| |
| |
| |
| | |
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.
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is involved with the construction of meaningful xapian queries with
respect to InfoRequestEvents. This commit also removes the
get_tags_from_params method, which presumably was targeted at
PublicBodies, but doesn't seem to actually be used anywhere.
XapianQueries is used to extend InfoRequestEvent in order to prevent
InfoRequestEvent becoming too unwieldy and to preserve the association
between these methods.
|
|/
|
| |
It is a better solution to forma sentenses in po file, therefore the substring in variable added to _() as a parameter.
|
|\
| |
| |
| |
| |
| |
| | |
rails-3-develop
Conflicts:
Gemfile.lock
|