Space Blueprint Children Issues

Hello Atlassian users,

I recently went through all of the beginning/intermediate template, blueprint and space blueprint tutorials in order to write out own space blueprint (which I used the simple blueprint as a guide for). Everything seemed fairly straightforward and self explanatory, but I cannot, for the life of me get any child page, other than my data child page, to show up. I thought for some reason I might have been limited to one child page, so I removed the content-template definition and blueprint reference for my data page, and nothing shows up. If I add multiple references to my data page, only one shows up. I have literally spent about 12 hours working on this problem and I cannot make any darn sense out of it. I know about the hello blueprint, and checked it out, and it works, but  I would like to build my own blueprint from scratch, so I do not have to go in and clean up everything. Also, for the record, my child page is experiencing the same issue detailed here (

Below are my atlassian-plugin.xml, properties, soy, and js files. The templates for each of the children simply contain a sentence describing what each page will contain in the future so I did not bother to attach them. They are valid, simple XML files.

<atlassian-plugin key="${project.groupId}.${project.artifactId}" name="${}" plugins-version="2">
        <vendor name="${}" url="${project.organization.url}" />
        <param name="plugin-icon">images/pluginIcon.png</param>
        <param name="plugin-logo">images/pluginLogo.png</param>
        Add our i18n resource 
            * i18n name: The localisation key for the human-readable name of the plugin module 
    <resource type="i18n" name="i18n" location="spacebp"/>
    <!-- add our web resources -->
    <web-resource key="spacebp-resources" name="spacebp Web Resources">
        <transformation extension="soy">
            <transformer key="soyTransformer">
            <transformation extension="js">
                <transformer key="jsI18n"/>

        <resource type="download" name="spacebp.css" location="/css/spacebp.css"/>
        <resource type="download" name="spacebp.js" location="/js/spacebp.js"/>
        <resource type="download" name="dialog-page.js" location="/soy/"/>
        <resource type="download" name="images/" location="/images"/>
        <dependency>com.atlassian.confluence.plugins.confluence-create-content-plugin:space-blueprints</dependency>   <!-- This dependency is not required for confluence 5.4+ -->
        create-space-blueprint-item allows the dialog launched by clicking the global "Create space" button to be extended.
            * i18n-name-key: (required) the i18n key for the name of the Blueprint that will be displayed in the dialog
            * description: (required) the i18n key for the description of the Blueprint that will be displayed in the dialog. May end up being used in searches
            * resource: (required) the icon to be displayed in the dialog, must be a 200 x 150 px PNG
            * blueprintKey: (optional) if present, binds this web-item to the blueprint with this key. If omitted, no binding occurs and custom JavaScript + Java must create the content
    <web-item key='sensor-space-blueprint-item' i18n-name-key=''
        <description key=''/>
        <resource name="icon" type="download" location="/images/watchtower.png" />
        <param name='blueprintKey' value='sensor-space-blueprint'/>
        content-template defines an XML resource in Confluence Storage-Format.
            * key: (required) referenced by the respective <blueprint>
            * i18n-name-key: (optional) used only when viewing this plugin in the Plugin Manager
            * description: (optional) used only when viewing this plugin in the Plugin Manager
              * resource: (required) the XML file containing the template content
            * context-provider: (optional) if present, will provide extra key-value pairs to be substituted against <at:var> instances in the template
    <content-template key="sensor-space-homepage-template" i18n-name-key="">
        <description key=""/>
        <resource name="template" type="download" location="/xml/wt-sensor-home.xml"/> <!--  Home page (checklist) -->
    <content-template key="sensor-space-data-template" i18n-name-key="">
         <description key=""/>
         <resource name="template" type="download" location="/xml/data.xml"/> <!--  Data page -->
    <content-template key="sensor-space-timeline-template" i18n-name-key="">
         <description key=""/>
         <resource name="template" type="download" location="/xml/timeline.xml"/> <!--  Timeline page -->
    <content-template key="sensor-space-geninfo-template" i18n-name-key="">
         <description key=""/>
         <resource name="template" type="download" location="/xml/general_information.xml"/> <!--  General information page -->
         blueprint groups together the main blueprint concepts:
            * index-key: (required) this is the name of the label that will be added to all content created from this blueprint, and used to
                           bring this content together on the index page.
            * index-template-key: (optional) this is the moduleKey of the <content-template> that will be used to create an index page.
                                    If none is provided, a default template will be used.
            * create-result: (optional) can be assigned the value of "view" or "edit".
                "view": cause the editor to be bypassed - the required content will be created and the user immediately redirected to viewing it
                "edit": user will be sent to the editor pre-filled
            * i18n-index-title-key: (optional) the i18n key for the title of the index page. Defaults to create-dialog-web-item name if none specified.
    <space-blueprint key="sensor-space-blueprint" i18n-name-key="">
        <content-template ref="sensor-space-homepage-template"> <!-- Home -->
             <content-template ref="sensor-space-data-template"/> <!-- Child Page -->
              <content-template ref="sensor-space-geninfo-template"/> <!-- Child Page -->
             <content-template ref="sensor-space-timeline-template"/> <!-- Child Page -->
        <dialog-wizard key="sensor-space-blueprint-wizard">
            <dialog-page id="exampleSpaceId"
</atlassian-plugin> Space Blueprint with a preconfigured Sensor Space a Sensor Space sensor Spaces this blueprint to create a Sensor Space Page Space Home page that contains data analysis, test and sample data archives, and expected data volume metric pages Info information for the sensor, to include background, capabilities, description, docs, resources and stakeholders timeline of events for all sensor related activities, to include meetings, boards, analysis and deliveries pages will be shown here Name sensorname Description describe this sensor
{namespace Confluence.SpaceBlueprints.sensor}
 * Dialog form template
 * @param atlToken the XSRF token to send with the form
 * @param? fieldErrors the map of errors to display keyed by field name
 * @param? name initial value for the name field
 * @param? key initial value for the key field
{template .dialogForm}
<form action="#" method="post" id="decisions-form" class="common-space-form aui">
    {call Confluence.Templates.Blueprints.CreateSpace.createSpaceFormFields}
        {param showSpacePermission: false /}
        {param fieldErrors: $fieldErrors /}
        {param name: $name /}
        {param key: $key /}
    /** Additional Create Space dialog */
        <div class="field-group">
            <label for="space-homepage-heading">{getText('')}</label>
            <input class="text" type="text" id="text-input" name="spaceHomepageHeading" title="Text input" 
        <div class="field-group">
            <label for="space-description">{getText('')}</label>
            <textarea id="space-description" class="textarea long-field" rows="3" type="text" name="spaceDesc"
    /** End Additional Create Space dialog */
    <input type="hidden" name="atl_token" value="{$atlToken}" />
AJS.bind("blueprint.wizard-register.ready", function () {
    function submitExampleSpace(e, state) {
        state.pageData.ContentPageTitle = + " " + AJS.I18n.getText(""); 
        return Confluence.SpaceBlueprint.CommonWizardBindings.submit(e, state);
    function preRenderExampleSpace(e, state) {
        state.soyRenderContext['atlToken'] = AJS.Meta.get('atl-token');
        state.soyRenderContext['showSpacePermission'] = false; 
    Confluence.Blueprint.setWizard('com.sensor.plugins.tutorial.confluence.spacebp.spacebp:sensor-space-blueprint-item', function(wizard) {
        wizard.on("submit.exampleSpaceId", submitExampleSpace);
        wizard.on("pre-render.exampleSpaceId", preRenderExampleSpace);
        wizard.on("post-render.exampleSpaceId", Confluence.SpaceBlueprint.CommonWizardBindings.postRender);

I I would greatly appreciate any help or assistance with this problem.

1 answer

Bueller? Bueller? Bueller?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Tuesday in Confluence

Confluence Admin Certification now $150 for Community Members

More and more people are building their careers with Atlassian, and we want you to be at the front of this wave! Important Dates Start the Certification Prep Course by 2 April 2019 Take your e...

196 views 2 10
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you