> I see. When you say 1.2 _doesn't_ reload, what do you mean? Why does > _not_ reloading make Radiant work, but reloading breaks it?
During initialization, the Behaviour class is loaded and all the subclasses also get loaded. When a subclass is loaded, it registers itself with the parent class. What I think is happening is that the Behaviour class is getting reloaded (and thus clearing the references to the subclasses), but the subclasses are not reloaded, and thus don't register themselves. > Either way, thanks for answering, I feel better knowing > someone else has > come across this issue. I haven't come across your specific issue, but knowing the radiant and rails codebases, I'm making a guess as to a possible cause. If it's not working after switching to production and your production.rb has cache_classes set to true, then I don't think I know what your issue is. Also, the mental branch doesn't have behaviours, it has extensions, so the answer to 'Do your behaviors load correctly under Mental and Rails 1.2.1?' is no, but my extensions do. Have a look through the mailing list archive for more information about porting behaviours to extensions if you want to go down that path. Dan. _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
