1. Building Sites with Oracle Content Management
  2. Developing for Sites
  3. Customize the Controller File
  4. Controller File Sections That Should Not Be Customized

Controller File Sections That Should Not Be Customized

Certain sections of the controller file are processed by the Oracle Content Management server in order to use the CDN and to define URL caching segments. These are noted inline in the sample below. 

<!DOCTYPE html>
<html>
<head>
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="initial-scale=1">
<script type="text/javascript">
<!-- The global variable SCSCacheKeys will be inserted at this location -->
 
 
var SCS = { sitePrefix: '/SampleSite/' };
<!-- A variable denoting the location of the CDN will be injected at this location. -->
<!-- Additionally, the prefix "/site" will be inserted before the site name segment. This is to support legacy controller files. -->
 
 
</script>
<script src="/SampleSite/_sitesclouddelivery/renderer/controller.js"></script>
<!-- The src value will be updated to use the CDN if this syntax is used. -->
 
 
</head>
<body id="scsControllerBody"><noscript>This site requires JavaScript to be enabled.</noscript>
<!-- The id of the <body> should not be changed. -->
 
 
<img id="scsWaitImage" style="display: none; margin-top: 5%; margin-left: auto; margin-right: auto;" src="data:image/png;base64,..." />
<!-- The id of the wait image tag should not be changed -->
 
 
</body></html>