Move indexing functionality to pm core, and extend

Created on 12 April 2016, over 8 years ago
Updated 24 February 2023, over 1 year ago

In 2.x, a common question has been regarding creating views relationships to parents of a specific type. This was cumbersome because it required chaining relationships, each time referencing only the immediate parent.

This is vastly improved in 3.x already (thanks to @D34dMan). Pm organization now maintains its own index of the organization attached to a specific node, whether it is the immediate parent or not. This means that we can use this relationship in views.

I propose that we extend this functionality to any node type. I think the simplest way would be to simply store all parents in the index. Then in the view, a standard node type filter could be used to select the org, project, etc.

Another way to do this would be to store the node type of the parent in the index as well, and configure this as part of the views relationship, but this feels to me like it duplicates functionality that the standard node type filter already provides.

📌 Task
Status

Closed: won't fix

Version

3.0

Component

Code

Created by

🇬🇧United Kingdom juliangb

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇩🇪Germany D34dMan Hamburg

    All feature request against 7.x would be closed. The focus is now on Drupal 10 release. If you feel this issue is relevant for Drupal 10 version of the project, please feel free to re-open and update the issue. Thanks for the discussion/contribution.

    You may follow 📌 Port PM to Drupal 10 Active to know more about Drupal 10 status.

Production build 0.71.5 2024