I have installed masterview into the vendor directory and when I start up mongrel I get: Initializing MasterView configuration (2007-04-02 13:18) Program name = script/server Using default admin_auth mixin for MasterView admin (local requests only) Adding MasterView AdminPages controller directories to controller_paths MasterView Admin pages enabled Failure to parse template. Exception=undefined method `progress'' for #<MasterView::TemplateProcessing::SAXParserListener:0x224d5f8> Failure to parse template. Exception=undefined method `progress'' for #<MasterView::TemplateProcessing::SAXParserListener:0x248661c> Failure to parse template. Exception=undefined method `progress'' for #<MasterView::TemplateProcessing::SAXParserListener:0x240b0d4> Failure to parse template. Exception=undefined method `progress'' for #<MasterView::TemplateProcessing::SAXParserListener:0x23c21e0> Failure to parse template. Exception=undefined method `progress'' for #<MasterView::TemplateProcessing::SAXParserListener:0x23acbec> Failure to parse template. Exception=undefined method `progress'' for #<MasterView::TemplateProcessing::SAXParserListener:0x2391234> Adding hook to allow MasterView to check for templates that have changed when processing a request Adding hooks to enable Rails to read erb directly from MasterView MasterView plugin initialized - Version 0.3.2 ** Rails loaded. Followed by the rest of the normal rails startup output. When I try to hit http://localhost:3000/masterview or other url''s that are masterview generated content I get the same error again Failure to parse template. Exception=undefined method `progress'' for #<MasterView::TemplateProcessing::SAXParserListener:0x3718bf8> Any idea on what I might have done wrong? I''m on Rails 1.2. David Koontz
On 4/2/07, David Koontz <david at koontzfamily.org> wrote:> > I have installed masterview into the vendor directory and when I start > up mongrel I get: > > Initializing MasterView configuration (2007-04-02 13:18) > Program name = script/server > Using default admin_auth mixin for MasterView admin (local requests only) > Adding MasterView AdminPages controller directories to controller_paths > MasterView Admin pages enabled > Failure to parse template. Exception=undefined method `progress'' for > #<MasterView::TemplateProcessing::SAXParserListener:0x224d5f8> > Failure to parse template. Exception=undefined method `progress'' for > #<MasterView::TemplateProcessing::SAXParserListener:0x248661c> > Failure to parse template. Exception=undefined method `progress'' for > #<MasterView::TemplateProcessing::SAXParserListener:0x240b0d4> > Failure to parse template. Exception=undefined method `progress'' for > #<MasterView::TemplateProcessing::SAXParserListener:0x23c21e0> > Failure to parse template. Exception=undefined method `progress'' for > #<MasterView::TemplateProcessing::SAXParserListener:0x23acbec> > Failure to parse template. Exception=undefined method `progress'' for > #<MasterView::TemplateProcessing::SAXParserListener:0x2391234> > Adding hook to allow MasterView to check for templates that have changed > when processing a request > Adding hooks to enable Rails to read erb directly from MasterView > MasterView plugin initialized - Version 0.3.2 > ** Rails loaded. > Followed by the rest of the normal rails startup output. > > When I try to hit http://localhost:3000/masterview or other url''s that > are masterview generated content I get the same error again > > Failure to parse template. Exception=undefined method `progress'' for > #<MasterView::TemplateProcessing::SAXParserListener:0x3718bf8> > > Any idea on what I might have done wrong? I''m on Rails 1.2. > >I don''t believe I have seen that error before, but I will take a look at the SAXParserListener code to see if I can determine what it is complaining about. Jeff -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/masterview-users/attachments/20070402/db69102b/attachment.html
On 4/2/07, David Koontz <david at koontzfamily.org> wrote:> > I have installed masterview into the vendor directory and when I start > up mongrel I get: > > Initializing MasterView configuration (2007-04-02 13:18) > Program name = script/server > Using default admin_auth mixin for MasterView admin (local requests only) > Adding MasterView AdminPages controller directories to controller_paths > MasterView Admin pages enabled > Failure to parse template. Exception=undefined method `progress'' for > #<MasterView::TemplateProcessing::SAXParserListener:0x224d5f8> > Failure to parse template. Exception=undefined method `progress'' for > #<MasterView::TemplateProcessing::SAXParserListener:0x248661c> > Failure to parse template. Exception=undefined method `progress'' for > #<MasterView::TemplateProcessing::SAXParserListener:0x240b0d4> > Failure to parse template. Exception=undefined method `progress'' for > #<MasterView::TemplateProcessing::SAXParserListener:0x23c21e0> > Failure to parse template. Exception=undefined method `progress'' for > #<MasterView::TemplateProcessing::SAXParserListener:0x23acbec> > Failure to parse template. Exception=undefined method `progress'' for > #<MasterView::TemplateProcessing::SAXParserListener:0x2391234> > Adding hook to allow MasterView to check for templates that have changed > when processing a request > Adding hooks to enable Rails to read erb directly from MasterView > MasterView plugin initialized - Version 0.3.2 > ** Rails loaded. > Followed by the rest of the normal rails startup output. > > When I try to hit http://localhost:3000/masterview or other url''s that > are masterview generated content I get the same error again > > Failure to parse template. Exception=undefined method `progress'' for > #<MasterView::TemplateProcessing::SAXParserListener:0x3718bf8> > > Any idea on what I might have done wrong? I''m on Rails 1.2. >I am guessing that possibly you may have REXML 3.1.6?? If you possibly have rexml 3.1.6 (I have only tested with up to 3.1.5) then maybe they have changed their interface some so they don''t support the progress method. Rexml 3.1.5 was broken with regards to parsing doctypes, so I fixed it and submitted a patch to them, but since I wasn''t sure when people would get the latest version and not sure what version the patch would go into (or when), I included a patched version of the parser which MasterView is using. It is possible that something in 3.1.6 changed the rexml interface such that this patched parser is now broken. (no longer supporting progress method). So what I need to do is to download 3.1.6 and see if I can reproduce the error. I can also verify whether they have applied the patch I submitted them and if so then my patched rexml would not be needed for 3.1.6+ I have to run now, but I will try to take a look tonight to see if that is the case. Jeff -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/masterview-users/attachments/20070402/de78ff08/attachment.html
Jeff - quick note on related but diff problem: one of my pet peeves is that our logging message when a template doesn''t parse correctly is thoroughly useful, in particular it doesn''t identify the name/path of the html file which isn''t valid html and causes our parser to barf. I''ll get in and fix that in the next day or so, as soon as I have a chance (unless you run across that as side effect of looking into this nstall/version problem...). I think you haven''t noticed that because you probably have tidy configured to preprocess your input templates (to clean up the bad markup you get from nvu?!), but I never run with that so anytime I mistype something masterview chokes in relatively mysterious ways. You can figure out during dev if you''re only working on a specific .html file and testing some changes, but in general case this is really bad. ~ Deb -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/masterview-users/attachments/20070402/6ec2889b/attachment.html
REXML::Version gives 3.1.3> On 4/2/07, *David Koontz* <david at koontzfamily.org > <mailto:david at koontzfamily.org>> wrote: > > I have installed masterview into the vendor directory and when I start > up mongrel I get: > > Initializing MasterView configuration (2007-04-02 13:18) > Program name = script/server > Using default admin_auth mixin for MasterView admin (local > requests only) > Adding MasterView AdminPages controller directories to > controller_paths > MasterView Admin pages enabled > Failure to parse template. Exception=undefined method `progress'' for > #<MasterView::TemplateProcessing::SAXParserListener:0x224d5f8> > Failure to parse template. Exception=undefined method `progress'' for > #<MasterView::TemplateProcessing::SAXParserListener:0x248661c> > Failure to parse template. Exception=undefined method `progress'' for > #<MasterView::TemplateProcessing::SAXParserListener:0x240b0d4> > Failure to parse template. Exception=undefined method `progress'' for > #<MasterView::TemplateProcessing::SAXParserListener:0x23c21e0> > Failure to parse template. Exception=undefined method `progress'' for > #<MasterView::TemplateProcessing::SAXParserListener:0x23acbec> > Failure to parse template. Exception=undefined method `progress'' for > #<MasterView::TemplateProcessing::SAXParserListener:0x2391234> > Adding hook to allow MasterView to check for templates that have > changed > when processing a request > Adding hooks to enable Rails to read erb directly from MasterView > MasterView plugin initialized - Version 0.3.2 > ** Rails loaded. > Followed by the rest of the normal rails startup output. > > When I try to hit http://localhost:3000/masterview > <http://localhost:3000/masterview> or other url''s that > are masterview generated content I get the same error again > > Failure to parse template. Exception=undefined method `progress'' for > #<MasterView::TemplateProcessing::SAXParserListener:0x3718bf8> > > Any idea on what I might have done wrong? I''m on Rails 1.2. > > > > I am guessing that possibly you may have REXML 3.1.6?? > > If you possibly have rexml 3.1.6 (I have only tested with up to 3.1.5) > then maybe they have changed their interface some so they don''t > support the progress method. Rexml 3.1.5 was broken with regards to > parsing doctypes, so I fixed it and submitted a patch to them, but > since I wasn''t sure when people would get the latest version and not > sure what version the patch would go into (or when), I included a > patched version of the parser which MasterView is using. > > It is possible that something in 3.1.6 changed the rexml interface > such that this patched parser is now broken. (no longer supporting > progress method). > > So what I need to do is to download 3.1.6 and see if I can reproduce > the error. I can also verify whether they have applied the patch I > submitted them and if so then my patched rexml would not be needed for > 3.1.6+ > > I have to run now, but I will try to take a look tonight to see if > that is the case. > > Jeff > ------------------------------------------------------------------------ > > _______________________________________________ > Masterview-users mailing list > Masterview-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/masterview-users
On 4/2/07, David Koontz <david at koontzfamily.org> wrote:> > REXML::Version gives 3.1.3 > > On 4/2/07, *David Koontz* <david at koontzfamily.org > > <mailto:david at koontzfamily.org>> wrote: > > > > I have installed masterview into the vendor directory and when I > start > > up mongrel I get: > > > > Initializing MasterView configuration (2007-04-02 13:18) > > Program name = script/server > > Using default admin_auth mixin for MasterView admin (local > > requests only) > > Adding MasterView AdminPages controller directories to > > controller_paths > > MasterView Admin pages enabled > > Failure to parse template. Exception=undefined method `progress'' for > > #<MasterView::TemplateProcessing::SAXParserListener:0x224d5f8> > > Failure to parse template. Exception=undefined method `progress'' for > > #<MasterView::TemplateProcessing::SAXParserListener:0x248661c> > > Failure to parse template. Exception=undefined method `progress'' for > > #<MasterView::TemplateProcessing::SAXParserListener:0x240b0d4> > > Failure to parse template. Exception=undefined method `progress'' for > > #<MasterView::TemplateProcessing::SAXParserListener:0x23c21e0> > > Failure to parse template. Exception=undefined method `progress'' for > > #<MasterView::TemplateProcessing::SAXParserListener:0x23acbec> > > Failure to parse template. Exception=undefined method `progress'' for > > #<MasterView::TemplateProcessing::SAXParserListener:0x2391234> > > Adding hook to allow MasterView to check for templates that have > > changed > > when processing a request > > Adding hooks to enable Rails to read erb directly from MasterView > > MasterView plugin initialized - Version 0.3.2 > > ** Rails loaded. > > Followed by the rest of the normal rails startup output. > > > > When I try to hit http://localhost:3000/masterview > > <http://localhost:3000/masterview> or other url''s that > > are masterview generated content I get the same error again > > > > Failure to parse template. Exception=undefined method `progress'' for > > #<MasterView::TemplateProcessing::SAXParserListener:0x3718bf8> > > > > Any idea on what I might have done wrong? I''m on Rails 1.2. > > >I believe I have found the issue. It is a result of the rexml version being older, the patched class uses an event progress which is not defined in 3.1.3. I am completing and testing a fix that checks the version of rexml before using the patched parser otherwise it will default to the original version (which might not handle doctypes properly but otherwise should work fine). Jeff -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/masterview-users/attachments/20070403/2dc4c1f2/attachment.html
On 4/2/07, David Koontz <david at koontzfamily.org> wrote:> > REXML::Version gives 3.1.3 > > On 4/2/07, *David Koontz* <david at koontzfamily.org > > <mailto:david at koontzfamily.org>> wrote: > > > > I have installed masterview into the vendor directory and when I > start > > up mongrel I get: > > > > Initializing MasterView configuration (2007-04-02 13:18) > > Program name = script/server > > Using default admin_auth mixin for MasterView admin (local > > requests only) > > Adding MasterView AdminPages controller directories to > > controller_paths > > MasterView Admin pages enabled > > Failure to parse template. Exception=undefined method `progress'' for > > #<MasterView::TemplateProcessing::SAXParserListener:0x224d5f8> > > Failure to parse template. Exception=undefined method `progress'' for > > #<MasterView::TemplateProcessing::SAXParserListener:0x248661c> > > Failure to parse template. Exception=undefined method `progress'' for > > #<MasterView::TemplateProcessing::SAXParserListener:0x240b0d4> > > Failure to parse template. Exception=undefined method `progress'' for > > #<MasterView::TemplateProcessing::SAXParserListener:0x23c21e0> > > Failure to parse template. Exception=undefined method `progress'' for > > #<MasterView::TemplateProcessing::SAXParserListener:0x23acbec> > > Failure to parse template. Exception=undefined method `progress'' for > > #<MasterView::TemplateProcessing::SAXParserListener:0x2391234> > > Adding hook to allow MasterView to check for templates that have > > changed > > when processing a request > > Adding hooks to enable Rails to read erb directly from MasterView > > MasterView plugin initialized - Version 0.3.2 > > ** Rails loaded. > > Followed by the rest of the normal rails startup output. > > > > When I try to hit http://localhost:3000/masterview > > <http://localhost:3000/masterview> or other url''s that > > are masterview generated content I get the same error again > > > > Failure to parse template. Exception=undefined method `progress'' for > > #<MasterView::TemplateProcessing::SAXParserListener:0x3718bf8> > > > > Any idea on what I might have done wrong? I''m on Rails 1.2. > > >Well David, I have good news and bad news. The good news is that I have updated MasterView in the trunk with a version that checks the REXML version before attempting to use the patched sax2parser. The patched parser works with 3.1.4 - 3.1.6 versions of REXML. According to REXML trac, supposedly REXML 3.1.7 will have my doctype patch in the core, so it will not be needed after that anyway. I have also made this patched parser configurable with a new config option. If you set config.use_original_rexml_sax2parser = true, then it will not use the patch regardless of the version otherwise it will load and use the patch if REXML 3.1.4 - 3.1.6. I have tested MasterView with all of these versions 3.1.4, 3.1.5, 3.1.6 (current). The bad news is that REXML 3.1.3 seems to have a broken sax2parser such that I get errors when trying to simply require it despite the fact that we aren''t loading the rexml patch. So it appears that MasterView won''t work with REXML 3.1.3. I put in a check for this now in startup and it throws an exception if one tries to use a version less than 3.1.4. 3.1.3 was released in 2004, so hopefully this will not be a problem for most people. I have checked all the code changes into svn in the trunk and will plan to do a gem build and release once Deb has had a chance to look at my changes. svn://rubyforge.org/var/svn/masterview/trunk/masterview I have updated the documentation to indicate that REXML version needs to be 3.1.4 or greater. Jeff -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/masterview-users/attachments/20070403/ad7a8b18/attachment.html
It''s not an issue for me to upgrade, I was using the MacPorts version of Ruby and assumed it was updating the standard libraries when it updated Ruby to 1.8.6. David> On 4/2/07, *David Koontz* <david at koontzfamily.org > <mailto:david at koontzfamily.org>> wrote: > > REXML::Version gives 3.1.3 > > On 4/2/07, *David Koontz* <david at koontzfamily.org > <mailto:david at koontzfamily.org> > > <mailto:david at koontzfamily.org <mailto:david at koontzfamily.org>>> > wrote: > > > > I have installed masterview into the vendor directory and > when I start > > up mongrel I get: > > > > Initializing MasterView configuration (2007-04-02 13:18) > > Program name = script/server > > Using default admin_auth mixin for MasterView admin (local > > requests only) > > Adding MasterView AdminPages controller directories to > > controller_paths > > MasterView Admin pages enabled > > Failure to parse template. Exception=undefined method > `progress'' for > > #<MasterView::TemplateProcessing::SAXParserListener:0x224d5f8> > > Failure to parse template. Exception=undefined method > `progress'' for > > #<MasterView::TemplateProcessing::SAXParserListener:0x248661c> > > Failure to parse template. Exception=undefined method > `progress'' for > > #<MasterView::TemplateProcessing::SAXParserListener:0x240b0d4> > > Failure to parse template. Exception=undefined method > `progress'' for > > #<MasterView::TemplateProcessing::SAXParserListener:0x23c21e0> > > Failure to parse template. Exception=undefined method > `progress'' for > > #<MasterView::TemplateProcessing::SAXParserListener:0x23acbec> > > Failure to parse template. Exception=undefined method > `progress'' for > > #<MasterView::TemplateProcessing::SAXParserListener:0x2391234> > > Adding hook to allow MasterView to check for templates that have > > changed > > when processing a request > > Adding hooks to enable Rails to read erb directly from > MasterView > > MasterView plugin initialized - Version 0.3.2 > > ** Rails loaded. > > Followed by the rest of the normal rails startup output. > > > > When I try to hit http://localhost:3000/masterview > > <http://localhost:3000/masterview> or other url''s that > > are masterview generated content I get the same error again > > > > Failure to parse template. Exception=undefined method > `progress'' for > > #<MasterView::TemplateProcessing::SAXParserListener:0x3718bf8> > > > > Any idea on what I might have done wrong? I''m on Rails 1.2. > > > > > > Well David, I have good news and bad news. The good news is that I > have updated MasterView in the trunk with a version that checks the > REXML version before attempting to use the patched sax2parser. The > patched parser works with 3.1.4 - 3.1.6 versions of REXML. According > to REXML trac, supposedly REXML 3.1.7 will have my doctype patch in > the core, so it will not be needed after that anyway. I have also made > this patched parser configurable with a new config option. If you set > config.use_original_rexml_sax2parser = true, then it will not use the > patch regardless of the version otherwise it will load and use the > patch if REXML 3.1.4 - 3.1.6. I have tested MasterView with all of > these versions 3.1.4 , 3.1.5, 3.1.6 (current). > > The bad news is that REXML 3.1.3 seems to have a broken sax2parser > such that I get errors when trying to simply require it despite the > fact that we aren''t loading the rexml patch. So it appears that > MasterView won''t work with REXML 3.1.3. I put in a check for this now > in startup and it throws an exception if one tries to use a version > less than 3.1.4. 3.1.3 was released in 2004, so hopefully this will > not be a problem for most people. > > I have checked all the code changes into svn in the trunk and will > plan to do a gem build and release once Deb has had a chance to look > at my changes. > > svn://rubyforge.org/var/svn/masterview/trunk/masterview > > I have updated the documentation to indicate that REXML version needs > to be 3.1.4 or greater. > > Jeff > > > > > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Masterview-users mailing list > Masterview-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/masterview-users