> I have just checked in some additional tests that show extension > routes working fine. I also created an extension, put in a custom > route, generated a link using url_for, and have no problems. A couple > of comments below:
thanks Adam I think things may be messed up in my case because I'm trying to add functionality to the page edit screen. I did this by directly editing page/edit.rhtml (in core radiant) and adding: <%= render :partial => 'attributes' %> But that partial exists only in my extension. This works, but I get the exception the second time _attributes.rhtml is loaded (via a page edit). I was thinking this would just be a temporary hack to make sure things work, and then later I would figure out how to enable the registering of a tab with the Page Edit interface just like you can register a new tab for the overall admin interface. So, so far I'm stuck here, but maybe I'm taking the wrong approach to modify the page edit screen. Any other suggestions? thanks, Jacob -- Posted via http://www.ruby-forum.com/. _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
