Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

Content Pluralization Route

#89

The plural of "content" should be "content", at least for routing sake. I don't mind have the contents controller, but I feel silly typing in /contents/new to add a piece of content.

Reported by Brian Michalski · June 6th, 2010 @ 12:41 PM

State: resolved
Milestone: none
Assigned to: nobody

Activity

  1. Brian Michalski
    Brian Michalski

    I could have sworn I did this one already [ab7a1c1d4c35e3fc39161c82a06754034ae1cc3b] but it doesn't work anymore. Maybe it was a beta1->beta3 issue, or I was dreaming...

    June 6th, 2010 @ 02:52 PM

  2. Brian Michalski
    Brian Michalski
    • State changed from new to open

    I think I've got a fix for this, but I'm having trouble generating a test so we can catch it if it happens again.

    -  resources :contents, :as => "content"
+  resources :contents, :path => "content"

    June 6th, 2010 @ 10:58 PM

  3. Brian Michalski
    Brian Michalski
    • State changed from open to resolved

    (from [9934b19dc5c898a24752da5c7cda5b406085bede]) Fixing content route plurization. Found a way to test pending Rails 3 RC [#89 Content Pluralization Route state:resolved] http://github.com/wtg/concerto/commit/9934b19dc5c898a24752da5c7cda5...

    June 8th, 2010 @ 01:31 PM

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.