Hey guys,
thanks for the swift reply! :)
Ian, interesting point. I'm running 1.0.1 here, but now you've got me
thinking of a custom filter that adds modules to the top of the
routing rules. I'll give it a shot, thanks.
Georg, actually I like that solution. That would nicely sit in a
preExecute.
Hey Daniel,
This is certainly not the smartest solution but it's probably as good as
the requirements: ... you mentioned as long as they don't really exist
:) Couldn't you check in the executeShowPage action whether the
requested page_name is actually the name of an existing module, and if
so, fo
Richtermeister wrote:
> module:
> url: /:module
> param: { action: list }
> requirements: { //module is a real module that exists in this app }
>
>
> That would rock, methinks.
> Or how do you guys go about serving "random" pages?
Interesting
In sf1.1 , you cuold listen to an even
