I found a bug with they way the filters and $m->flush_buffer work. Version 1.30-1.33 had a bug that made $m->flush_buffer or autoflush not work at all if there was a filter section upstream. This was fixed in version 1.33.
However, I think this introduced a new bug, because in any version >= 1.33, the filter section is completely bypassed when autoflush is on or you call $m->flush_buffer. In my case, the filter section is in the topmost autohandler and I am using $m->flush_buffer is a component in a subdirectory that is 3 levels deep. Someone else reported this back in November: http://article.gmane.org/gmane.comp.web.mason.user/9459/ But, there were no replies and it looks like nothing came of it. I also don't see anything in the current bug list. Can a mason developer check this out? Thanks, Bryan Opfer ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Mason-users mailing list Mason-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mason-users
