I found that just the self.included in Export wasn't being executed, I think it works in the main plugin.
After a few hours I gave up and integrated export functionality into a branch of active scaffold. On May 25, 11:12 am, "Sergio Cambra .:: entreCables S.L. ::." <[email protected]> wrote: > On Lunes, 25 de Mayo de 2009 10:50:34 Ed W escribió: > > > > > Sergio Cambra .:: entreCables S.L. ::. wrote: > > > On Domingo, 24 de Mayo de 2009 20:02:56 usted escribió: > > > > Sorry to pester but do either of you see this with AS on your setup? > > > > > I've wasted a whole day trying to figure it out and it would at least > > > > help to know that it's not just my configuration? > > > > > Essentially none of the setup code for the various actions is running > > > > for me - this mainly breaks the before_filters > > > > > Thanks > > > > I think before_filters must raise an exception, render a view or > > > redirect to halt normal execution. I think it was changed in rails 2, > > > we should fix that filters in ActiveScaffold, I had forgot it (I > > > changed it in some projects before I had write access to repository) > > > Actually I think it's worse than that > > > Deliberately introduce some code into the various actions > > "self.included" function and you will see that it doesn't execute? I > > introduced some deliberate syntax errors just to be sure and nothing > > happened... > > It's working here. I have added a Rails.logger.debug line in > create_authorized? and is executed. I override create_authorized? in a > controller and it was executed. > > > > > > > In my case I noticed it because I was trying to use this function in my > > plugin to hook into the view paths and eventually it dawned on me it > > wasn't my code which was wrong, but that the code wasn't running!! > > > Can you also review my other email about how to more neatly integrate > > view paths from plugins? > > > I think restructuring the activescaffold init function to actually > > initialise @active_scaffold_paths (rather than doing it in the getter) > > and then provide a simple setter function should solve this and some > > related problems. The rest of the AS code can then use this if it needs > > to. > > > I can provide a patch, but it's really a one liner? > > I think the best way it's to add an method, add_active_scaffold_path, to add > view paths. All paths added by plugins usually should go between > active_scaffold_overrides and active_scaffold_frontends, so it will be enough > with that method most time. > > -- > Sergio Cambra .:: entreCables S.L. ::. > Nicolás Guillén 6, locales 2 y 3. 50.018 Zaragoza > T) 902 021 404 F) 976 52 98 07 E) [email protected] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "ActiveScaffold : Ruby on Rails plugin" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/activescaffold?hl=en -~----------~----~----~----~------~----~------~--~---
