<br><br><div><span class="gmail_quote">On 11/10/06, <b class="gmail_sendername">Ed Howland</b> <<a href="mailto:ed.howland@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">ed.howland@gmail.com
</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Jeff and Deb,<br><br>Turns out I had a project with many user defined directives. I<br>installed 0.3.0 and followed the instructions in your email.<br><br>What I did was this (in a typical directive in<br><rails_app>/app/masterview/directives/text_field_tag.rb:)
<br><br>require 'masterview/deprecated/directive_base'<br>module MasterView<br> module Directives<br> class Text_field_tag < MasterView::DirectiveBaseOld<br>...<br># for testing this just redefines empty stag/etag methods
<br><br>Then I went into all .html files that had custom directives and<br>changed the namespace from mv: to mvx: (Note: the errors below were<br>unchanged before I switched namespaces to mvx)<br><br>Running rake mv:parse results in :
<br> ERROR -- : Failure to parse template. Exception=undefined method<br>`attribute_qname' for MasterView::Directives::Text_field_tag:Class<br>It also seems to be missing class method : namespace_name<br><br>Now, some other directives complain about this:
<br>ERROR -- : Failure to parse template. Exception=undefined method<br>`harden_metadata' for<br>MasterView::Directives::Link_to_remote_no_quote:Class<br><br>These exist only in 0.3.0. So it seems that while it seems to be
<br>seeing my existing directives in the new namespace or using the new<br>directive_base.rb instead of the old deprecated one.<br><br>Have I missed a step?<br><br>Ed<br><br><br></blockquote></div><br><br>Deb,<br><br>I am out the door to get on a plane, will be back Wednesday.
<br><br>Can you take a look at Ed's problem? <br><br>It looks like we didn't have good test coverage in this area. I added a test example_directive_base_old_test.rb into the trunk, so if you have time to test you can run that.
<br><br>Also sounds like he might have some other issues with it finding his directives.<br><br>PS. Also we can upgrade his directives to the new API as well, but we should resolve the problems either way.<br><br>Thanks,<br>
<br>Jeff<br><br>