My Oracle Support Banner

SitePlanTree Entry Randomly Not Published With Page Asset (Doc ID 1569926.1)

Last updated on MAY 31, 2024

Applies to:

Oracle WebCenter Sites - Version 7.6.2 and later
Information in this document applies to any platform.


On :  7.6.2 version, WebCenter Sites

SitePlanTree entry randomly not published with Page asset  

It was noticed that the tag was failing in the Production environment when used in a template that interacts with Page assets.  Upon further investigation, it was found that the Page asset that caused the Template to throw an exception was missing an entry in the SitePlanTree table.  A query was run on the Production database and it was found that there are around 300 Page assets which are currently missing entries in the SitePlanTree table.  The same query was run against our Staging database which is for the server where the Production content is authored prior to publishing to Production.  67 Page assets were found missing entries in the SitePlanTree.  This was confirmed for both results by running the Check Assets tool in the Support Tools website for each environment.  In addition, there are assets on the Production environment missing SitePlanTree entries, while the versions on Staging are not.  If a Page asset which has the SitePlanTree entry on Staging but not on Production is re-published, then the SitePlanEntry entry is correctly added on Production.

Page assets that were published to a publish destination should have a SitePlanTree entry.

The issue can be reproduced at will with the following steps:
This can be done in the FirstSiteII site and you can assume an initial SitePlan configuration as the following:

- Placed Pages
   -  TopParent
        - Parent001
            - Child 1
            - Child 2
            - Child 3
- Unplaced Pages

Assuming the initial SitePlan pages have been published to the destination,
and the destination reflects the same configuration, perform the following
steps on the source environment:

i) In the SitePlan tab, right-click the Parent001 page and select Place page.
ii) In the Place Page screen, click the Remove checkbox next to the Child 3
page and click Save.
iii) Approve the Parent001 page for publish.
iv) Publish to the destination.




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.