Pablo Brasero

I agree that the current solution is not ideal. For the moment, the recommended workaround is to override the `index` action of your controller so that you can implement your...

Thank you for the feedback. The whole i18n setup needs some rethinking and I'm not sure about making small changes now as we may want to go in a different...

Hello @lake-effect. Thank you for the thorough description. This is indeed an issue we were not aware of, and it should be fixed. To add insult to injury, our example...

@lake-effect - Would you be able to paste here your `has_many` and `belongs_to` declarations in your models? I'm checking that I'm not missing anything with my fix.

Thank you for the additional info :-) One thing I'm noticing is that your associations are defined with `class_name`, `primary_key` and `foreign_key`, the same settings that work for you on...

Do you mean that the original `belongs_to` association in the ActiveRecord model is also using your workaround? If that's the case, then it sounds to me like the problem is...

I'd say let's wait for #1973 first and then let's see where my branch is when it arrives, and if we can use my branch to simplify your spec.

This is the branch that reorganises the example app: https://github.com/thoughtbot/administrate/pull/1998. When it's merged, we can revisit this PR.

I noticed this: `@attribute=:coates` in the text you paste. Could it be that there is a typo in your `SHOW_PAGE_ATTRIBUTES`, and you are listing coats as "coates"? If this is...

Thank you for the report @pjmartorell. It looks like we could have used a feature spec there. Do you think you'd be able to provide a PR?