Pablo Brasero

Good thinking. To add to the use cases, here's a generalisation of your second one: * Some fields should only be editable only when the application is in a certain...

Sorry for the delay. This is a difficult problem that requires some dedicated thinking... Starting with your _notate bene_: 1. I agree that `page.fields` would be more descriptive. I have...

See https://github.com/thoughtbot/administrate/issues/1949 for another use case: loading fields depending on the application domain name.

@januszm - Would it work for you if you use the i18n translation files? You should be able to provide any labels that you want with that. Admittedly there are...

I'm not sure if this will work, but you can use any sort of `call`-able as the `collection` option, for example a lambda. This should allow for more dynamic collections,...

I'd prefer two partials: one for the header and another for the record rows, both used from `app/views/administrate/application/_collection.html.erb`. At least for now, as it will be more forward-compatible. In the...

@audyaver - In your specific case, I think that Administrate is not the problem. Your route definition looks wrong. You have this: ``` get 'admin/foo/:id/solr_index', to: 'foo#solr_index', as: 'admin_foo_solr_index_path' ```...

Re: this issue in general, there's some progress at https://github.com/thoughtbot/administrate/pull/1998, which implements new partials to help with this.

I agree. I can't think of a reason why namespaces should be singularized. Would someone be up for a PR?

@DevS1993 - Yes, I'll be happy to look at a PR for this.