Hmm no reply yet, let me clear up my questions: 1. It doesn't seem possible to extend STK by supplying all code and config in a new module. So without modifying STK config. Is that right or am I missing something?
2. TemplateAvailability config and server config can not be extended from a module it seems, is that right? For template availability you would have to change stk config and plug in your own class or add entries to the availability list itself. For server config I tried all kinds of extensions from my module config, but so far no luck. My suggestion to magnolia dev team is to remove all instanceof STKPage code in the category / root resolving part so that an implementer can create his own page type based on STKPage. I also found the code for finding rootnode scattered around a bit. Lastly it would be handy if the stktemplatingfunctions and other helpers could be easily overriden since they contain parts that could conflict with ones custom implementation. -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=2e053b50-f2f1-4c17-9551-cc0cfb3dacc7 ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
