WebCenter Sites Release Notes

11g R1 BP1 (



1.0 What’s New in Oracle WebCenter Sites 11gR1. 3

1.01 Usability Improvements. 3

1.02 New Look and Feel 3

1.03 New Page Building Capabilities. 4

1.04 New Bulk Operations. 4

1.05 New Search Capabilities. 4

1.06 New Dashboard. 4

1.07 Session Replication. 4

1.08 TempObjects Cleanup. 4

1.09 Security Updates. 4

2.0 Deprecated Functionality. 6

3.0 Limitations. 7

3.01 Asset Type Name Restrictions. 7

3.02 API 9

3.03 Browser Support. 9

3.04 BulkLoader / BulkApprover. 9

3.05 CatalogManager. 10

3.06 CatalogMover. 10

3.07 Contributor UI 10

3.08 CSDT. 11

3.09 Database. 11

3.10 Install 11

3.11 Localization. 11

3.12 Page Cache - inCache. 12

3.13 Publishing. 12

3.14 REST API 12

3.15 Satellite Server. 12

3.16 Search. 13

3.17 Site Capture. 13

3.18 Site Launcher. 13

3.19 Site Management. 13

3.20 Sites DocLink. 14

3.21 Sites Desktop. 14

3.22 Tags. 14

3.23 Template / Site Entry / CS-Element. 14

4.0 General Issues and Workarounds. 14

4.01 API 14

4.02 Admin Interface. 15

4.03 Analytics Integration. 15

4.04 AssetCache. 15

4.05 Browser Support. 16

4.06 Caching - Satellite Server. 16

4.07 CKEditor. 16

4.08 Contributor UI 16

4.09 CSDT. 17

4.10 Engage. 18

4.11 Flex Assets. 18

4.12 Installation / Upgrade. 18

4.13 Performance. 19

4.14 Publishing. 19

4.15 REST API 19

4.16 Revision Tracking. 20

4.17 Site Capture. 20

4.18 Site Launcher. 20

4.19 Sites Desktop. 21

4.20 Sites DocLink. 21

4.21 Sites Explorer. 21

4.22 Start Menu. 21

4.23 Tags. 21

4.24 WEM Admin. 22

4.25 WEM Framework. 22

4.26 Workflow.. 22

4.27 User Mgmt - LDAP. 22

4.28 XMLPost. 22


1.0 What’s New in Oracle WebCenter Sites 11gR1

The latest version of Oracle WebCenter Sites (earlier known as FatWire Content Server), represents the most advanced version of our product in terms of design, functionality, and usability. The Oracle WebCenter Sites 11gR1 release includes a host of new features to support drag-and-drop page creation and asset management. Additionally, there are updates to the look and feel of the administrative interface, improved search capabilities.

1.01 Usability Improvements

Usability is a primary theme of the latest release. Efforts have been made to simplify interfaces and provide the right functionality at the right time.

·       New tab-based Contributor Interface – the new Contributor Interface for marketers and business users provides a browser-like interface to efficiently manage multiple assets simultaneously. Assets can be opened in individual tabs and out-of-the-box revision tracking prevents asset changes from being overridden by concurrent edits.

·       Improved support for drag and drop it is now possible to drag content from search results and sidebar trees to both asset forms and page slots. Drag and drop can also now be used to quickly order the pages of a site plan.

·       New search results views – view search results as either lists or thumbnails. Search results can be docked to make them conveniently available for dragging (e.g., to a page slot).  The dock automatically appears on the active tab.

·       Improved approval process – available out-of-the-box, assets as well as their dependencies can now be approved with a single operation.

·       Better ease of use – the integrated WEM bar is now easier to use. A single click opens the WEM bar, and it will remain open until manually closed.

1.02 New Look and Feel

The Contributor Interface has been given a modern look and feel with easily accessible controls and an updated color palette. Similarly, the Advanced, or Administrative, interface has been updated to better match the Contributor Interface.

1.03 New Page Building Capabilities

The page building model and process has been redesigned. The management of page content can be accomplished using drag-and-drop functionality in combination with “dockable” search results, sidebar trees, and strategically available toolbars. Once page creation is initiated, content can be dragged to predefined slots. Slots can be constrained by asset type and role-based user permissions per slot can be assigned. Non-technical users can easily control the presentation of content with graphical layouts and predefined arguments.

1.04 New Bulk Operations

New capabilities to operate on multiple assets efficiently, including bulk deletion, approval, and bookmarking. These operations are conveniently available from search results screens. Operations can be executed by selecting multiple assets and pressing a single button.

1.05 New Search Capabilities

Updated capabilities to locate assets (e.g., with a keyword) from the Contributor Interface’s search bar, including a convenient, embedded control to search by asset type.

1.06 New Dashboard

A dashboard is now provided out-of-the-box. Widgets to manage assignments, bookmarks, and checkouts are included. Widgets can be rearranged on the dashboard using simple drag-and-drop.

1.07 Session Replication

Session replication issues in the management user interfaces are resolved with release (14291305 and 14290365)

1.08 TempObjects Cleanup

To clean up the TempObjects table, you must enable the event CleanTempObjects in the SystemEvents table by changing the value of 0 in the enabled column to 1. By default, the event will run at midnight and keep the last 5 days of data, to change this default, add the property cs.TempObjectsDaysToKeep to the futuretense.ini and specify the number of days to retain this data. This change is available from (14291528)

1.09 Security Updates

Request Authentication filter has been added to Sites to prevent CSRF attacks.

Enabling/Disabling the filter

The request authentication filter will be enabled OOB after upgrade or new installation. The installer adds the following in web.xml.


<filter-name>Request Authentication Filter</filter-name>





<filter-name>Request Authentication Filter</filter-name>




ReqAuthConfig.xml file in <deploy>/WEB-INF/classes folder can be used to configure the filter properties.

Updates to REST API

All REST requests must have a header with “X-CSRF-Token” as both key and value to be authenticated as valid requests.

Update to CatalogManager

Any request going to catalog manager with the command parameter (ftcmd) must be a POST request if the command is not one of the following:

·         exportlog

·         exportForm

·         logout

·         selectFromTable

·         selectCount

·         mirrorgetconfig

·         listtables

·         retrieve

·         retrievebinary

·         pingdb

·         interrogatetbl

·         checksession

·         history

·         retrieverevision

On writing form post related code

All form elements must use satellite:form(in jsp) or SATELLITE.FORM(in xml) tags for POST requests

Update to Install Guide for trusted CAS redirect using service parameter

On successful login to Sites, CAS redirects the user to the requested service. For additional security, the ability to validate the requested service before redirecting the user exists by specifying the list of trusted/permitted URLs in the WEB-INF/spring-configuration/customBeans.xml file.  The URLs can be in either of the following formats: 

1.       Exact URL [http://hostname:port/cs/wem/fatwire/wem/Welcome]

2.       Matching URL '/*' at the end indicates any URL that has the same prefix as specified [http://hostname:port/SitesWebapp/*]

To allow users to access trusted resources using IP address, specify those URLs as well. 

Customization in Upload Attribute Editor
Following steps should be followed to add custom logic to optionally validate an uploaded file:

1.       Create a jsp element with the name ValidateFileUpload in the path CustomElements/fatwire/ui/util

2.       The file name and the byte array containing the uploaded file data are available in the request scope and can be retrieved by calling ics.GetVar("filename") and ics.GetVar("filebytes") in jsp element.

3.       Write your custom logic to ensure that the uploaded file data is acceptable.

a.       If the file data is valid then the developer must set the variable "fileValidated" equals to true by calling ics.SetVar("fileValidated","true"). This would ensure that the file will be uploaded to the Sites server.

b.      If the file data is invalid then the developer must set the variable "fileValidated" equals to false by calling ics.SetVar("fileValidated","false"). This would reject the data uploaded by the user and an error message will be shown to the user.

Sample code with the exception of the validation logic is available in the base element fatwire/ui/util/ValidateFileUpload. This element should not be modified and custom code must be written in the custom element as specified above

Preventing Header Manipulation
Sites has two properties called bs.validheadernames (whitelist) and bs.invalidheadernames(blacklist). These properties can be used to check if the header sent to BlobServer is a valid header. These properties can be specified as comma-separated values in the futuretense.ini to prevent malicious header manipulation. An administrator can add the valid and invalid headers allowed by BlobServer in the futuretense.ini. If both properties are specified in futuretense.ini, bs.validheadernames will take the precedence.

2.0 Deprecated Functionality

The functionality below is removed effective this release:

·        Dash UI and InSite UI have been removed, they are replaced with Contributor UI

·        URL attribute data type has been removed, use BLOB instead.

·        RememberMe attribute editor has been removed, use TypeAhead or PickFromTree instead.


The functionality below is deprecated effective this release:

·        The ability to manage new content assets of type – basic, flex, page and engage - the Admin UI (formerly called the Advanced UI). You should now access this functionality from the Contributor UI.

·        Mirror Publishing, use Real Time publish instead

·        Old caching implementation, use the new inCache based implementation (this is active upon install by default)

·        SOAP based web services are being deprecated, use the public REST API.

·        Page Debugger, users should look to IDE integration for JSP debug capabilities. DebugServlet is not deployed.

·        Usage of asset API from stand alone Java applications is deprecated, use REST API instead.

·        Support for JBoss is not available in this release

·        Support for Safari is not available in this release, it is planned for a future release

3.0 Limitations

3.01 Asset Type Name Restrictions

The following lists display the asset type names used by Oracle WebCenter Sites:

·        All administrative database tables created by WebCenter Sites which were added post release 7.5 of Content Server will be prefixed with FW_. Asset types should not be created with a prefix of FW_.

·        If there are any asset types that were created using names in our Standard Asset list, upgrade scripts will encounter errors. Manually back up their data and elements before starting the upgrade process to preserve these assets. If you install the sample sites, do not use the Sample Site asset type names listed below when creating custom asset types.

Standard assets - These asset types are created by default:






















Asset Types installed by the avisports Sample Site:









Asset Types installed by the FirstSite II Sample Site:































Restricted Names for Asset Types:

The following names (in alphabetical order) are reserved for WebCenter Sites’ use and must not be assigned to custom asset types:



























































































































































































































Any name that starts with VMz





































·      For a given database, the name of a flex asset type must have ten characters less than the maximum number of characters that are allowed for database table names.

·      For a given database, the name of a basic asset type must have five characters less than the maximum number of characters that are allowed for database table names.

·         Attributes “Start Date” and “End Date” are reserved as Sites uses these for out of the box assettypes and should not be used in user created AssetMaker Assets (14725212)

3.02 API

·      Dynamic loading of new DataSource using loadproperty tag is not supported.


·      When Asset API is used in a standalone app and called from main method, it does not automatically terminate after the Asset API call is complete like other Java apps. The reason is because Asset API behaves like another cluster member of Sites and boots up all the events in the background. To terminate, code should call System.exit(0)

3.03 Browser Support

·      If Apache Web Server is not configured to use HTTP1.1, pages will be cached by IE


·         In Internet Explorer, the Tools > Internet Options > Settings > Every Visit to the page must be set to true.


3.04 BulkLoader / BulkApprover

·      Without validation, the utility ignores versioning on content. With validation, if the content type is under versioning, it will not update the content.


·      Page cache is not flushed by BulkLoader. as page cache is persistent, the cache should be cleared prior to running BulkApprover


·      BulkApprover requires running WebCenter Sites as it is implemented via Sites tags


·      Flex filters are not fired (for example, FieldCopier)


·      BulkLoader does not support BLOBs; for this you should use XMLPost


·      Start and End date can't be specified nor configured for bulk transferred assets using BulkLoader (14289184)


·      BulkLoader should not be executed while WebCenter Sites is running


·      When assets are added using BulkLoader, the assets will not be indexed in Lucene. You will need to re-indexed after import. (14290298)


·      Running multiple BulkLoader instances is not recommended unless it is performing the same operations for example, all insert or all update and multiple source tables do not refer to the same asset. Doing so will cause data corruption.

3.05 CatalogManager

·      If revision tracking is enabled for an object table, and then you delete the table using CatalogManager, WebCenter Sites still thinks that the table is being revision tracked.


·      Sites allows the value in the tablename column in the SystemSQL table to be null. However, for resultset caching to work properly, this value must be specified.


·      You cannot log into Sites if the username you are using to log in has the same "id" value of a different user in the SystemUsers table. For example, DefaultReader has an ID value of 2. If you create a user with the username "2," that user cannot log in.

3.06 CatalogMover

·      CatalogMover does not export from columns that hold BLOBS. For example, a table is created with a column using the data type specified by the property cc.blob. An image is uploaded to the table. When CatalogMover exports the row, the image is not written to the export data.

3.07 Contributor UI

·      Use of the browser back button is not supported in this release


·      Approval and Delete listing screens shows references based on evaluation of the layout template. If the layout template execution fails for any reason, the assets presented in the tables may not be correct.  (14290251)


·      Page Layout allows for multiple levels of nested slots. However the slot properties are only for the first two levels. The tool allows drag and drop to multiple levels however. (14289783)


·      Drag and drop in Contributor UI will not work if the page uses an iframe (14289662)


·      TextArea attribute editor is not supported for editing in Web Mode, CKEditor should be used


·      Clarkii Image Editor is not supported in Web Mode


·      Use of IE in Compatibility Mode is not supported

3.08 CSDT

·      For a CSDT export created from Content Server 7.6 patch 2, import will not succeed if it contains Page Assets. The recommendation is to upgrade to Sites 11gR1 and then re-export using the CSDT Plug-in for this version before the next import.


·      CSDT does not support assets enabled for revision tracking             

3.09 Database

·      Sites 11gR1 uses the length specification for strings, to specify the underlying database column sizes in bytes. When specifying the max length of a text field, keep in mind that multi byte characters will need more bytes per character.

3.10 Install

·      When cs.use.short.jsp.names=false (the new default value - used to be true by default), JSP elements that contain dots (such as "www.xyz.com/common/flexLinkButton") will not get deployed properly. They will be deployed without the .jsp extension so the AppServer won't know how to run them. To work around this, clients who use dots in their jsp element names should set cs.use.short.jsp.names=true.


·      If your installation of WebCenter Sites fails, take the following steps before re-executing the installation:

o   Drop the database tables

o   Undeploy the .ear/.war file

o   Delete the Sites installation folder

o   Restart the Application / Web Servers


·      When installing a Web Server in between Remote Satellite Server and Sites, you must set the cookie header property http.protocol.single-cookie-header=true in the httpaccess.properties file and place it in the <remote_satellite_server install folder>/WEB-INF/classes folder


·      For security reasons, we recommend that only internal access is provided for the following servlets:

o   Install

o   HelloCS

o   CatalogManager

o   TreeManager

o   CacheServer

o   Inventory

3.11 Localization  

·      Non-ASCII characters should not be used in the following Form Name Fields (14290733):

o   Site

o   Template

o   Site Entry

o   CS-Element

o   Attribute

o   Recommendation

o   Segment

·         Only use alphanumeric characters for the following (14290733):

o   AssetTypes

o   Asset Definitions

o   Asset Subtypes

o   Legal Arguments


3.12 Page Cache - inCache  

·      Persisting cache to disk wipes out Last Access Time and hit count on RSS            


·         It is recommended to initialize inCache by accessing one page of the site from each of Sites’ cluster members.

3.13 Publishing

·      Ensure that the maximum number of open file handles for your publish destination Operating System is set to 65000, the source system should be at least 32000. These numbers are only a guideline and may need to be adjusted based on type of data and size of publish operations.


·      Export to Disk - Exported page effectively rendered with wrong template when using SIMPLENAME. Contact support for a utility to remove the duplicate pub keys               


·      The INPUTFORM tag support is limited in ASSET API when creating basic asset types via REST. As a result, unsupported INPUTFORM TYPES are interpreted as <INPUTFORM TYPE="TEXT" WIDTH="48" REQUIRED="YES"/>. In order for users to see proper asset type attributes in WebCenter Sites UI's, the INPUTFORM tags need to be updated in the asset descriptor file through the database (AssetType table in Sites Explorer).                


·      Setting BufferingConfig.xml to use multiple threads is not supported


·      It is possible to create duplicate fw_uid if you perform a GET and use PUT on the resulting bean when using REST API. In this scenario a new asset with a different asset id will be created but it will still have the same fw_uid. The workaround is to clear the fw_uid in the bean before PUT.


·      When using REST API the following message is displayed on the server side and can be safely ignored:

com.sun.jersey.core.impl.provider.xml.SAXParserContextProvider getInstance

WARNING: JAXP feature XMLConstants.FEATURE_SECURE_PROCESSING cannot be set on a SAXParserFactory. External general entity processing is disabled but other potential security related features will not be enabled.

org.xml.sax.SAXNotRecognizedException: http://javax.xml.XMLConstants/feature/secure-processing

3.15 Satellite Server

·      Sites and Satellite Server have to be in the same time zone     

3.16 Search

·      Lucene fails to index text that comes after dashes, underscores and other special characters


·         If indexing takes longer than the cs.timeout setting, exceptions will be thrown and indexing may be in an unstable state. The timeout should be adjusted based on the size of index


·      SQL Server only stores milliseconds up to 3.33 millisecond precision with data type DATETIME 


·      WebCenter Sites does not support indexing legacy Word95 documents and throws exceptions in the logs.       


·      Lucene standard analyzer treats words differently if they contain a hyphen (-)

For example:    

ABC-DEF-HIJ is sometimes indexed as one word and sometimes indexed separately as "ABC" and "DEF-HIJ", when this occurs, searching for "ABC-DEF-HIJ" will not always return the proper results.               


·      Search for text within XML or HTML tags is not supported          

3.17 Site Capture

·      Site Capture application needs to run on context root. This is required to enable the preview functionality to render pages inside the archive which may have any context root. The application needs to be deployed on its own application server.


·         Status messages are not shown in the application user interface; check the crawler.log file for log messages.


·         When previewing the crawled site in Site Capture Admin App, there is no indication when an external link is being viewed (e.g. if your download archive has a link to an external site, clicking on that link in preview mode will redirect to the external site).


·         Site Capture does not support running over https in this release

3.18 Site Launcher

·         Site Replication will fail if the site being replicated contains eWebEditPro as this has been removed from presentationobject.dtd. Users should remove <!DOCTYPE PRESENTATIONOBJECT SYSTEM “presentationobject.dtd”> from the eWebEditPro attribute editor prior to replication to avoid this. (14473113)


3.19 Site Management

·         Creating a site without a Preview asset assigned results in errors in the log which can be safely ignored

[CS.XCELERATE.ASSET][ERROR] error: unable to load asset type information for Variables.previewAssetType, in tag asset.load pagename:OpenMarket/Xcelerate/Admin/SiteFront" and "[CS.XML][ERROR] object.get no object named previewAsset"  


·      Site names that include a hyphen '-' are not supported if using LDAP  

3.20 Sites DocLink

·      If Windows is configured using the "Show All Folders" option, if your session times out and you are using Sites DocLink, the login window will appear when explorer loads the shortcuts


·         Revision Tracking of DocLink assets is not supported in this release

3.21 Sites Desktop

·      Revision Tracking and Workflow are not supported from Sites Desktop in this release.

3.22 Tags

·         Choice of values entered for variant attribute used in insite:calltemplate must be applicable to all types valid for clegal argument

3.23 Template / Site Entry / CS-Element

·         Wrapper pages with "." in the name will not execute. Templates and Site Entry assets should not have dot (.) in their name.


·         Do not use the tag <throwexception> in the code of a template asset. <throwexception> effectively kills execution in Sites for itself and any nested or parent Sites engine. This breaks template execution and streaming of data to the client. In addition, when a user approves a template for export publish, a <throwexception> terminates the execution of the approval page and the user gets no feedback.


·         No warning is given regarding potential for broken pages when deleting templates. Users should delete templates with care as if they are used as default in assets, the delete will result in failure to render those pages.

4.0 General Issues and Workarounds

 4.01 API

·     ics.CommitBatchedCommands() does not return the correct status or set the errno variable properly in every situation.


·     JSP processing adds whitespace


·     When using asset:export / asset.export tags on an asset that isn't a page or collection, the output XML doesn't contain info about the unnamed associations.


·     The Asset API Tutorial contains example byte d = fileObj.getBinary();

However getBinary() no longer exist. It has been changed to getBinaryStream() which returns an InputStream. Instead of byte d = fileObj.getBinary() , the example should be

changed to:

byte d = newbyte[fileObj.getBinaryStream().available()];      


·     The XML tag ASSET.DELETEREVISION, which deletes a specific revision of the asset, fails to execute. JSP variant asset:deleterevision should be used.

4.02 Admin Interface

·     In the AdminUI, the Tree Applet will not reflect changes when Start Menu name is edited. (14289692)


·     Downloading thread dumps from the System Tools is not supported for WebSphere


·     500 error is thrown if you browse directly to Sites-Cache status when AssetCache is not started or enabled


·         Pasting text using Ctrl+V into the query box of the Log Viewer triggers View Logs function. The correct short cut for log viewer functionality is Ctrl + shift + V


·     Downloaded log files from System Tools doesn't include information from cas.log


·     Right click REFRESH does not refresh page for Thread Info, Sites Info, and DB Info


·     Message "An error has occurred" appears when attempting to view logs in Log Viewer if the logs are empty.


·     "No access allowed" messages appear multiple times when permissions are insufficient for viewing table information in DB Info


·      Unable to run the File System test multiple times without changing the type of test to run.  


·      System Tools, File System Test information is not displayed in graph form in Internet Explorer. To view this graph use Firefox


·      When creating a new AssetMaker Assettype, using the tab key to move through the fields will result in the Browse button disappearing from view. Clicking in the area where the button originally appeared will allow Browse to continue.


·      Setting the property - xcelerate.showSiteTree property to false does not turn the applet off in Admin UI


·      When Sites is configured to use hierarchical LDAP, if the user only has access to the Management Site and you log into the Admin UI, the tree tab loads and shows the tabs, but all the tabs are empty.

4.03 Analytics Integration

·      Assets deleted in the Contributor UI are not reflected in the Analytics data.txt

4.04 AssetCache

·      When a revision tracked asset is deleted, on the initial inspection of asset, AssetCache shows this asset with updated time and valid dependency which is incorrect  


·      Uploading a BLOB larger than 5MB will result in an exception:

 "Error met serializing / deserializing <Assettype ID> for copying purpose in AssetCache". This can be safely ignored.


·      <render:LogDep> could cause un-linked cache If there is an un-recognized rendermode passed, the system will cache the page and not log the dependencies. This will cause the page not being flushed in any way since there dependencies are not there. The correct behavior should be:

            1. Cache the page and log the dependencies anyway or

            2. If the dependencies are not logged, do not cache the page.

4.05 Browser Support

·         Entering data into forms in the AdminUI when using Chrome 21x on MacOSx may not work properly if the action is initiated from the Applet (14640939)


·         Selecting Delete from the top menu in the Contributor UI will throw a JavaScript error when using IE9, delete using the Delete button instead to avoid this issue. (14569817)

4.06 Caching - Satellite Server

·         Any blob which is not supposed to be cached by the Satellite Server will be added under  <sscachedir>/uncachedblob. This directory can grow if blobs are not being cached on the satellite server. The content of this directory can be safely deleted at any time. It can be deleted manually or by using the FlushServer reset call.  Note: FlushServer reset call will also clear all the cache from the Satellite Server

4.07 CKEditor

·      Anchor name is added before the selected text when using IE9. (14464618)


·      Upgraded assets may have an extra <p> <span> added when viewed in Form Mode post upgrade. This can be resolved by changing the attribute to use the updated CKEditor.


·      For assets created prior to Content Server 7.5 Patch 1 - If the first piece of data in the FCKEditor window is an embedded link or included asset, you must switch to source view to add additional content prior to the embedded link or included asset. Similarly, if the last asset is an embedded link or included asset, source view must also be used to add additional content immediately following the link or included asset.                

4.08 Contributor UI

·     For multivalued BLOB attributes, the asset should be saved prior to using the manage option in Web Mode. (14755373)


·      If there is a failure due to template compatibility reasons while swapping a slot, the original slot content is cleared. Refresh or cancel the save to revert back to the previously saved state.


·      For multivalued BLOB attribute, use the browse button in the reorder popup rather than the upload that appears in the minitoolbar to prevent errors on saving.


·      Bookmarks are not appearing in the Tree for sites that are imported using CSDT. To resolve this, edit and save the bookmark tree tab in Admin.


·      When dragging and dropping from the docked search the avatar window (showing the asset name in blue ) tends to hide behind the search


·      Drag and Drop of page to the Site Plan Tree is not supported. Doing so may result in the tree node indicator to spin and not return results, other operations are able to continue during this time except action initiated from the node of the site plan tree that is no longer responding.


·      Moving of the Dashboard Widgets in the Home tab is not possible in Internet Explorer 9.


·      Progress bar is not displayed accurately for large (>64MB) file uploads for Basic Assets.


·      Setting bs.security=true results in blobs failing to render in Web Mode or Preview


·      Setting bs.security=true results in a failure of the blob to render correctly on create screen, inspect will display properly.


·         Changes to the presentation of a slot are not copied during an asset copy operation in Web Mode.


4.09 CSDT

·      Importing a CSDT export from to will fail if the export includes fw_attributeeditor or fw_uiconfiguration assettypes, users should remove these types from the datastore prior to the import (14659634)


·         CSDT plug-in will fail to share templates across multiple sites. Templates can be shared using Sites AdminUI and then they can be successfully used with the CSDT plug-in (14556308)


·         CSDT import from version 7.6.x will not be successful if the DatePicker attribute editor is included in the datastore as the calendar is different between this version and 11gR1+. Remove the attribute to import this data. (14620821)


·         When creating templates using the existing element option, if the specified element does not exist, an empty template will be created in Sites but cannot be exported


·      If filename length of exported file exceeds the OS filename limitation, the file cannot be exported. This is likely to happen if filename of uploaded blob is too long.


·      Deleting a site does not update the information on the exported assets. The workaround is to first unshare the assets from the site which you wish to delete then delete the site.


·      Deleting of non-asset resources should be done manually on each destination. This is currently no sync for deleted non-asset resources 


·      User must be cautious of the order which resources are imported. Consider situation where all developers have A points to B in their system. Then one developer changes A to point to C and deletes B. If other developers were to sync B before A, the import will fail since you cannot delete an asset that is being referenced.           


·      During import, you may experience some indexing data exceptions. This will only affect the search index and not the actual data import. Re-Index the affected asset types after the import if necessary.           


·      Resources that contain fw_uids which include slashes or commas cannot be exported


·      The Sync and FW workspace views in Eclipse do not properly display UTF-8 characters on Windows.     


·      The locale hierarchy information is not preserved for exported hierarchical DimensionSet. The workaround is to manually configure the hierarchal information after import.   


·      SiteCatalog resources do not contain a dependency on the ElementCatalog resource. These currently need to be exported/imported manually                  


·      The CSDT Eclipse Plug-in auto complete will add double quotes if your AppServer does not support this, the double quotes must be changed to single quotes manually      

4.10 Engage

·      Recommendation selection criteria "Random" will organize based on the weighted rating.                        


·      The index on VMVisitorAlias that puts a unique constraint on the combination of visitoridentifier and visitor columns causes the page to fail to render and stack traces will appear in the log when the same visitor visits the site again. To resolve this issue, drop the index on this combination.    

4.11 Flex Assets

·      If using multiple parents, they should all use the same Parent Select Style

4.12 Installation / Upgrade

·      Going back or restarting the install after entering passwords requires that the passwords be reentered or the system defaults will be used.


·      During upgrade, the following ERROR may appear in the sites log and can be safely ignored:

[com.fatwire.logging.cs] Exception loading properties from file list futuretense.ini java.lang.Exception: Required key not found: cs.pgCacheTimeout"

4.13 Performance

·         Admin UI Tree Applet takes 2 - 4 minutes to release memory used when switching sites, this is a JRE limitation

4.14 Publishing

·      Export to Disk - Changing display template results in multiple assets in pub list. Contact Support for a utility to resolve this.


·      "Exception loading applications assetcom.fatwire.assetapi.common.AssetAccessException: asset type FW_Application cannot be found in Content Server" may appear in the sites.log when installing avisports sample site or when a new site is created, this exception can be safely ignored.


·      When publishing from a CM install and subsequently creating a new site on another CM install, the Contributor App is not enabled by default and must be enabled manually for this new site.


·      Removing a published child page from the site plan and later only publishing the parent will leave the child page on the destination but the page will not appear in the site plan.


·      When you use an invalid multi-ticket in a REST call to SS, instead of redirecting to the login screen, it throws an exception:

javax.servlet.ServletException: Failed to parse assertion for multi ticket xxx

When you use an invalid multi-ticket in a REST call to SS, it does redirect to the login screen. However, instead of generating a ticket and displaying the requested information, the redirect fails, and an error is shown.


·      Initiating a REST call using an invalid ticket or multi-ticket via the browser while you are logged into Sites will be successful as it will use the session ticket (#30028)


·      Multivalued association is not returned with the ordinal value


·      Deleted groups are not deleted from the Security Configuration. The group can be manually deleted by removing the entries from the FW_CSSecurityConfig table.        


·      When under load, the following exception may occur when using Buffered Writes, this can be safely ignored as the data is properly returned:

com.sun.jersey.server.impl.application.WebApplicationImpl onException

 SEVERE: Internal server error javax.ws.rs.WebApplicationException: javax.xml.bind.MarshalException           


·      Content-type header must be set to allow delete operations  


·      When creating asset types in REST, the PluralForm is not reflected/honored in Advanced UI    


·      Invoking the Delete method on a non-existent object returns a 200 status code             


·      Update is not working for Application object type if Delete permission is not also granted         


·      If the first request after a restart of Sites is a PUT, the create will fail with a 500 error   


·      The Navigation service will return a 500 instead of 200 error if there are no Page assets               


·      Although description is a required attribute for a Site, the Sites REST service doesn't validate for a Site description during create/edit.


·      When roles are deleted via REST, the corresponding entry for Site and Users is not deleted. Use WEM Admin UI to delete a role or manually clean up the UserPublication table to remove the dependencies.


·      Access to navigation service requires user to be part of the RESTAdmin Group

4.16 Revision Tracking  

·      Viewing the version of a revision tracked asset where the parent has been deleted will display a blank screen


·      Deleting an asset that was associated to a revision tracked asset removes all associations on rollback


·      Content-type header is lost when a wrapper page is called using Co-resident Satellite Server. Sites logs

"Unable to set header (header name) because the header has already been committed”

   The workaround is to increase the application server response buffer size.


·      Unable to view document uploaded into the previous version of an asset from the show versions view. To view the earlier saved document version user can use the rollback feature as a workaround  

4.17 Site Capture

·      Download Archives action may timeout if the archive size is large.

·      Multiple Jobs and Archives get created if schedules overlap for the same crawler. It is recommended to create only one schedule for each crawler to avoid creation of duplicate jobs and archives.


·      In some cases, when install is on Solaris, if the start URI is not configured correctly, errors will be reported as HTTP instead of network errors. Ensure that the start URI is configured correctly.

4.18 Site Launcher

·         Site Launcher: the Sites Desktop information in the replicated site does not set the description field for Sites Desktop to enabled in the copied site  

4.19 Sites Desktop  

·         The following error may appear in the sites.log when assets are created using Word 2010

[ERROR] [WebContainer : 6] [docx4j.openpackaging.contenttype.ContentTypeManager] No subclass found for /word/stylesWithEffects.xml.

This error can be safely ignored.


·         Locale selected during creating an asset from Sites Desktop doesn't appear in Sites Desktop before save even though its saved correctly       


·      Unable to upload multiple images to a multivalued attribute.


·      Unable to reorder multivalued attributes in Desktop

4.20 Sites DocLink

·         Unable to create translate assets using 'copy' option


·      After the Document Type is changed in Sites, refreshing DocLink does not make this change active - the user must logout and log back in for the change to be effective.


·      Required fields are not marked as "Required" in DocLink Edit Configuration screen. But From Sites DocLink Client interface its prompting properly for all required fields problem only with Edit Configuration field.

4.21 Sites Explorer

·         Login using Sites Explorer on Windows 2008R2 over https fails to authenticate. It is recommended to use Sites Explorer on Windows XP or Windows 7 if configured using https

4.22 Start Menu

·         Start Menus that contain more than 21 characters  are not displayed properly in the search box in Contributor UI

4.23 Tags  

·         In earlier versions of Sites, <render:calltemplate scoped=”local”> would copy all variables from the calling element to the called element which was a bug. In 11gR1+ the behavior has been corrected to match the documentation in the Tag Reference Guide and it will now only copy over those variables that are passed to the called element as arguments. To retain the earlier incorrect behavior, add –DuserLegacyLocalScoping=true to the JAVA_OPTS  of the AppServer instance. (14664998)


·         Setting roles in insite:calltemplate results in inability to edit primary asset


·      The POST tag works incorrectly when USERNAME, PASSWORD or LOGOUT attributes are passed to it. Login and logout requests are sent to the URL being posted to instead of CatalogManager. One workaround is to perform login before this tag is executed. Alternatively, FormPoster API can be directly used to perform the post operation.


·      SEARCHSTATE.ADDRICHTEXTCONSTRAINT fails when the resultset returns more than 1000 rows.


·      Unable to delete page and basic assets using asset:void tag if a valid pubid is not present in session. Workaround is to set the pubid in the session to "0", then remove it again after voiding.

4.24 WEM Admin  

·         Case sensitivity of sorting is inconsistent


·      Site names with special characters or symbols are not getting deleted. Delete the site using Advanced UI in this case  


·      Deleting a site does not clean up the Apps assigned to the site. To resolve this, manually remove the site entries from the urlaccessroles column in FW_Applications table using Sites Explorer


·         Cannot assign roles to a user who has stale group membership data. The workaround for this is to edit and save the user in the WEM Admin UI               

4.25 WEM Framework

·         The SiteAdmin role is not added to the user for WEM Admin by default when the user has been assigned SiteAdmin role in another site. The user should be manually assigned access to the WEM Admin App if required.


·      If the last accessed application or asset no longer exists, subsequent login to Sites will result in blank screen. To resolve this clear the cookie from the browser cache.

4.26 Workflow

·         Shared roles need to be reselected if a workflow report is edited after initial save.


·      DashUser is listed in list of Workflow Participants if the user was part of the group before upgrade. This user role should be removed and replaced with SitesUser


·      If you select a workflow for an asset, then go to the Set Participants form, then click the Cancel button, the workflow is set to all participants, as if you had selected the Select All button.

4.27 User Mgmt - LDAP

·         Assigning a pre-existing LDAP role will fail. Workaround is to delete the role from LDAP before assigning to Sites users

4.28 XMLPost

·         XML namespaces are stripped from XML elements during evaluation.


·      XMLPost Creating Recursive Dependency on Itself When Trying To Modify Parent