#711 - Allow more control over where/how often pages show under the Wiki+ tree view
| Identifier | #711 |
|---|---|
| Issue type | Feature request or suggestion |
| Title | Allow more control over where/how often pages show under the Wiki+ tree view |
| Status | Open |
| Handling member | Deleted |
| Addon | wiki |
| Description | The Wiki+ tree view only shows a Wiki+ entry in the tree view once, and it seems to default to showing the most recent location that an entry was added. I would like to suggest that an option to be added under the Wiki+ entry editing view that allows the user (or just admin, or be a privilege-controlled option) to select from the following options:
1) Show entry in all tree locations (this may mean that an entry shows in multiple locations) 2) Show entry under the selected tree locations (with an option that allows the user select from the current parent tree's that are active for that Wiki+ page) 3) Show only one entry (with an option to select either "first parent" or "most recent parent") It would be best if an default option could be specified in the site settings (probably a choice of the #1 and #3 options, with #2 being over-ride option within each Wiki+ entry). |
| Steps to reproduce | |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".
Comments
The main reason it only shows one parent right now is to stop loops. That's because the tree is not a real tree, it's what they call a "graph" in computer science. I believe it is quite possible to make a page 'A' with a page 'B' under it with the page 'A' under that. A different algorithm could be used to prevent display of loops.
A secondary reason is we don't want the tree to be huge. On some sites it won't be, on some sites it will be. Minimising redundancy in the tree mitigates that, but it's not really a solution. The solution would be to have a maximum-display-depth option, and to allow generation of subtrees for any page via an icon on that page.
This removes the need for a complex UI -- as we want to make Composr automatically display pertinent information, rather than being a complex database management system.