…(rendered in Devise specific views such as login and register)
…users to use an rc, but added the rails 3.0.6.rc version to the Gemfile so we can develop and test against it
…n just say "home"
…in the source)
month to prevent miscalculated month decrements/increments.
…t and example.org are the sole 2nd level domain names reserved for sample configurations (see http://tools.ietf.org/html/rfc2606).
entities are related via team->division->league. The dummy application contained within test suite is about to be used as demo.railsadmin.org test application so I'm trying to tidy it up a bit.
…dcoding them, fixes #266
…methods on models" This reverts commit fa48e16. Conflicts: app/controllers/rails_admin/main_controller.rb spec/dummy_app/config/initializers/rails_admin.rb
…ttp://goo.gl/H1mLV 1. Don't generate urls with :: in them, that's not legal (see http://www.faqs.org/rfcs/rfc2396.html Section 2.2, 2.3). Use ~ instead. This is still hacky. Ideally we should treat namespaces as proper URL components, e.g. /cms/basic_page/5/edit, but that would have been a bigger change. 2. Rails will automatically change model names containing "::" into "_" when generating input field names. A recent commit started using Rails's native form helpers to generate input field names which completely broke namespaced model support. This has been patched by gsub'ing "~" -> "_" in incoming parameters. This is a stop gap measure pending a wider resolution of the namespace issue. This fixes # 3. Added test support for namespaced models which was lacking and probably the reason why previous support regressed.
… Labels are no longer supported in sections, only at the model level." This reverts commit 470408c. This was causing some confusion, since version 0.0.1 was never actually released as a gem on rubygems.org.