Hi Peter, I get you now. No, you can't really do that. Like you say, the configuration is read "from a certain place". You can extend another place by referencing it in the "a certain place", but it can't work the other way round... You'd get into a situation where you have to dig deeper and deeper into the code, replacing the locations config gets read from - I don't think that's the way to go.
Just overwrite the configuration, don't worry about it. Even if it "feels wrong" now, in 2 weeks you'll have forgotten about it. The way the configuration works via content2bean really is one of magnolia's great strengths, so I think you'll like it even as it is... After more than 2 years' experience with magnolia I can say with confidence it is not a problem to modify the config. It's what it's there for. If you need to look at the original config you could keep backups, but I would not even bother with that. You can always start up a demo-system (or just use magnolia's online demo) if you need to check something about the original config... > Anybody got any other ideas how to leave stk config nodes unchanged while > still being able to use and extend stk? Depends what it is. For example, I leave all the original dialog, template and paragraph definitions and scripts untouched. I can simply copy & rename them if I need them. In Magnolia EE I also leave the original site-definition (demo-project) untouched, I can create my own site definition. In Magnolia CE you *have* to modify the site definition, because there is only one, but you can still leave the dialogs, template defs and template scripts untouched and make your own instead. For the configuration under /server/... I don't think there's a good solution without changing it - just go ahead and set your values there directly. Regards from Vienna, Richard -----Ursprüngliche Nachricht----- Von: [email protected] [mailto:[email protected]] Im Auftrag von peter falks (via Magnolia Forums) Gesendet: Donnerstag, 21. Juni 2012 15:38 An: Magnolia User List Betreff: [magnolia-user] Re: Customizing STK using dependent module I think I got it the wrong way around the entry point is the original location, that config might probably be extended by my module config, not the other way around. The ExtendingContentWrapper gets the extended information, but the entry point is the original location. Bummer, no extending /config/server from my module. Guess I am forced to bootstrap my stk config changes in my module. Anybody got any other ideas how to leave stk config nodes unchanged while still being able to use and extend stk? -- 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]> ---------------------------------------------------------------- ---------------------------------------------------------------- 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]> ----------------------------------------------------------------
