View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 142 | Composr | core | public | 2010-04-07 22:18 | 2015-05-03 23:17 |
| Reporter | Chris Graham | Assigned To | Chris Graham | ||
| Priority | normal | Severity | feature | ||
| Status | resolved | Resolution | fixed | ||
| Summary | 142: Merged sitemap API | ||||
| Description | We currently have a sitemap API, and a sitetree API, and the splurgh/tree-view code, and the content tree APIs. These are all structural content APIs and should be merged (we also have the content_meta_aware hooks, and also award hooks, but these are more service-orientated although they still can tie into structure). Advantages: * simpler code * if the sitemap block uses this merged system we can remove the memory problems, by using the splurgh system for display. * we could get rid of the splurgh-powered 'tree' screens for content modules, which hardly get used, and instead make it so the main_sitemap block can be called up to show subtrees of the wider sitemap, as required (more flexible). * we can do a better job of menu auto-generation * we can get around some design problems with the splurgh system: bad caching model, performance problems due to showing too much at once, requirements for JS [we can now avoid splurgh entirely - see above] | ||||
| Additional Information | Also it would be nice if Comcode pages were rendered in a tree from this API, respecting their defined parenting structure (if one has been). | ||||
| Tags | Risk: Core rearchitecting , Risk: Major rearchitecting , Type: Cross-cutting feature | ||||
| Attach Tags | |||||
| Time estimation (hours) | 16 | ||||
| Sponsorship open | |||||
| parent of | 140 | Not Assigned | Guest | Category permissions for menus |
| parent of | 16 | Resolved | Chris Graham | Fully support menu stitching |
| related to | 130 | Resolved | Chris Graham | Foolproof content embedding |
| related to | 1250 | Not Assigned | Guest | Allow menu items to show current-page highlighting via analysis of breadcrumbs |
| related to | 1366 | Resolved | Chris Graham | Adaptive menu mode |
| related to | 1389 | Resolved | Chris Graham | XML Sitemap index |
| related to | 1390 | Not Assigned | Guest | Include "last comment date" in XML Sitemap date |
| Not all the children of this issue are yet resolved or closed. | ||||
|
|
Also ID selection for the main_content block should work from the single site tree, when it's developed. So you don't select content-type+ID, you just browse to the content. |
|
|
See if we can incorporate breadcrumbs into this, so they are auto-generated by the Site Tree where possible. Also tie in the logic about menu item subordination. |
|
|
We don't need to see the term "entry point" anywhere in the UI or documentation. We can just use the term page-link. |
|
|
Suggest that tracker item 415 also be addressed at the same time. http://compo.sr/tracker/view.php?id=415 |
|
|
This functionality may be built on top of the new Resource-FS. |
|
|
Note that we want to make sure that Comcode page hierarchy comes out of this system correctly. Currently the pages come out flat, because they are top-level under a zone. |
|
|
We can also likely merge in the do_next_menu hooks as part of the site-tree, (and give site-tree nodes support for icons in the process). |
|
|
Also consider if we need to allow different XML sitemaps, per content-type (i.e. to stop the main one getting larger than is allowed, isolating size problems in a specific sitemap). |
|
|
Absorb the bookmarks menu into the site-tree also. |
|
|
Also features like list_galleries, which are of very limited use, can simply become part of the new site tree. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2016-06-08 00:14 | Chris Graham | Tag Renamed | Major rearchitecting => Risk: Major rearchitecting |
| 2016-06-08 00:15 | Chris Graham | Tag Renamed | Core rearchitecting => Risk: Core rearchitecting |
