New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Display Page Template info in the Details panel #4916
Comments
Show the same way as in edit mode. Link to edit. |
…anel #4916 Added Page Template filed to properties widget.
Nice. But didn't @mortyeriksen and @sigdestad mention that this should be added as a box of it's own? Not important for me though, but we need two lines of info. Depending on tooltips on hover is a bit annoying and not obvious, also not very accessible. The information for a page template is two lines: This is how it looks when editing a content and inspecting what is used to display it. |
…Correctly retrieve page template info inside (#4916)
…a link to page template wizard. Moved content summary inside the details container to fix vertical scrolling. (#4916)
Display name of used Page Template for every Content in the Details panel #4916
In the list of "system data" for each content inside the Details Panel, it would be oh so ever handy to see the answer to a very common question on all training sessions I've held: what Template is running?
Add "Template: Xxx" (preferable with a link to select that specific template in the content grid!).
Name of template should be its DisplayName.
If no template is used, that should be displayed like "No template set up" (not linked anywhere), if automatic is used, then that should also be specified with "Template: automatic (Articles)" so that you always can find the correct info (without clicking 10 times and finding this info deep within the Page Editor).
And of course, if template is custom, "Template: Custom" is written (not linked anywhere).
In here is a most perfect place to put this kind of data! Many have requested it.
The text was updated successfully, but these errors were encountered: