Two quick, easy rules to getting help:
- Questions concerning problems with code you've written must describe the specific problem and include valid code to reproduce it. See http://SSCCE.org for guidance.
- Questions asking for code must demonstrate a minimal understanding of the problem being solved. Include attempted solutions, why they didn't work, and the expected results. See also: http://goo.gl/9nI4eq.
Please provide the following information in a new Gist:
- The code that you think is causing your problem.
- Please split multiple files up in a new Gist using the "Add Another File" feature.
- The error message and the complete "Full Trace" output from your application.
- Any relevant output from your logs (in log/development.log, usually)
- Lacking any error message or stacktrace, a complete description of the problem.
- Steps to reproduce the problem.
Don't know how to use Gist? Follow this guide.
Without these three things, we are unable to help you with your problem.
Bonus points: create a repository on GitHub that contains code that we can clone and run to reproduce the issue.
If your problem is to do with routes, please show us the complete contents of config/routes.rb, as well as the related controllers and view templates of your problem.
Active Admin, Active Scaffold, Rails Admin and their ilk are the scourges of the Devil and should be avoided at all costs. Designing your own admin interface will give you precisely what you want, with none of the mysterious behaviour that Active Admin or Active Scaffold provides.
Using rails g scaffold to write your entire application will produce a lot of code that just isn't necessary. Please generate controllers and models with their appropriate generators and fill them out as necessary.