> You seem to need access to the Wiki object in more then one controller.
Why?
One case of use is described in issue 962 (now fixed, about re-using the
wiki model)
Other possible case: I intend to give access to wiki documents from a view
in a plugin, i.e.:
controllers/plugin_bavaria.py
def wiki():
# another wiki interface
# for customizing with
# plugin layout elements
return auth.wiki()
link in plugin_bavaria/views/menu.html
{{=more_plugin_stuff}}
<!-- Ja, a link to a real bavarian speciality!-->
<!-- Not sure if I am using a valid link here -->
{{=URL(c="plugin_bavaria", f="wiki.html", args=["my-bavarian-menu-slug"
,]))}}
I can see why one may want to define the wiki outside of an action to
> benefit from the menu (if you delete models/menu.py) all actions will have
> the wiki menu but only one action should actually expose the menu.
>
You're right, I was not following correctly the way the new wiki works.
--
