> This was an often requested feature: the ability to select a number
> of content items that should always appear at the top of a
> collection. It made sense to use the otherwise unused related items
> field to implement this.
Thanks, Wichert. I can understand this being a useful feature. I think
we can keep it and still do better, UI-wise, than special-casing the
use of the Related Items field, as it confuses 8 out of 8 of the users
I informally polled. Besides, the Related Items field is not otherwise
useless on Collections; my content editor sought to use it for its
normal purpose and considered the resulting behavior a bug, as did the
other 7 polled.
What do you think of adding an actual, dedicated field to Collections,
something like a ReferenceField called "Other items to include"? A
migration could move any related-to-Collections items to this field.
I'm happy to write a PLIP and the code and do some usability testing.
Regards,
Erik
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/_______________________________________________
Plone-developers mailing list
Plone-developers@...
https://lists.sourceforge.net/lists/listinfo/plone-developers