Sean Linsley

It's possible that #1935 will fix this, though I haven't checked.

The solution probably lies deep in Rails' autoloading code :octocat:

Disconnecting this from the Rails reloading, I can reproduce by simply calling [`ActiveAdmin.unload!`](https://github.com/activeadmin/activeadmin/blob/f7483e3b8fcd74437b03c18fb658dac62a9fc62e/lib/active_admin/application.rb#L197) ``` ruby ObjectSpace.each_object(ActiveAdmin::Resource).count => 17 ActiveAdmin.unload! ObjectSpace.each_object(ActiveAdmin::Resource).count => 17 ids = ObjectSpace.each_object(ActiveAdmin::Resource).map{ |r| r.controller.object_id } ids.count =>...

If someone can get a PR merged on Formtastic's side, sure, but Active Admin has plenty of custom form code.

Yep, it works just fine. Some references: - http://www.activeadmin.info/docs/0-installation.html#will_paginate_compatibility - http://stackoverflow.com/questions/13723897/undefined-method-page-for-activerecordrelation0xaadc8d4 Though it should probably be added to the Kaminari docs as well

It may just be the nested namespace that's causing the issue. Can you reproduce with simple Ruby classes?

https://www.owasp.org/index.php/Cross-Site_Request_Forgery_(CSRF)_Prevention_Cheat_Sheet#Checking_the_Referer_Header >Checking the Referer is a commonly used method of preventing CSRF on embedded network devices because it does not require any per-user state. This makes Referer a useful method...

@ssokolow could you link to such browser extensions? Is there data to suggest that they block the referer header indiscriminately on any website, even when navigating from page to page...

FWIW the above-linked Smart Referer browser extension only removes the header when navigating cross-domain. From my point of view, if you have corporate customers you can either afford the budget...

I'd be happy to help with this @SergioBenitez