Page_attr / getchildren enhancement (v2.2.x vs 2.3)
Posted: Thu Feb 27, 2020 10:19 am
Hi,
I haven't tested v2.3 yet and I hope this is not already done there.
I've based content navigation in templates on child structure in our cms (head, child, sub-child) and as advised by people here (deprecated menu module).
I find it very pleasant for dev and much more practical for editors too.
As I'm working for side project with "graphical/textual" content listings, I found myself very dependant on the page_attr and custom content (title, description, introduction, word from the author, date...whatever).
So here is my need, make page_attr capable of returning a (full) collection of attributes at once to avoid multiple calls.
As a side mater, CGSimple_getchildren might benefit from same logic and return attributes (maybe getchildren_attr new function)
I understand this is typically something one could self-develop but it does have some merit to be in our base CMS (or CGSimple) to build leaner smarty templates.
Thx for feedback or ideas.
I haven't tested v2.3 yet and I hope this is not already done there.
I've based content navigation in templates on child structure in our cms (head, child, sub-child) and as advised by people here (deprecated menu module).
I find it very pleasant for dev and much more practical for editors too.
As I'm working for side project with "graphical/textual" content listings, I found myself very dependant on the page_attr and custom content (title, description, introduction, word from the author, date...whatever).
So here is my need, make page_attr capable of returning a (full) collection of attributes at once to avoid multiple calls.
As a side mater, CGSimple_getchildren might benefit from same logic and return attributes (maybe getchildren_attr new function)
I understand this is typically something one could self-develop but it does have some merit to be in our base CMS (or CGSimple) to build leaner smarty templates.
Thx for feedback or ideas.