-
Bug
-
Resolution: Fixed
-
Low
-
5.1.5
In Confluence 5.1.3 the "create from template" macro created child pages from where the macro was used. This does not work anymore in version 5.1.5. New pages from the template are created directly below the the space home page. The behavior should be changed again to create child pages or to be more customizable specify the parent page for the new pages in the macro. Otherwise it is not possible to keep a clean space structure.
- relates to
-
CONFSERVER-29859 'Create from Template' Macro No Longer Creates Child Pages
-
- Closed
-
[CONFSERVER-30495] create-from-template macro creates pages in wrong place
Workflow | Original: JAC Bug Workflow v3 [ 2880714 ] | New: CONFSERVER Bug Workflow v4 [ 2989591 ] |
Workflow | Original: JAC Bug Workflow v2 [ 2781182 ] | New: JAC Bug Workflow v3 [ 2880714 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JAC Bug Workflow [ 2709272 ] | New: JAC Bug Workflow v2 [ 2781182 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2377712 ] | New: JAC Bug Workflow [ 2709272 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 [ 2266729 ] | New: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2377712 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5.1 - TEMP [ 2210398 ] | New: Confluence Workflow - Public Facing - Restricted v5 [ 2266729 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2156442 ] | New: Confluence Workflow - Public Facing - Restricted v5.1 - TEMP [ 2210398 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 [ 1912010 ] | New: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2156442 ] |
@Karina, Please see the status of this issue and
CONF-29859. Both have been said to be resolved in Confluence >= 5.2.5. If you are experiencing the issue with a later version, I suggest you create a new Jira issue and link this orCONF-29859to explain it's a possible regression in that later version. If you however are running Confluence < 5.2.5, I suggest you upgrade to a later version which should fix this issue.