-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"No route matches" for model named "News" #89
Comments
Can you do a |
(Sorry for the formatting...) |
Yep, the same for me. Everything works as expected except "News" resource, and I have all necessary routes. |
guess this is what you are looking for http://stackoverflow.com/questions/5290142/rails-and-module-scoped-routes-strange-behaviour |
issue still doesn't solve and the problem from active_admin itself not from rails because I create a rails project as a test and create news scaffold and It worked. but it didn't work in active_admin |
I am also having issues with this. I have a model named Series and I get a similar error message. |
See issue #369. |
Thanks pcreux. I hope will be fixed soon |
I got this error as well and all I needed to do was to restart the server. |
Using ActiveAdmin for a model called "News" seems to not work properly. After creating a resource for the News model, visiting any ActiveAdmin page will raise an error such as this:
However, when renaming the resource with :as (to "Post", "Gherkin", or anything else that can be pluralized), the model and all views behave as expected.
The same error occurs when renaming any other model to "News" using :as, for example:
The text was updated successfully, but these errors were encountered: