aboutsummaryrefslogtreecommitdiffstats
path: root/spec/controllers
Commit message (Collapse)AuthorAgeLines
* Don't redirect to signin on expiration of a non remember-me sessionLouise Crow2015-04-23-1/+0
| | | | In practice, it's just confusing if you've been away from the site.
* Limit the number of pages of requests shown for public bodies.Louise Crow2015-04-07-0/+7
| | | | Needs to be restored as part of https://github.com/mysociety/alaveteli/issues/2137.
* Merge branch 'add-frontpage-autodetect-feed' into rails-3-developLouise Crow2015-03-26-0/+8
|\
| * Add an autodetect feed for the frontpage list of requestsLouise Crow2015-03-19-0/+8
| | | | | | | | Closes Â#434.
* | Fix translating Public Body HeadingsGareth Rees2015-03-18-106/+411
| | | | | | | | | | Fixes submission of form containing both existing and new translations
* | Fix translating Public Body CategoriesGareth Rees2015-03-18-136/+564
| |
* | Fix translating Public BodiesGareth Rees2015-03-18-200/+345
|/
* Fully prevent banned users editing their photoGareth Rees2015-02-24-0/+28
|
* Fully prevent banned users editing their about_meGareth Rees2015-02-24-0/+29
|
* Merge branch 'hotfix/0.20.0.7' into rails-3-developLouise Crow2015-02-05-0/+6
|\ | | | | | | | | Conflicts: config/initializers/alaveteli.rb
| * Do not allow requests for search results after the first 500Louise Crow2015-02-03-0/+6
| | | | | | | | | | | | | | The pages for these search results are extremely slow to load. This is not an ideal solution by any means. Really we want to dig into why high offsets are so slow, and whether there's anything we can do to fix that.
* | Merge branch 'hotfix/0.20.0.6' into rails-3-developLouise Crow2015-02-05-12/+142
|\ \ | | | | | | | | | | | | Conflicts: spec/models/public_body_spec.rb
| * | Build available locales in the controllerGareth Rees2015-02-03-0/+15
| | | | | | | | | | | | | | | Removes logic from views and obsoletes AdminPublicBodyHelper#public_body_form_object
| * | Fix submission of form containing both existing and new translationsLouise Crow2015-02-03-41/+50
| | |
| * | Add AdminPublicBodyController#update specsGareth Rees2015-02-03-0/+106
| |/ | | | | | | | | | | | | Covers core functionality. Could do with extracting multiple assertions in to individual specs. Strange that you need to call `reload` on the PublicBody instance when testing “updates an existing translation and adds a third translation”
* | Merge branch '2051-back-to-search' into rails-3-developGareth Rees2015-01-13-0/+45
|\ \
| * | Add a “Back to search results” linkGareth Rees2015-01-13-0/+45
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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/
* | | Use a partial to render batch sent messageGareth Rees2015-01-13-3/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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)
* | | Use a partial to render request sent messageGareth Rees2015-01-13-0/+10
|/ /
* | Merge branch 'hotfix/0.20.0.2' into rails-3-developLouise Crow2015-01-07-0/+24
|\|
| * Sanitize the blog contents0.20.0.2Louise Crow2014-12-22-0/+12
| |
| * Sanitize the contents of HTML attachments before displayLouise Crow2014-12-22-0/+12
| |
* | Remove focus tagLouise Crow2014-12-23-1/+1
| |
* | Merge branch 'restful-admin-routes' into rails-3-developLouise Crow2014-12-18-301/+511
|\ \
| * | Don't raise internal error when handling non-user or request rulesLouise Crow2014-12-18-43/+107
| | | | | | | | | | | | | | | | | | | | | Handle attempts to edit or destroy global or public body censor rules with a notice and a redirect. Closes #2009
| * | RESTful routing for admin censor rule actionsLouise Crow2014-12-18-213/+249
| | |
| * | RESTful routing for admin track actionsLouise Crow2014-12-18-4/+3
| | |
| * | Use RESTful routes for CRUD admin user actionsLouise Crow2014-12-18-5/+5
| | |
| * | Move admin incoming message actions to use RESTful routes.Louise Crow2014-12-18-5/+5
| | | | | | | | | | | | | | | So data changing actions require a POST and can be protected against CSRF.
| * | Move change request actions to use RESTful routes.Louise Crow2014-12-18-4/+6
| | |
| * | Move edit and update to RESTful routingLouise Crow2014-12-18-1/+1
| | |
| * | Move new action to use RESTful routing.Louise Crow2014-12-18-1/+1
| | |
| * | Use RESTful routing for indexLouise Crow2014-12-18-2/+2
| | |
| * | Make downloading a raw email a RESTful routeLouise Crow2014-12-18-3/+19
| | |
| * | Make marking an event as a clarification a RESTful routeLouise Crow2014-12-18-0/+41
| | |
| * | Make hide a RESTful action accessed via POSTLouise Crow2014-12-12-3/+3
| | |
| * | Make show_raw_email a RESTful action via GETLouise Crow2014-12-12-28/+14
| | | | | | | | | | | | | | | Move specs that involve receiving email and then viewing the interface to be integration specs, which is what they really are.
| * | RESTful routing for editing and updating commentsLouise Crow2014-12-12-0/+66
| | |
| * | Use RESTful routing for destroy actionLouise Crow2014-12-12-2/+2
| | |
| * | Use RESTful routing for index and show actionsLouise Crow2014-12-12-2/+2
| | |
* | | Merge branch 'admin-public-holiday-interface' into rails-3-developLouise Crow2014-12-18-0/+265
|\ \ \
| * | | Allow import of holidays from feed or built-in suggestionsLouise Crow2014-12-15-1/+75
| | | |
| * | | Add some inline editingLouise Crow2014-12-15-7/+31
| | | |
| * | | Add create actionLouise Crow2014-12-15-0/+39
| | | |
| * | | Add new actionLouise Crow2014-12-15-0/+15
| | | |
| * | | Add basic destroy action.Louise Crow2014-12-15-0/+25
| | | |
| * | | Add basic update action.Louise Crow2014-12-15-2/+38
| | | |
| * | | Add basic edit actionLouise Crow2014-12-15-1/+21
| | | |
| * | | Add index method for listing existing holidaysLouise Crow2014-12-15-0/+32
| | | |
* | | | Refactor the application of masks and censor rules to messages.Louise Crow2014-12-15-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
generated by cgit v1.2.3 (git 2.25.1) at 2025-07-21 20:00:50 +0000