The not open doc material for developers prompts that....thought that this point of my question was already completed.... With my working with TYPO3 i think its obvious for me that i dont hack around in the source and use modules but that was not my question! The question was what is the best way to solve this, is it now solveable through using a template that searchs the whole site, if, how to do that or do i have to use a module and if, is there any documentation (not the short short one about using maven as archetype) about this for not members of ur club!
Very Best Regards Boris Magnolia - User mailing list wrote: > > On Mar 25, 2008, at 5:53 PM, sirobbob wrote: >> ... >> 2. as i know now, there isnt any 'real' support how to build >> modules if you >> use the community edition, > > > What prompts this observation? > > Magnolia is made of modules, the CE as much as the EE. Anything you > customize should ALWAYS be in a module, or you break your update path. > > Regards > - B > > ---------------------------------------------------------------- > for list details see > http://documentation.magnolia.info/ > ---------------------------------------------------------------- > > -- View this message in context: http://www.nabble.com/export-tree-to-xml---where-to-find-in-the-sourcecode-tp16278377p16300424.html Sent from the Magnolia - User mailing list archive at Nabble.com. ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/ ----------------------------------------------------------------
