aboutsummaryrefslogtreecommitdiffstats
path: root/config/routes.rb
Commit message (Collapse)AuthorAgeLines
* Merge branch 'restful-admin-routes' into rails-3-developLouise Crow2014-12-18-70/+89
|\
| * RESTful routing for admin censor rule actionsLouise Crow2014-12-18-22/+11
| |
| * RESTful routing for admin track actionsLouise Crow2014-12-18-2/+5
| |
| * Restrict modifying comments' visibility to a POST actionLouise Crow2014-12-18-1/+1
| |
| * Make clearing a profile photo a post-restricted actionLouise Crow2014-12-18-2/+1
| |
| * Make logging in as a user a POST-constrained action.Louise Crow2014-12-18-1/+2
| |
| * RESTful route for destroying a trackLouise Crow2014-12-18-1/+1
| |
| * RESTful route for clearing a bounce messageLouise Crow2014-12-18-1/+1
| |
| * RESTful route for bounce messageLouise Crow2014-12-18-1/+1
| |
| * Use RESTful route for banned user listLouise Crow2014-12-18-2/+3
| |
| * Use RESTful routes for CRUD admin user actionsLouise Crow2014-12-18-5/+5
| |
| * Move outgoing message admin actions to RESTful model.Louise Crow2014-12-18-4/+7
| |
| * Move admin incoming message actions to use RESTful routes.Louise Crow2014-12-18-4/+7
| | | | | | | | | | 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-2/+5
| |
| * Use RESTful routing for importing the public bodies csv fileLouise Crow2014-12-18-1/+2
| |
| * RESTful routing for missing_scheme and mass_tag_addLouise Crow2014-12-18-2/+2
| |
| * Move destroy action to RESTful routingLouise Crow2014-12-18-2/+0
| |
| * Move create to RESTful routingLouise Crow2014-12-18-2/+1
| |
| * Move edit and update to RESTful routingLouise Crow2014-12-18-3/+1
| |
| * Move new action to use RESTful routing.Louise Crow2014-12-18-2/+1
| |
| * Move show method to use RESTful routingLouise Crow2014-12-18-2/+1
| |
| * Use RESTful routing for indexLouise Crow2014-12-18-2/+6
| |
| * Make downloading a raw email a RESTful routeLouise Crow2014-12-18-1/+1
| |
| * Make marking an event as a clarification a RESTful routeLouise Crow2014-12-18-1/+7
| |
| * Make hide a RESTful action accessed via POSTLouise Crow2014-12-12-1/+1
| |
| * Make show_raw_email a RESTful action via GETLouise Crow2014-12-12-1/+8
| | | | | | | | | | 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.Louise Crow2014-12-12-2/+0
| |
| * RESTful routing for editing and updating commentsLouise Crow2014-12-12-2/+8
| |
| * Move generate_upload_url action to be RESTfulLouise Crow2014-12-12-1/+1
| |
| * Make move a RESTful actionLouise Crow2014-12-12-1/+1
| |
| * Use RESTful routing for destroy actionLouise Crow2014-12-12-1/+0
| |
| * Use RESTful routing for resend actionLouise Crow2014-12-12-1/+1
| |
| * Use RESTful routing for index and show actionsLouise Crow2014-12-12-3/+6
| |
* | Add routes for admin of holidaysLouise Crow2014-12-15-0/+15
|/
* Add extra censor rule routesGareth Rees2014-11-19-0/+18
| | | | | | | | | | | | | | | Adds specific routes for creating censor rules associated with an info request or user. Creates: POST /admin/info_requests/:info_request_id/censor_rules(.:format) GET /admin/info_requests/:info_request_id/censor_rules/new(.:format) POST /admin/users/:user_id/censor_rules(.:format) GET /admin/users/:user_id/censor_rules/new(.:format) Using these routes prevents the ID of the association object being lost when re-rendering the form on an unsuccessful persistence attempt.
* Redirect /help to /help/aboutGareth Rees2014-11-05-0/+1
| | | | Shouldn't really 404 on an important/accessible URL
* Merge branch 'spam_address_routing' into rails-3-developGareth Rees2014-10-14-1/+1
|\
| * Add admin prefix to spam_addresses resourcesGareth Rees2014-10-10-1/+1
| |
* | Merge branch 'issues/222-category-editing-add-order-interface' into ↵Louise Crow2014-10-14-0/+18
|\ \ | |/ |/| | | rails-3-develop
| * fixup! Use RESTful routing.Louise Crow2014-10-09-2/+2
| |
| * Use RESTful routing.Louise Crow2014-09-26-13/+12
| |
| * fixup! Basic category admin screenLouise Crow2014-09-25-1/+0
| |
| * Add actions for reordering public body headings and categories.Louise Crow2014-09-22-0/+2
| |
| * Basic category admin screenlizconlan2014-09-22-0/+18
| |
* | Merge branch 'issues/1827-healthcheck' into rails-3-developGareth Rees2014-09-30-0/+2
|\ \
| * | Add an action to run the checksGareth Rees2014-09-25-0/+2
| |/
* / Redirect GET signup to signinhotfix/0.19.0.6Gareth Rees2014-09-24-1/+2
|/ | | | | | | | | | | | | | | After allowing only POST requests to signup in 316b1e: > What I think will happen at least sometimes is that someone will enter > information in the signup form, submit it via a post request, and end > up on the URL /profile/signup, at which point they want to refresh and > start again, at which point they hit the URL in the address bar to do > so. Currently that would mean they get a 404. I wonder about adding > another route match '/profile/sign_up' => 'user#signin', :as => > :signin, :via => :get to handle this case. That would mean that a get > request to profile/signup renders the empty form. > > – https://github.com/mysociety/alaveteli/pull/1850#issuecomment-55387700
* New API method for updating request statelizconlan2014-07-28-0/+1
|
* Rename XXX comments with TODO:Gareth Rees2014-06-10-2/+2
| | | | Picks these up in `rake notes` and adds semantic meaning
* Add AdminSpamAddressesController and UIGareth Rees2014-03-28-0/+8
|
generated by cgit v1.2.3 (git 2.25.1) at 2025-09-06 08:20:50 +0000