Plone should…

Support content object references

I know this isn't exactly new, but it's really crying for a solution:

We often have a few pages (or other objects) that contextually belongs in more than one place (folder).

To avoid creating redundant objects means using collections or custom views, etc. all of which are too complicated for content managers that aren't plone savvy.

How can we accomplish this?
Often the content

63 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    IanFHoodIanFHood shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
    planned  ·  optiludeAdminoptilude (Admin, Plone) responded  · 

    I’m doing some research into something similar, in the package collective.alias. I’m not sure how well it’ll work yet, but it’s coming along. This is based on SimpleAlias (in principle, there’s no code sharing), which already works today (but has a few limitations).

    6 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • yurj.spaceyurj.space commented  ·   ·  Flag as inappropriate

        Products.UberForlder too:

        https://svn.plone.org/svn/collective/Products.UberFolder/

        The fun thing is that you can run subtyping on this folder, it is a sort of virtual collection:

        ========

        Introduction
        ============

        This is a fake folderish content type to aggregate contents.

        Typical use cases:

        - Aggregate contents with related info but without enough metadata to be
        aggregate with a Collection.

        - Provide a specific view to show data, for example to show graphical
        data of many contents.

        In general: you have to collect contents but a Collection find too many objects
        or too few or the criteria should be too complicated to be manageable.

        Features
        ========================

        Similar to Collection it aggregates the contents in the portal, contrary you
        have to choose explicity which contents you want to show.
        The behavior is like a Folder content, *the methods provided are the same*.

      • yboussardyboussard commented  ·   ·  Flag as inappropriate

        Yes it's a good feature I think and some user want to have this in plone. Collection and link don't answer to this problematic because the content stay in one place and user want have a new virtual place for his content. The best will have an collection like content type that put all content referenced by criteria in virtual place. So you can have automatic transversal navigation defined for example by keyword.

      • davisaglidavisagli commented  ·   ·  Flag as inappropriate

        You can also use Plone's built-in Link content type to this effect...though that would be better if it supported internal links by UID and a reference browser widget, in addition to the plain URL input

      Feedback and Knowledge Base