#1089 - Commandr-fs content hooks
| Identifier | #1089 |
|---|---|
| Issue type | Feature request or suggestion |
| Title | Commandr-fs content hooks |
| Status | Completed |
| Handling member | Chris Graham |
| Addon | commandr |
| Description | Add a new abstract CRUD/REST-style internal content API via Commandr-fs.
Implement this for all the content_meta_aware and resource_meta_aware hooks, adapting the existing hooks to reference the new Commandr-fs for that hook. The content_meta_aware/resource_meta_aware hook must specify whether they are operating on directories (categories) or files (entries). i.e. we don't implement separate Commandr-fs hooks for category and entry types, they are shared by one hook, which handles them as directories and files. Content-types will be uniquely identified by a URL moniker. In order to facilitate quick and consistent implementation of the hooks, they will inherit from a superclass which defines some of this functionality automatically. Our Commandr-fs objects should have the following methods, roughly... class … extends commandr_fs_cma_bridge { function find_id_by_context($context) { } function find_id_by_name_and_context($name,$context) { } function add($name,$context) { } function delete($id) { } // Most of the following will inherit, so actually will be defined in commandr_fs_cma_bridge function set_properties_via_cloning($id,$from_id) { } function set_properties_via_import($id,$file_path) { } function set_property($id,$key,$val) { } function set_content_access($id,$groups) { } function set_content_privileges_from_preset($id,$group_presets,$assume_full_group_coverage=true) { } function set_content_privileges($id,$group_settings,$assume_full_group_coverage =true) { } function set_content_privileges_from_preset__member($id,$member_preset) { } function set_content_privileges__member($id,$privilege,$setting) { } function find_cma_hook() { } } We need a function defined in the existing Composr content API… function find_commandr_s_hook_for($content_type) { } This allows easy integration of the existing content API, with the more sophisticated CRUD Commandr-fs API. |
| Steps to reproduce | |
| Related to | #1113 - Aggregate Content Types #1139 - Commandr-fs resource hook - theme images #1138 - Commandr-fs resource hook - newsletters #1137 - Commandr-fs resource hook - emoticons #1136 - Commandr-fs resource hook - filedump #1135 - Commandr-fs resource hook - point-store #1134 - Commandr-fs resource hook - staff stuff #1133 - Commandr-fs resource hook - chat messages #1132 - Commandr-fs resource hook - billboard #1131 - Commandr-fs resource hook - warning templates #1130 - Commandr-fs resource hook - private topic invitations #1129 - Commandr-fs resource hook - quiz entries #1128 - Commandr-fs resource hook - word-filter #1127 - Commandr-fs resource hook - HTTPS settings #1126 - Commandr-fs resource hook - gathered feedback info #1125 - Commandr-fs resource hook - member settings #1124 - Commandr-fs resource hook - event reminders #1090 - WebDav for Commandr-fs #1140 - Commandr-fs resource hook - classifieds #1141 - Commandr-fs resource hook - gifts #1142 - Commandr-fs resource hook - diseases #1143 - Commandr-fs resource hook - activities #1145 - Commandr-fs resource hook - booking #1146 - Commandr-fs resource hook - workflow |
| Funded? | No |


Comments
Do a search of a Resource-FS hook's structure if it fails to look up a label, to confirm it really is missing - but only if we don't have too much of that content type (i.e. a safeguard)
Unit tests for resource-fs, life-cycle each resource type with lots of asserts (partially done, 'delete' ops not yet fully passing)
Unit tests for aggregate content types (ACT), life-cycling
Test ACT UI
Test ACT in detail
"Explicit move flag" used for Wiki+ page path, as currently prevents multi-categorisation of pages
Make sure GUIDs are explicitly set/specified for the resources auto-created when a match failed (currently it's not done)
Implement _folder.xml