This chapter describes general issues and workarounds for Oracle WebCenter Portal. It includes the following sections:
Section 4.1, "SQL Query with NCHAR Data Type Throws Exception"
Section 4.2, "Cannot Customize or Personalize a JSF Portlet"
Section 4.3, "Portals Do Not Display Correct Language When WebCenter Portal is Accessed Using OAM"
Section 4.4, "Announcement Publication Format can be Incorrect in Thai"
Section 4.5, "The Run as Servlet Link on Producer Test Page Does Not Work for JSF Portlet"
Section 4.6, "Using OpenSocial Pagelets to Post Activities to User's Activity Stream"
Section 4.7, "Unable to View Entire Content on iPad as Scrollbars Not Shown"
Section 4.12, "Unable to Check Out a Document When Using Firefox First Time"
Section 4.14, "Deployment Fails Because Versioned Applications Are Not Supported"
Section 4.15, "Displaying a Page on a Device When the Page Name Includes a Space"
Section 4.16, "Unable to Create Pages in Portals Created Using REST APIs"
Section 4.17, "Mobile Page Variants Not Displayed Correctly on Nexus 4 Devices"
When using a SQL data control, you may encounter an error if the query contains a column with the NCHAR data type. As a workaround, you can use the to_char(NCHAR_COLUMN NAME) function.
When clicking OK after customizing or personalizing a JSF portlet (that is, a portlet created using the Oracle JSF Portlet Bridge), the portlet does not respond and displays a time-out message. This is caused by performing an edit action and changing the portlet mode in a single operation. End users can work around this issue by clicking Apply (instead of OK) to perform the edit action first, then clicking Return to change the portlet mode back to View mode. Portlet developers can avoid the issue occurring by editing the code for the generated Edit Defaults mode (in the edit_defaults.jspx file) and Edit mode (in the edit.jspx file) and removing the code for the OK button so that end users are forced to use the Apply button instead.
When users access WebCenter Portal through OAM, portals do not display the language selected on the OAM login page. WebCenter Portal does not use the same xlf file name standard as OAM.
When the display language is set to Thai, the announcement publication format can be incorrect. This happens when announcements are opened to edit and are then saved, even if nothing in the announcement itself is updated.
You can create a JSF portlet (that is, a portlet that uses the Oracle JSF Portlet Bridge) using the Create JSR 286 Java Portlet Wizard by selecting the Generate ADF-Faces JSPX implementation method on the third step of the wizard.
If you create a JSF portlet in this way, you may find that clicking the Run as Servlet link on the portlet's Producer Test Page produces an error. The portlet itself, however, runs correctly.
To avoid this issue, add the ADF Page Flow scope to the project that contains the portlet. For information, see the "Adding and Removing Technology Scopes" section in Oracle Fusion Middleware Developing Portals with Oracle WebCenter Portal and Oracle JDeveloper.
Pagelets based on OpenSocial gadgets are not able to post activities to a user's activity stream. To implement a temporary solution, grant User Profile 'edit' permission to Oracle WebCenter Portal's Pagelet Producer using the following WLST/WSAdmin command:
grantPermission(appStripe="pagelet-producer", principalClass="oracle.security.jps.internal.core.principals.JpsAuthenticatedRoleImpl", principalName="authenticated-role", permClass="oracle.webcenter.peopleconnections.profile.security.ProfilePermission", permTarget="/oracle/webcenter/peopleconnections/profile/s8bba98ff_4cbb_40b8_beee_296c916a23ed/.*", permActions="view,edit")
After running the command, restart the Pagelet Producer server.
The Apple iOS platform does not use scrollbars. When you view a page on an iPad, content may appear truncated because scrollbars are not shown. Also, iFrame components ignore dimensions on iPad. To view the entire content area, use the two-finger scroll gesture on your iPad.
The Apple iOS platform renders RSS links by loading them through the site reader.mac.com. If the WebCenter Portal instance is not accessible outside your firewall, RSS links cannot be viewed.
The Apple iOS platform does not support a native file system browser. Therefore, you cannot upload content from an iPad. All upload actions, such as publish, upload, and share are disabled or hidden when you access WebCenter Portal from an iPad.
If you access a page through an iPad, you cannot copy the text displayed on the page. This is a limitation from the Apple iOS platform.
The Mail task flow does not render embedded images. If an email contains inline images, they are shown as attachments, and not within the message body.
The first time you access WebCenter Portal using the Mozilla Firefox browser, and attempt to open a document using Desktop Integration over an SSL or HTTPS connection, you will receive a warning that the certificate is not trusted, even if the environment has a valid certificate. You can open the document, but cannot check in or check out the document from within a Microsoft Office application. However, subsequent use of Desktop Integration through the Firefox browser will work as expected and you will be able to check documents in and out from within a Microsoft Office application.
The Web Clipping portlet is deprecated in 11g Release 1 (11.1.1.8.3) and should not be used. Instead, create a clipper pagelet using Oracle WebCenter Portal's Pagelet Producer.
Application versioning is no longer supported by default for ADF applications. Upon initial deployment, an existing 11.1.1.7.0 (or earlier) or new application 11g Release 1 (11.1.1.8.3) (or later) deploys successfully regardless of the application's versioning. However, when redeploying an unversioned application from JDeveloper 11.1.1.7.0 to a WebLogic Server where a versioned instance of that application is already running, deployment will fail. This is because the server is already running a versioned instance and WebLogic Server does not allow deploying an unversioned instance of the same application. You will see an error message like this:
Weblogic Server Exception: weblogic.management.ManagementException: [Deployer:149082]You cannot deploy application 'Application1_application1' without version. The application was previously deployed with version 'V2.0'.
To resolve this issue, undeploy the versioned application first and then deploy the unversioned application.
An issue exists when accessing a portal page on a device (such as a tablet or iPhone) when all of the following conditions are true:
The page has a space in its name
The page does not have a page variant defined
The Page Fallback setting for the page or the portal is Display No Page
In this case, the expected behavior is to see Page Not Available on the device. However, when all of the listed conditions are true, the content of the page appears (without the page title) on the device instead of Page Not Available.
For more information, see the "Setting Page Behavior for a Portal When No Page Variant Exists" and "Setting Page Behavior for a Specific Page When No Page Variant Exists" sections in Oracle Fusion Middleware Building Portals with Oracle WebCenter Portal.
In a portal created using WebCenter Portal REST APIs, you will face problems creating pages. To work around this issue, you need to reapply page permissions. Navigate to the Security page in WebCenter Portal Builder Administration. On the Roles tab, deselect all the permissions for pages and save the setting. Now select the same permissions again and save the settings.
Mobile page variants are not displayed on the new Nexus 4 devices. To resolve this issue, create a new device with the following user agent string:
Mozilla/5.0 \(Linux; Android.+4.2.+Nexus 4.+Chrome.*Mobile Safari.*
For information about creating new devices and specifying the user agent string, see the "Creating and Managing Devices" section in Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.
When you navigate to a discussions page by using its direct URL and pass forumId as a query parameter in the page URL, clicking the Create Topic button in the discussion forum displays a list of forums instead of opening the Create Topic dialog. This issue occurs when you access the pages that contain the Discussion Forums task flow with #{param.forumId} set as the value for the Forum ID attribute.
To ensure that clicking the Create Topic button displays the Create Topic dialog, use the following workaround:
Open the page that contains the Discussion Forums task flow in edit mode in Composer.
Ensure that the view switcher is set to Data.
On the Source tab, click PageDef at the bottom of the frame.
Locate the task flow binding within the <executables> section of the PageDef source.
You will notice that this task flow binding has the attribute Refresh="ifNeeded", and one of the input parameters to the task flow binding is "param.forumId".
Delete the attribute Refresh="ifNeeded".
Replace it with the following attribute: RefreshCondition="#{param.forumId!=null}".
Click Save to save the changes.