Richard Frovarp schrieb: > Andreas Hartmann wrote: >> Richard Frovarp schrieb: >> >> [...] >> >> >>>> the problem here is that your publication inherits the module >>>> declarations of the default publication. You can either remove them >>>> from default/publication.xconf or file an enhancement bug that you >>>> need the functionality to exclude the menu items. I don't think we >>>> should provide a mechanism to override the module inheritance, since >>>> this would reduce the functionality of a child publication and I guess >>>> this could lead to unpredictable problems. >>>> >> >> >>> Okay. I thought that since the publications obtain a copy of >>> publication.xconf from the super publication it didn't fallback for >>> module declarations. This actually works out just fine for me. I will >>> probably end up with a large number of publications. If I want to add a >>> module, it can be done at a lower level. If I need to remove a module, >>> then I will need to touch all of the publications. >>> >> >> That's a bug, the module + resource type declarations shouldn't >> be copied. Thanks for the pointer! >> >> http://issues.apache.org/bugzilla/show_bug.cgi?id=41084 >> >> -- Andreas >> > > I take it from the comment about creating the first page for a template, > that any changes to the publication.xconf for an individual publication > should go into local.publication.xconf? Will these be inherited as well > by lower publications or no?
I have to admit that I'm not familiar with the local.publication.xconf mechanism, but I guess that it just replaces publication.xconf during the build process. So I guess if you're using local.* files, you have to make your changes there and they will be inherited. -- Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
