Custom Elements 8-5
8.4 Legacy Custom Element Compatibility
All custom element forms created with Site Studio releases 10gR3 10.1.3.3.2 and earlier are not compatible with Site Studio 11gR1 and will need to be manually
upgraded re-authored. The primary reason for not maintaining backward compatibility is Site Studios prior dependency upon Internet Explorers proprietary
window.external functionality. The window.external functionality of custom elements used in Site Studio release 10gR3 and earlier is blocked at the point of code execution
and is not easily duplicated in a cross-browser and cross-platform DHTML solution.
The upside to breaking backward compatibility is that current custom elements are much more flexible, and better integrated into the Contributor application architecture
in addition to being a cross-browser and cross-platform solution.
This section contains the following topics:
■
Section 8.4.1, Detecting Legacy Custom Element Forms
■
Section 8.4.2, Upgrading Legacy Custom Elements
8.4.1 Detecting Legacy Custom Element Forms
A custom element form created using Site Studio 10gR3 10.1.3.3.2 or earlier that is, a legacy custom element form, if loaded into the Contributor application with the
SSValidateCustomElements flag is set to true, will be detected. An error message will be displayed in its place within the contributor form.
The Contributor application does this by first downloading the custom element form, parsing the source code, and determining whether or not the custom element form is
compatible with the new Contributor application.
The functionality and overhead to detect legacy custom element forms is unnecessary on production installations and is turned off by default. To turn on legacy custom
element form detection, add the following line to Oracle Content Servers config.cfg file and restart the server:
SSValidateCustomElements=true ElementAPI.GetSiteoptions;
Displays the Choose Website picker UI. ElementAPI.GetSectionoptions;
Displays the Choose Website Section picker UI. ElementAPI.GetColoroptions;
Displays the Color picker UI. ElementAPI.GetFontoptions;
Displays the Get Font picker UI. ElementAPI.GetSearchResults options;
Displays the Oracle Content Servers Get Search Results page.
ElementAPI.GetQueryTextoptions; Displays the Get Query Text UI.
ElementAPI.CaptureQueryoptions; Displays the Oracle Content Servers Capture
Query page. ElementAPI.GetHyperlinkoptions;
Displays the Hyperlink Wizard UI. ElementAPI.FocusFormoptions;
Focuses the parent window thereby blurring the Element window.
Function Description
8-6 Oracle Fusion Middleware Technical Reference Guide for Site Studio
8.4.2 Upgrading Legacy Custom Elements
Any custom element forms created using a Site Studio release up to 10gR3 10.1.3.3.2 are not compatible with Site Studio 11gR1. They must be manually upgraded and
re-authored. The primary reason for not maintaining backward compatibility is Site Studios prior dependency on Internet Explorers proprietary window.external
functionality due to the ActiveX control used for the legacy Contributor application. This functionality was removed from Site Studio as a result of the
browser-independent, JavaScript-based Contributor application that is used in Site Studio 10gR3 10.1.3.3.3 and higher including 10gR4 and 11gR1.
9
Idoc Script Extensions 9-1
9
Idoc Script Extensions
Site Studio uses several Idoc Script extensions that are used to run a web site:
■
Section 9.1, About Idoc Script Extensions
■
Section 9.2, wcmPlaceholder
■
Section 9.3, wcmElement
■
Section 9.4, wcmListStart
■
Section 9.5, wcmListEnd
■
Section 9.6, wcmListElement
■
Section 9.7, wcmListRowCount
■
Section 9.8, wcmDynamicList
■
Section 9.9, wcmIncludeElement
■
Section 9.10, wcmDynamicConversion
■
Section 9.11, wcmGetListAsResultSet
■
Section 9.12, wcmFragment
■
Section 9.13, wcmUrl
■
Section 9.14, ssIncludeXml
■
Section 9.15, ssGetDocInfo
■
Section 9.16, ssGetXmlNodeCount
■
Section 9.17, ssIncDynamicConversion
■
Section 9.18, ssIncDynamicConversionByRule
■
Section 9.19, ssIncDynamicConversionByRulesEngine
■
Section 9.20, ssIncInlineDynamicConversion
■
Section 9.21, ssIsNativeDoc
■
Section 9.22, ssRandom
■
Section 9.23, ssGetNodeProperty
■
Section 9.24, ssGetWebsiteNodeType
■
Section 9.25, ssGetCoreMajorVersion
■
Section 9.26, ssSplitString
■
Section 9.27, ssGetWebsiteName
9-2 Oracle Fusion Middleware Technical Reference Guide for Site Studio
■
Section 9.28, ssGetSiteProperty
■
Section 9.29, ssGetFirstNodeId
■
Section 9.30, ssGetRelativeNodeId
■
Section 9.31, ssLoadSiteNavResultSet
■
Section 9.32, ssGetServerRelativeUrl
■
Section 9.33, ssGetServerRelativePath
■
Section 9.34, ssGetUrlPageName
■
Section 9.35, ssGetNodeLabel
■
Section 9.36, ssGetNodeLabelPath
■
Section 9.37, ssGetAllSites
■
Section 9.38, ssLink
■
Section 9.39, ssNodeLink
■
Section 9.40, ssWeblayoutUrl
9.1 About Idoc Script Extensions
Kategori