The new Plone Roadmap (under progress) is aiming at seperation of the
navigation from the general catalog.
It is important to understand two understand very important approaches
for editors (not programmers) that should be seperated in the future:
1. The switch to exclude an object from navigation.
This is very important if you need to hide an object outside his
context due to security or orientation purposes.
2. Simplifying the displayed navigation to avoid duplicated entries
when an object is set as default object of the folder.
In Plone both flags seem to be used to set the same result but due to
different targets.
Just filtering out the data from displayed elements by CSS is bad
design, if you need the semi security feature, because if you get the
content via RSS, CSS is ignored.
We often have the need to display an object as default but include it
in the navigation.
A workaround is to use a link object that points at the object to be
diplayed as default and set the link object as default. The link is
not displayed in the navigation and the intended object is displayed
by default.
The backdrafts of this approach:
1. Needs the option to redirect at once set for the content type "Link".
2. A lot of clicks and boring if used more than in some folders.
3. Unconvenient for the "Owner" of the link who always sees the link
instead.
Keep Dexterity in mind!
If in the future all objects can become folderish, the lack of a
"container" to hold the setting, needs the implementation of a flag or
special view to display explicitly the content or the redirect to the
default.
If reimplemented in the core, an improvement should fix all these
points at once!
Armin
Am 22.04.2012 um 15:29 schrieb Andreas Jung:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Does anyone know where the default page of a folder is filtered out?
The navigation portlet won't display an object if it is set as default
page of a folderish object. Our editors find this behavior weird -
so I
need to revert it. I would prefer if the full tree would be exposed
and
such a filtering could be applied in a less invasive way e.g.
through CSS.
- -aj
_______________________________________________
Product-Developers mailing list
[email protected]
https://lists.plone.org/mailman/listinfo/plone-product-developers
