Joseph Method wrote: > This isn't the easiest way to start out with extensions, but I am > trying to integrate Instiki into Radiant. There will obviously be lots > of issues with this, but I'm experimenting to see how much refactoring > of the actual Instiki code will be required. So the first steps I've > taken: edited the Instiki migrations so that all redundant tables are > removed or renamed (pages becomes wiki_pages, etc.). Then I've pointed > my instiki_extension.rb to map /admin/instiki/create_wiki to > :controller=> 'wiki'. I don't expect it to work when it reaches > index.rhtml, but it stops when it reaches password_check, a method > belonging to the subclassed parent ApplicationController. So in the > original Instiki code, the Rails magic is able to access the parent > class. Is this a problem in the extensions implementation?
You can use the no_login_required class method to turn authentication off on for a specific controller: class MyController < ApplicationController no_login_required end -- John Long http://wiseheartdesign.com _______________________________________________ Radiant mailing list Post: [EMAIL PROTECTED] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
