WebCenter Sites | Community Release Notes
11g R1 BP1 (11.1.1.6.1)
Table of Contents
1.0 What’s New in
Oracle WebCenter Sites Community 11gR1
1.01
Comments / Reviews Improvements – Visitor side
1.02
Comments / Reviews Improvements – Moderators Side
1.05
Social login and Custom Session Bar
1.06
Moderation and Customization
4.0 General Issues and
Workarounds
·
Compact look
and feel
·
Comments /
Reviews preview
·
Posting HTML
and media content
·
Permalinks for
comments
·
Helpfulness
rating
·
Social sharing
·
Category
management for comments and reviews
·
Auto disable
for comments/reviews
·
Max number of
posts
·
Post until date
·
Manually close
posting comments/reviews for a specific page
·
Search Engine
Optimization
·
Individually
deploy new rating widgets
o Thumbs up/down
o Like It
o Recommend
·
Summary widgets
· Moderate ratings based on rules
·
Simple,
powerful and rules based authoring
·
Graphical and
non-graphical results
·
Precise control
o Results display
o Poll status
·
Intuitive menu
with deploy option
·
Out of the Box
support for:
o Facebook
o Twitter
·
Extend login
options to 20+ social platforms through Janrain
(partner)
·
Optional login
controls for widgets
·
Individually
pluggable login bar
·
Simplified
navigation
·
Blacklisting/whitelisting users from Comments moderation screen
·
Templating for all widgets
o Customize look and feel
o Rearrange components
o Add custom data points
·
Language Support
·
WebCenter Sites
Community 11.1.1.6.1 includes a new upgrade engine to support upgrade from
versions 11.1.1.6.0 and 11.1.1.6.0 Patch 1
·
Refer to the Community Installation Guide for installation and
deployment requirements / recommendations
·
Note the following:
o In case of deploying both management and production Community applications in the same machine, it is recommended to changes default context-root for one of the Community applications (e.g. management community using context 'cosm' or production community using context 'cosp')
o It is recommended to change default Visitor
CAS context root to another (cas --> vcas) in case of deploying Visitor CAS on a machine where
another CAS application is already deployed (e.g
Sites CAS)
o If the installation directory specified in
the installer does not exist, the installer will create it, but it is limited
to one level of the directory structure. If the install directory is more than
one level user has to create it manually before running the installer.
o Widgets are certified with valid html
host pages only (tested on XHTML 1.0 of Strict doctype)
o Widgets are certified with the host page
URLs that contain valid query strings only (http://en.wikipedia.org/wiki/Query_string)
o CSS of host page may potentially impact the
widgets' look and feel. It may be necessary to apply custom CSS to widgets or even
adjust your host pages CSS
o Visitor CAS should be installed on the same
domain as the live site
o Community Server Admin application is not
supported in standalone mode (view) and is meant to be accessed only via Sites
WEM UI
o For the Community Admin application - IE
users must set the browser to receive all third party cookies
o Ensure Lucene
indexing is enabled for all Community asset types.
o The WebCenter Sites
URL provided during Community installation should be the same as used to access
Sites, for example, if you specify Sites hostname in the Community install,
then accessing Sites via IP address will result in failure to load the
Community Application
·
Change to restricted words has no effect on existing posts.
·
Sharing comment or review using Janrain, shows the Sites
login page. (14634351)
·
Timeout messages on Deployment tags are not localized
·
Date time format of comments, reviews etc is the same across
locales
·
Anonymous user is registered under different localized user names
·
Warning message "An attempt was made to set the session variable
"preferred_locale" to an invalid
value" is displayed on preview of sample blog pages, this can be safely
ignored.
·
Creating author assets with the same name may cause undesirable
behavior, i.e. the wrong author can be displayed for a blog
·
Sample Blog asset types need to be re-indexed after install to
search
·
Errors appear in log on first access of sample blog pages - these
can be safely ignored