2 General Issues and Workarounds

This chapter describes general issues and workarounds for this release.

2.1 A/B Testing

  • If a page on which an A/B test is running is changed and republished, then the A/B test shows correct new data for variant A. If the page is changed in such a way that the differentials for the variant pages no longer apply, then the variants aren’t shown correctly as expected.

  • Template assets that are used in A/B testing but aren’t used elsewhere can also be deleted. However, deleting a template used in a differential of an A/B test prevents the A/B test from displaying the intended content to the site visitors.

  • When an A/B test is running, it is possible to modify and publish the base page. These changes may prevent the test variants from being delivered correctly and invalidate the test results without warning. Therefore, it is recommended to not change a page while it is taking part in an A/B test.

2.2 Accessibility

In the Contributor interface, the JAWS accessibility reader doesn’t read the field names for flex assets that use the Pulldown, Uploader, and typeAhead attribute editors. In addition, the reader doesn’t read all field names on the Workflow Status screen. Lastly, the reader doesn’t read the field name for multiple-value date fields that use the date picker attribute editor.

2.3 Admin Interface

  • Downloaded log files from System Tools don’t include information from cas.log.

  • Right-clicking REFRESH doesn’t refresh the page for Thread Info, Sites Info, and DB Info.

  • The message "An error has occurred" appears when attempts are made to view logs in Log Viewer, but 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 isn’t displayed in graph form in Internet Explorer. To view this graph, use Firefox.

  • When WebCenter Sites is configured to use a hierarchical LDAP, if the user has access only to the Management Site and you log in to the Admin interface, the tree tab loads and shows the tabs, but all the tabs are empty.

2.4 APIs

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

  • JSP processing adds white space.

  • When asset:export / asset.export tags are used on an asset that is not a page or collection, the output XML does not contain information about the unnamed associations.

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

  • For case-sensitive databases, setting the case sensitivity to false does not disable the case sensitivity of the search query.

2.5 Approval

  • Approving a site plan using the right-click in the Contributor interface will not include any slot assets in the approval. Pages with slots will need to be approved separately.

  • When a recommendation or promotion is approved, it does not show segment as a dependency.

2.6 AssetCache

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

  • Uploading a blob larger than 5 MB will result in an exception, which can be safely ignored:

    "Error met serializing / deserializing <Assettype ID> for copying purpose in AssetCache"

  • <render:LogDep> could cause unlinked cache. If there is an unrecognized rendermode passed, the system will cache the page and not log the dependencies. This will cause the page to not be flushed in any way since their dependencies are not there.

  • A warning message in the log is sometimes seen: "Creating a new instance of CacheManager using the diskStorePath". The message can be safely ignored.

2.7 Authentication

Integrating WebCenter Sites with the WebLogic Server embedded LDAP may affect the listing of users previously assigned to the site on the Manage Sites Users page in the WEM Admin interface. This display issue does not affect functionality; previously assigned users can log in to the site successfully.

2.8 Bulk Approver Utility

Running the Bulk Approver utility no longer requires login credentials as plain text in the bulkapprove.ini file. The utility now accepts the credentials as arguments in the command line, as follows:

BulkApprover <config=...> <action=initialize,notify,approve,mark_publish> <output_file=xxx> <target_list=...> <username=...> <password=...>

target_list=<...>[optional, overrides approvalTargetList

2.9 Caching: inCache

The disk store size keeps growing as the cache gets more usage, even if the actual number of items in cache remains the same.

2.10 Caching: Satellite Server

  • Any blob that 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.


    The FlushServer reset call will clear all the cache from the Satellite Server.
  • Pages based on a template variant are not cached on Remote Satellite Server on the first request.

2.11 CKEditor

A frame shows a "Loading" message if the target is set to "not set", "frame", or "Same Window (_self)" during creation of the external link in CKEditor.

2.12 Cluster

After a successful user log in to a WebCenter Sites cluster environment, an error message displays in the sites.log file indicating that the ticket is either invalid or already expired. This message does not affect functionality and can be ignored.

2.13 Contributor Interface

  • When a page is previewed in a new window in the Contributor interface, it first checks the wrapper element in the request. If this element is not available, the page uses the default wrapper configured for the site in the Admin interface.

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

  • Bookmarks are not appearing in the tree for sites that are imported using Developer Tools. To resolve this, edit and save the bookmark tree tab in the Admin interface.

  • During 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 pages to the Site Plan Tree is not supported. Doing so may cause 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.

  • The progress bar is not displayed accurately for large file uploads (greater than 64 MB) for Basic Assets.

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

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

  • The select layout template appears behind videos added as part of a proxy asset in the Contributor interface.

  • Date picker does not work in Web Mode if the value is empty.

  • In Web Mode, the selected layout in the Change Layout option is retained in the browser even when the asset is not saved.

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

  • When Right-to-Left (RTL) orientation is used in the Contributor interface, the context menu and submenu may overlap in the navigation pane tree. In addition, the Content menu’s submenu options may not display fully.

  • The New menu option from Placed Pages node under the Site Tree in Contributor interface is removed.

  • In the Web mode, image upload fails in the first attempt, but is successful in the second attempt. Image upload works fine in the Form mode of the Contributor interface.

  • If you try to delete an asset, dependent assets are shown in the Delete page, but are not shown under the 'Referenced By' column in metadata tab of the asset.

2.14 Developer Tools

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

  • If the file name length of an exported file exceeds the operating system file name limitation, the file cannot be exported. This is likely to happen if the file name of an uploaded blob is too long.

  • You must be cautious of the order in which resources are imported. Consider the situation in which 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 would fail, since an asset that is being referenced cannot be deleted.

  • During import, you may experience some indexing data exceptions. This will affect only 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 that include slashes or commas cannot be exported.

  • The locale hierarchy information is not preserved for an 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.

  • Import fails to import segment assets when the segment criteria contain a history definition with a string value.

  • During a connection to a remote instance, the project WEB-INF folder points to a nonexistent location. As a result, code completion will not work. To work around this issue, map to local jars / tlds when working with remote connections.

  • If an ElementCatalog entry is created with the name of an existing ElementCatalog entry, the JSP will be overridden with a new empty JSP.

2.15 Edge Browser

  • If you are unable to login to Sites in the Edge browser, refresh the Edge browser or access the Site through other browsers, and then login to the Site through the Edge browser.

  • While switching sites in the Edge browser, click on the Browser Refresh icon to enable switching of the sites in the Edge browser.

2.16 Engage

  • To add segments in Recommendation assets, Oracle recommends using forms in the Contributor interface instead of enabling the Asset Forms functionality provided in the Admin interface. In the Contributor interface, the asset creation forms can be created using the Content > New menu, and these forms are accessible through Search/Tree tabs.

  • Due to an issue with the Add Selected Segment option accessible through Recommendation Asset Creation in the Admin interface, after enabling Asset Forms you may not be able to add segments. (The Add Selected Segment option is available after setting the advancedUI.enableAssetForms property to true through Property Management in the Admin interface and enabling the Recommendation asset type for the site.)

  • Setting an asset that is part of a recommendation to a rating of 100 results in only that asset being returned.

2.17 Flex Assets

If you are using multiple parents, they should all use the same Parent Select Style.

2.18 Image Optimization

The default Image Optimization filter does not optimize GIF images. This is a JDK limitation. Custom image optimization APIs may need to be implemented if you need optimized GIF images.

2.19 Installation

  • During and after installation, an exception related to the jersey-container-servlet-core-2.9.jar library may display when the WebCenter Sites server is shut down. This exception does not interrupt the shutdown process and can be ignored.

  • During a WebCenter Sites Managed Server and Administration Server shutdown, an exception may display in the Managed Server or Administration Server log files. These exceptions do not affect functionality and can be ignored.

  • During the configuration of WebCenter Sites with Apache on HTTPS protocol, use Apache 2.4.0 or higher version. There are known issues with configuration of WebCenter Sites with Apache versions lower than 2.4.0  for Transport Layer Security version 1 (TLSv1) protocol. The product installation may fail.

2.20 Logging

The Sites.log and cas.log files are not displayed in the Fusion Middleware Control console.

2.21 Mobility

  • Zooming in on more than 150 percent does not render the mobility preview page correctly.

  • The devices.xml file provides a sample that works best using user-agent identification to identify by device name. Modify this file for greater granularity.

2.22 Proxy Assets

Creating a Content Query that contains proxy assets will show only dots (…) in the search results.

2.23 Publishing

  • During publishing to a cluster, the progress bars in the publish status screen show progress out of order from the actual steps.

  • Export to Disk: Changing display template results in multiple assets in pub list. Contact technical support for a utility to resolve this.

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

  • Temp files created during publishing remain in the file system after publication.

  • Dependent asset relation for promotion is lost after publishing. This also occurs through REST and Developer Tools import / export.

  • Error -3100 when publishing blobs may occur. This can be safely ignored.

  • In the Admin interface’s Publish console, deleting a publish session that failed does not remove the session. The deleted session continues to display on the History tab.

  • When a user with the Publisher role publishes a page, the Publish screen does not list the page’s dependent (children) assets. This behavior differs from the Approval screen, which lists a page’s dependent (children) assets for approving the page.

2.24 REST APIs

  • To make a REST call, the user first gets the multi-ticket from CAS. Once the multi-ticket is received, the user should send the POST request to the URL http://<host:port>/sites/wem/service/encrypttoken. This POST request should contain the ContentType header value as applications/x-www-form-urlencoded. The user will get the encryptedtoken value as a response to this call. All calls to REST URLs must include this encryptedtoken value as the value of the X-CSRF-Token header in the request. This change applies to all REST calls except AGGREGATED REST APIs.

  • When you use an invalid X-CSRF-Token header value in a REST call to Satellite Server, it does redirect to the log in screen. However, instead of generating a ticket and displaying the requested information, the redirect fails, and an error is shown.

  • Initiating a REST call to sites using an invalid ticket or multi-ticket via the browser while you are logged into WebCenter Sites will be successful, as it will use the session ticket.

  • Multivalued association for an asset is returned in the same order when it is saved.

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

  • Under load, the following exception may occur during use of 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

  • During creation of asset types in REST, Plural Form is not reflected/honored in the Admin interface.

  • Update is not working for an Application object type if Delete permission is not also granted.

  • If the first request after a restart of WebCenter Sites is a PUT, the create may fail with a 500 error.

  • The Navigation service will return a 400 error if Page assets type is not enabled for the site.

  • When roles that are assigned to a user in a site are deleted via REST APIs, it results in 403 error.

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

  • A REST API for asset data sometimes returns an empty string when the attribute data is null.

  • REST API calls to Remote Satellite Server through Central Authentication Service (CAS) must be made after acquiring a multi-ticket and using that multi-ticket in each REST call.

2.25 Revision Tracking

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

  • If access to Checkout is denied, clicking the Checkout button in the Contributor interface will result in no response.

  • Deleting an asset that was associated to a revision-tracked asset removes all associations on rollback.

2.26 Satellite Server

  • On a Remote Satellite Server instance that runs on Apache Web Server, one or more operations related to uncached templates may get blocked because of another ongoing operation. This blocking of operations or threads occurs due to a bug in Apache, and it results in decreased throughput. This issue is exacerbated by an increased number of uncached templates.

  • A content-type header is lost when a wrapper page is called using Co-resident Satellite Server. WebCenter 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.

2.27 Search

  • When assets in the Contributor interface are assigned multiple tags, an advanced search does not return the correct results. For example, if an asset is assigned three tags and an advanced search looks for the asset based on one of its tags, no search results display for the asset.

  • When an attribute-specific advanced search in Contributor begins with an uppercase character, advanced search displays no results.

2.28 Shared File System (NIO)

  • When an NIO (Nonblocking I/O) shared file system is used in which the shared file system is stored on a separate database, a delay of 2-5 minutes on the first log in to WebCenter Sites is expected.

  • When the shared file system is managed in the database, the download option available under System Information tools is not working.

2.29 Site Capture

  • Download Archives action may time out if the archive size is large.

  • Multiple Jobs and Archives get created if schedules overlap for the same crawler. Oracle recommends creating only one schedule for each crawler to avoid creation of duplicate jobs and archives.

  • In some cases, when the installation is performed 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.

  • Site Capture shares two caches with WebCenter Sites: linked-cache.xml and cas-cache.xml. The default values are the same for Site Capture and WebCenter Sites.

    For cache configuration, Site Capture should be treated as a cluster member of WebCenter Sites. If the WebCenter Sites ports change, the Site Capture ports must be updated to match. If WebCenter Sites is changed to unicast, then Site Capture must also be changed to unicast.

    If Site Capture and WebCenter Sites reside on different machines, the timeToLive (ttl) value needs to be adjusted, as if they were members of the same cluster.

2.30 Site Navigation

  • The site navigation in avisports shows only the unplaced pages when an updated page is republished. The site navigation works as expected in the newly created sites.

  • If a page is moved to a different site navigation while another user is editing or viewing the page in the Contributor interface, the multidevice preview may not accurately reflect the correct device group.

  • Setting showparentnodes=false will result in related assets of the last node in the tree appearing as children of the root node.

2.31 Sites Explorer

Oracle recommends using Oracle WebCenter Sites Explorer on Windows 7 if it is configured using HTTPS.

2.32 Start Menu

Start menus that contain more than 21 characters are not displayed properly in the search box in the Contributor interface.

2.33 System Tools

The ResultSet Summary screen refresh does not always refresh properly. Use the individual screen for each cache for more accurate reporting.

2.34 Tags

  • The POST tag works incorrectly when a USERNAME, PASSWORD, or LOGOUT attribute are is passed to it. Log in and log out requests are sent to the URL being posted to, instead of CatalogManager. One workaround is to perform log in before this tag is executed. Alternatively, the FormPoster API can be directly used to perform the post operation.

  • SEARCHSTATE.ADDRICHTEXTCONSTRAINT fails when the ResultSet returns more than 1000 rows.

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

2.35 User Interface Customization

If the left navigation and right navigation panels in LayoutConfig are swapped, the Contributor interface throws errors and does not load.

2.36 Vanity URLs

Prior to release 12.2.1, administrators configured a URL rewriter filter to resolve Vanity URLs by modifying the web.xml file. In release 12.2.1, administrators now configure the rewriter filter by modifying the site.prefix property in the wcs_properties.json file using the Property Management Tool, as described in Managing JSON File Properties in the Oracle Fusion Middleware Property Files Reference for Oracle WebCenter Sites. The site.prefix property provides a comma-separated list of unique site prefixes required for resolving vanity URLs using the rewriter filter.

2.37 Visitor Services

Configuring Visitor Services requires profile, identity, and access provider (optional) JAR files. You can create these files in the following ways:
  • Create new implementations. For information, see Developing WebCenter Sites: Visitor Services in Oracle Fusion Middleware Developing with Oracle WebCenter Sites.

  • Modify the sample source and Java files shipped with the distribution. These sample JAR and source files are available in the samples folder when Visitor Services is installed with the With Samples option selected in the Configuration Wizard. If you installed Visitor Services without the samples, contact Oracle Support for these JARs and source files.

2.38 WEM Admin Interface

  • When you add a new site in the WEM Admin interface, a message may occur indicating that an error has occurred. This error message can be ignored.

  • Case sensitivity for sorting is inconsistent.

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

  • You 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 interface.

2.39 WEM Framework

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

  • If the last accessed application or asset no longer exists, a subsequent log in to WebCenter Sites will result in a blank screen.

2.40 Workflow

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

2.41 XMLPost

  • When invoking the XMLPost utility, as described in Importing Assets of Any Type in Developing with Oracle WebCenter Sites, developers should include the ESAPI.properties file in the class path to avoid security warnings.

  • XML namespaces are stripped from XML elements during evaluation.

  • XMLPost is created as a recursive dependency on the asset during modification of a parent asset.