Following all the steps to disable directory trees like
"bySubjects" and "byCoverage" don't work. This is my
contrib:
<extension
target="org.nuxeo.ecm.platform.ui.web.ContentViewService"
point="contentViews">
<contentView name="bySubjectsContentView"
enabled="false" />
<contentView name="byCoverageContentView"
enabled="false" />
[ ... ]
</extension>
<extension
target="org.nuxeo.ecm.platform.virtualnavigation.NavTreeService"
point="navigationTree">
<navTree treeId="bySubjectsNavigation" enabled="false"
/>
<navTree treeId="byCoverageNavigation" enabled="false"
/>
</extension>
<require>org.nuxeo.ecm.virtualnavigation.directory.DirectoryTreeService.contrib</require>
<extension
target="org.nuxeo.ecm.webapp.directory.DirectoryTreeService"
point="trees">
<directoryTree name="bySubjectsNavigation"
isNavigationTree="false">
<directory>topic</directory>
<directory>subtopic</directory>
</directoryTree>
<directoryTree name="byCoverageNavigation"
isNavigationTree="false">
<directory>continent</directory>
<directory>country</directory>
</directoryTree>
</extension>
Anyway, it seems to me that this mechanism is very
incoherent, because if you have the navigation tree concept,
the logical way to disable one navigation tree is to do it
through this extension point.
In that sense, I propose you, Nuxeo guys, (if you haven't
done yet) to declare directoryTree as navigation tree in the
navTree extension, rather than current confusing
implementation.
Thus, you can remove this block of code:
List<NavTreeDescriptor> directoryTrees =
getDirectoryTrees();
if (directoryTrees != null) {
allTrees.addAll(directoryTrees);
}
keeping it cleaner, IMHO. I've done in that way and all is
working like a charm.
Regards.
---
Mailing list: [email protected]
Forum: http://forum.nuxeo.org/f/1/
