Feature request: better implementation of section model

[exponentcms]

We could make much better use of the 'section' model beyond its current use to access the database for creation, selection, and deletion. Because of this we do not truly use it as a 'model' in most of the views/actions and tend to pass the entire menu/page hierarchy as an array of data. Besides we still access the global $db object from within the controller...which should be moved to within the model. The model could NOT include Ajax/JSON based methods since they must be made to the controller. Some possible model methods (which may or may not already be within the navigationController) could be:

• getParent()
• getTopParent()
• getSiblings()
• getChildren() - perhaps with params as to the depth such as all immediate children or all subordinates...of only a single depth down, etc...
• hasChildren()
• isTopLevel()
• isStandAlone()
• isPublic()
• some of the delete/remove method now in the controller? rebuild_sectionrefs()

[exponentcms]

[bulk edit]

[exponentcms]

Methods moved from controller to model

• hasChildren()
• getChildren() ... current params are section & yui (format)? added a 'single level' param
• canView()
• isPublic()
• rebuild_sectonrefs() moved to sectionref model (duh?)

New simple methods added

• isTopLevel()
• isStandalone()
• getParent()
• getSiblings()
• getTopParent()

[exponentcms]

(from [09030bc]) Feature request: better implementation of section model [#1242 state:resolved]
09030bc

[exponentcms]

(from [5d78495]) Converts several new methods in section model from static methods to object methods [#1242]
5d78495

[exponentcms]

Lighthouse URL: https://exponentcms.lighthouseapp.com/projects/61783/tickets/1242