Hey folks, I talked to infra (well, Joe) and they would like to see SSI turned off on our vhost
it appears there's a much simpler way to implement our navigation using the CMS' philosophy more directly. < joes4> jMCg: can we finally shut off ssi for trafficserver? < jMCg> joes4: I'm afraid not: For two reasons: The old docs still use it, and the new docs use it for the navigation. < gmcdonald> cms has its own nav includes < joes4> bad design jMCg < joes4> should just enable it for the old docs < jMCg> joes4: how am I supposed to generate the nav for the CMS without regenerating all the pages? < joes4> why wouldn't you want to regenerate all the pages? < joes4> you just drop the nav stuff into templates < joes4> and include those templates into your main template < jMCg> joes4: that.. makes sense. < jMCg> Well, except that the nav is different for different subtrees. < joes4> there's no point to ssi with the cms < joes4> you need to break out that logic in your path spec < joes4> template names can be parametrized < jMCg> joes4: ACK, will discuss with amc. < joes4> in your path.pm pass a variable which represents the name of the nav template to use < joes4> and in your main template use that variable with an include statement < joes4> no perl code necessary in view.pm < joes4> that is the standard way of doing nav < joes4> with django templates < joes4> might require an eval if you want to use a piece of the path as the argument < joes4> lemme look at the build system < joes4> yes so if you went that route i don't recommend monkeying with path.pm < joes4> just use captured variables in your regexp and reference them in the corresponding view < joes4> and in there add something to %args < joes4> it'd probably be worthwhile to document your steps at cmsref.html So long, i -- Igor Galić Tel: +43 (0) 664 886 22 883 Mail: i.ga...@brainsware.org URL: http://brainsware.org/ GPG: 6880 4155 74BD FD7C B515 2EA5 4B1D 9E08 A097 C9AE
