-
Suggestion
-
Resolution: Unresolved
-
None
-
1
-
1
-
NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.
Hello - I am trying to create a page template with several fields on it (e.g. field A, field B, field C), and would like to then list each page created via the template in a tabular format. So if I have 10 pages, I would have a column for A, B and C. When I try to do this using Page Properties macro so that I can later user Page Properties Report macro, upon previewing my page, I get "Details can only be used on pages or blog posts" in the place where I placed the Page Properties macro in my template. The steps to create this issue are:
1- Create a new template.
2- Place Page Properties Macro into the template.
3- Add a table with two columns into Page Properties section. Column 1 should have labels, Column 2 should have corresponding variable names.
4- Preview the template and the error message appears. The same message appears if the template is saved and later a page is created via the template.
- relates to
-
- Closed
[CONFSERVER-28573] Allow the page properties macro to be used in templates with variables
Rob van der Lee
added a comment - Workaround:
this "Details can only be used on pages or blog posts" only occurs when a label is used in the macro page-properties macro. I don't use this label (nor do the default blueprints) but just add a label to the page template which is used by the page-properties-report.
Rob van der Lee
added a comment - Workaround:
this "Details can only be used on pages or blog posts" only occurs when a label is used in the macro page-properties macro. I don't use this label (nor do the default blueprints) but just add a label to the page template which is used by the page-properties-report. Pretty crucial functionality for us as well.. If not considered a bug, then definitily a showtopper !
Scott Weintraub
added a comment - How in the world is this not a bug? the current behavior was intended?
Scott Weintraub
added a comment - How in the world is this not a bug? the current behavior was intended? 
Daniel Berman
added a comment - This would be a pretty handy fix because the page property summary allows arbitrary columns to be displayed as opposed to the content summary macro where you cannot (summarize by label).
Daniel Berman
added a comment - This would be a pretty handy fix because the page property summary allows arbitrary columns to be displayed as opposed to the content summary macro where you cannot (summarize by label). This is quite confusing. I also have this problem. The title of this issue has been changed to "Allow the page properties macro to be used in templates"... but isn't it supposed to work in templates by design???
The Page Properties macro is used in the Product Requirements Blueprint template:
https://confluence.atlassian.com/display/DOC/Product+Requirements+Blueprint
Moreover Matt Hodges here suggests the use of this macro to enhance a Blueprint template:
https://confluence.atlassian.com/display/DOC/Working+with+Blueprints (see comments)
Is there any difference between a blueprint template and a standard user template?
I was very disappointed to find out this isn't working!
Though the user experience seems to be even worse now!
When trying to use template variables in the page properties macro table it just doesn't work when creating a page from template, variables are being ignored! Please fix this!