routes

I have a problem injecting resolve parameters from the routing into the controller. I'm setting the resolve value to an object {name: 'Banner', slug: 'banner'} , but I get an error. App.js var app = angular.module('CMS', ['fields', 'ngRoute']); app.controller('ModuleController', ['$http', 'properties', function($http, properties) { var module = this; module.properties = properties; if (module.properties.slug.length) { $http.get(module.properties.slug + '.php').success(function(data) { module.list = data; }); } } ]); app.controller('HomeController', function() {}); app.config(function(

I'm trying to change the will_paginate links from the format of /list?page=1 to /list/page/1 . I have the routes setup right for this, but will_paginate is using the query string in links rather than my pretty URL style. How to tell it otherwise? I'm using will_paginate 2.3.16 and Rails 2.3.14 . will_paginate uses the url_for helper. If you define routes containing the parameters it uses, it should generate pretty urls. map.connect '/lists/page/:page', :controller => 'lists', :action => 'index' Please make sure, you define this route above any routes that could also match your controller

I'm trying to create a route with Sinatra that only accepts POST with an Content-type: application/json without success. My approach is as follows: post '/dogs', :provides => :json do # returns here a json response end Testing with curl, I have seen that :provides => :json configures the route to respond with an Content-Type: application/json . That's right because I want also to respond with a JSON message to the POST request but I really need that this route only respond to POST requests with a Content-Type: application/json and not, for example, to others (e.g. Content-Type: application/xml

I've got an existing codebase that I'm attempting to upgrade from Rails 3.2 to Rails 4.0 I have controller called assets_controller with a 'create' method and I have a an entry in my routes file: resources :assets Using jQuery for ajax on the front end, if I send a post request to '/assets' from a browser, I get 405 (Method Not Allowed): $.ajax({method: 'POST', data: asset, url: '/assets' }); This worked just fine in Rails 3, and I can't seem to figure out what the issue is. Updates: Heres a simplified version of my controller: class AssetsController < ApplicationController skip_before_filter

I was updating my Laravel 3 app to Laravel 4 when I hit this problem... Routes I have tried: Route::get('backend/login', 'backend/UserController@login'); Route::get('backend/login', 'backend.UserController@login'); I had a similar issue just a few hours ago and had to play a little bit with it to have it working. Routes: Route::group(array('prefix' => 'admin'), function() { Route::resource('/', 'admin\DashboardController'); }); In "controllers/admin" i put the DashboardController: namespace admin; use Illuminate\Support\Facades\View; class DashboardController extends \BaseController { public

I wasn't able to find anything here or elsewhere that covered both restricting a resource's routes and adding additional non-RESTful routes in Rails 3. It's probably very simple but every example or explanation I've come across addresses just one case not both at the same time. Here's an example of what I've been doing in Rails 2: map.resources :sessions, :only => [:new, :create, :destroy], :member => {:recovery => :get} Pretty straightforward, we only want 3 of the 7 RESTful routes because the others don't make any sense for this resource, but we also want to add another route which is used