is not a mechanism, just a page include), this is simply a feature request
that had been (to my understanding) approved and only due to my own
inability to get the patch in is it not there now.

I don't care about the reason or whether it has been approved or not. It is clearly too late for 2.6.

You can say that you have a ticket to the plane at the gate, but if the plane is already rolling on the tarmac, it's simply too late.

I would recommend opening a ticket at the issue tracker. That way it won't be forgotten.

(And frankly, I don't still see the point. You can install your own ViewTemplate.jsp with your personal headers in your own custom template directory, and it should just work across upgrades. That's what I do. I think this TitleBlock feature is going to be far more useful in 3.0 timescale, when a) we're reworking the templates the next time, and b) there will be a proper multiwiki feature, which will probably allow custom CSS for each wiki, so it is helpful to have common elements.

Heck, why does it have to be a TitleBlock? Our company requires both a sidebar and a titleblock - and I've seen companies which require a footer block. Why should we have a block for each possibility? Isn't it just easier to allow people to define their own structures through the ViewTemplate than to second-guess every single possible corporate deployment?)

/Janne

Reply via email to