Deciding which template set to use in catalogues view
Standard member
Example: let's say we have a catalogue with codename faqs.
Viewing the catalogue shows these templates:
Code
templates/CATALOGUE_DEFAULT_CATEGORY_EMBED.tpl (1)
templates/CATALOGUE_DEFAULT_CATEGORY_SCREEN.tpl (1)
templates/CATALOGUE_DEFAULT_FIELDMAP_ENTRY_FIELD.tpl (1)
templates/CATALOGUE_DEFAULT_FIELDMAP_ENTRY_WRAP.tpl (1)
templates/CATALOGUE_DEFAULT_GRID_ENTRY_FIELD.tpl (1)
templates/CATALOGUE_DEFAULT_TABULAR_ENTRY_FIELD.tpl (1)
templates/CATALOGUE__catalogue_category_FIELDMAP_ENTRY_FIELD.tpl (1)
templates/CATALOGUE__catalogue_category_FIELDMAP_ENTRY_WRAP.tpl (1)
templates/CATALOGUE__catalogue_category_GRID_ENTRY_FIELD.tpl (1)
templates/CATALOGUE__catalogue_category_TABULAR_ENTRY_FIELD.tpl (1)
templates/CATALOGUE_faqs_CATEGORY_EMBED.tpl (1)
templates/CATALOGUE_faqs_CATEGORY_SCREEN.tpl (1)
templates/CATALOGUE_help_support_FIELDMAP_ENTRY_WRAP.tpl (20)
Strangely, it's also referencing a template from another catalogue of mine (the last one, help_support)
Is this normal or should it only display one template set?
Site director
I've tried to explain the page rendering tools better:
https://github.com/ocproducts/composr/commit/2ae4b7a54ea8248153b631d5fd565e9533897a59
As for catalogues you're not meant to see there, wow you found a performance issue. Fixed in:
https://github.com/ocproducts/composr/commit/d12a659960803e7548c329f1a314dfe7b2de89b2
Become a fan of Composr on Facebook or add me as a friend. Add me on on Mastodon. Follow me on Minds (where I am most active). Support me on Patreon
- If not, please let us know how we can do better (please try and propose any bigger ideas in such a way that they are fundable and scalable).
- If so, please let others know about Composr whenever you see the opportunity or support me on Patreon.
- If my reply is too Vulcan or expressed too much in business-strategy terms, and not particularly personal, I apologise. As a company & project maintainer, time is very limited to me, so usually when I write a reply I try and make it generic advice to all readers. I'm also naturally a joined-up thinker, so I always express my thoughts in combined business and technical terms. I recognise not everyone likes that, don't let my Vulcan-thinking stop you enjoying Composr on fun personal projects.
- If my response can inspire a community tutorial, that's a great way of giving back to the project as a user.
1 guest and 0 members have just viewed this.
