Content of a page not visible after saving Edited

There is a specific page on our Confluence site which the user is unable to view after saving although there is content in the page. 

When we manually type in on the page, that content appears. 

Confluence is running on v6.0.4

Please advise. 

1 answer

0 votes
Ann Worley Atlassian Team Sep 19, 2017

Hi Pooja,

I understand there is a page in your instance that a user is unable to view after saving.

Please let me know more:

  • Does the user see an error message when attempting to view the page? (Please post a screen shot of what the user sees when they go to the page.)
  • Does it matter which browser is used?
  • Is the page visible to other users after it is saved?
  • Please provide the storage format of the page:
  1. Click on the ellipsis () in the top right-hand corner and select View Storage Format from the dropdown.  
  2. Copy the storage format to your clipboard and paste it in a code block on this thread.



Hello Ann, 

The page is visible after saving but the content in it is not.

No, the user does not see any error message. 

It is not just with the user but even me as confluence admin, i am unable to view the content after saving. Although it is visible in edit mode. 

Snapshots attached. saved mode.PNGedit mode.PNG


The issue is same across different browsers. 

Storage format code>

<p><ac:structured-macro ac:name="toc" ac:schema-version="1" ac:macro-id="feb707d6-293e-49e6-9b99-b30aacee53c4" /></p>
<p><br /></p>
<div class="assistive">
<p class="assistive">In order to deploy the API Proxy or Web Service Proxy onto sit,uat,svp,sandpit and prod the CARA plans will be used to execute the job.</p>
<p><br /></p><ac:structured-macro ac:name="info" ac:schema-version="1" ac:macro-id="7c66db9b-da96-48e9-a51b-a16c2fe05d74"><ac:parameter ac:name="title">CARA Login Page</ac:parameter><ac:rich-text-body>
<p><a href="" rel="nofollow"></a></p></ac:rich-text-body></ac:structured-macro>
<div class="confluence-information-macro confluence-information-macro-information conf-macro output-block">
<div class="confluence-information-macro-body">
<h4>Step 1 : Create Template Categor<strong>y</strong></h4>
<p>For Registraion, the template category need to be create for the API Name. The naming standards for the template category has to be '<span style="color: rgb(51,51,0);"><em>&lt;Release Number/Name&gt; API Name</em></span>'.</p>
<p>The template consists of different processes. These processes have been described in&nbsp;<a rel="nofollow" href="">Designing CARA Artefacts</a>. Screenshot shows the two process that need to be added for&nbsp;<strong>Proxy Registration</strong>&nbsp;and&nbsp;<strong>Promote KPS Artefact.</strong></p>
<p>Also environment specific templates may have to be created to cater for environment specific processes and the naming standard is '<em>&lt;Environment Name&gt;</em>'</p>
<p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><ac:image ac:width="825"><ri:attachment ri:filename="image2017-4-21_13-11-16.png" /></ac:image></span></p>
<p><br /></p>
<h4><strong>Step 2 : Create Deployment Plan</strong></h4>
<p>After a template is created, a deployment plan will be created. Click Releases &rarr; Deployment Plans by Project &rarr; New Deployment Plan.</p>
<p>Deployment Plan has to be created from the above created template category and deployment.</p>
<p>It will have below naming conventions -</p>
<p>Name:&nbsp;<em>&lt;Asset Type&gt;</em></p>
<p>Build:&nbsp;<em>&lt;Asset ID&gt;</em></p>
<p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><ac:image ac:width="376"><ri:attachment ri:filename="image2017-4-21_13-13-9.png" /></ac:image></span></p>
<p><br /></p>
<h4><strong>Step 3 : Verify Deployment Steps</strong></h4>
<p>Once the plan is created, navigate to deployment steps and make sure the processes that were added in template categories are reflected in your plan</p>
<p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><ac:image ac:width="735"><ri:attachment ri:filename="image2017-4-21_13-16-16.png" /></ac:image></span></p>
<p><br /></p>
<h4><strong>Step 4 : Update Input parameters</strong></h4>
<p>To deploy an application, a release engineer will update the required input parameters for that process</p>
<p>Navigate to each process and update the required missing values</p>
<p>a) API Gateway Deployment&nbsp; will need below inputs</p>
<p><br /></p>
<div class="confluence-information-macro confluence-information-macro-information conf-macro output-block">
<div class="confluence-information-macro-body">
<p><strong>Input Values</strong>&nbsp;:</p>
<li>API_NAME: It should be &lt;domainName&gt;-&lt;subDomainName&gt;-v1-&lt;apiproxy or wsproxy&gt;.</li>
<li>ARTIFACT_BUILD_NO : Artefact version of the released assets of the source code in artifactory</li>
<li>OVERRIDE_ARTIFACT : Artefact version of overrides that is released in artifactory.</li></ol></div></div>
<p><br /></p>
<p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><ac:image ac:width="761"><ri:attachment ri:filename="image2017-4-21_13-16-59.png" /></ac:image></span></p>
<p><br /></p>
<p>b) Promote KPS artefacts will need below inputs -</p>
<p><br /></p>
<div class="confluence-information-macro confluence-information-macro-information conf-macro output-block">
<div class="confluence-information-macro-body">
<p><strong>Input Values</strong>&nbsp;:</p>
<li>API_NAME : Can have values as 'internal-gateway or 'external-gateway' for API Type internal and external respectively</li>
<li>KPS_ARTEFACT_NO&nbsp;: Artefact version of KPS that need to be promoted. In case you don't have to promote KPS you can also set it to 'None' which will don't update any KPS</li></ol></div></div>
<p><br /></p>
<p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><ac:image ac:width="820"><ri:attachment ri:filename="image2017-4-21_13-17-36.png" /></ac:image></span></p>
<h4><strong>Step 5 :&nbsp;Run Deployment</strong></h4>
<p>Click on Deploy button and it will ask for Deployment Name. Select the environment and click Save. It will start the deployment. Naming convention is &lt;apiname&gt;-artefact-&lt;artefact no&gt;-overrides-&lt;override artifact&gt;-kps-&lt;KPS artefact no&gt;</p>
<p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><ac:image ac:width="456"><ri:attachment ri:filename="image2017-4-21_13-55-50.png" /></ac:image></span></p>
<h4><strong>Step 6 : &nbsp;Validate the Deployment</strong></h4>
<p>You can verify your deployment is successful or not</p>
<p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><ac:image ac:height="250"><ri:attachment ri:filename="image2017-4-21_13-57-29.png" /></ac:image></span></p>
<p>Note : In case you are not promoting the KPS artefact and KPS_ARTIFACT_NO is set to 'None', you will see that Promote KPS Artefact Status as Done but it will not execute it.</p>
<p><br /></p></div>
<p>&nbsp;Pooja Pandey</p>
<p>Another test</p>
<p><br /></p>
<p><br /></p>
<p><br /></p>

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Dec 18, 2018 in Confluence Cloud

Happy holidays from our team to yours!

Hi Community!  2018 was filled with changes for our team, both big and small, and we've taken a lot of time to both celebrate our wins and recognize areas of improvement. One thing that we're a...

475 views 3 18
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