[PATCH] shuffle application load order, load routes/observers last

+1

Looks reasonable. "Initializer" seems like it should happen before other stuff, like observers - even if it breaks somebody somewhere.

+1

Quoting my reply in the ML:

Instantiating an observer triggers loading its observed model class to register it, and I think the model class should be allowed to expect full initialization. Particularly we are concerned here with extensions to Active Record by plugins or initializers.

If you happen to be creating observed models in config/initializers you can still manually instantiate the singleton. So there's some price here, but you still have a simple solution, and I believe the use cases above are far more important.

Good docs, except that observers are loaded between plugins and app initializers.

(In [8787]) Reshuffle load order so that routes and observers are initialized after plugins and app initializers. Closes #10980 [rick, fxn]

Oh yes, sorry for the lapse, thank you for the fix.