...
1. Check out the Simple Content Portlet from Jasig Subversion:
| No Format |
|---|
$ svn co https://wwwsource.ja-sigjasig.org/svnportlets/sandbox/SimpleContentPortlet/trunk SimpleContentPortlet |
2. Build the portlet using maven.
| No Format |
|---|
$ cd SimpleContentPortlet
$ mvn clean install
|
...
In uPortal, this step involves calling the portal's deployPortletApp ant task from the command line. From uPortal's top-level directory:
| No Format |
|---|
$ ant deployPortletApp -DportletApp=/path/to/SimpleContentPortlet/target/SimpleContentPortlet.war
|
...
AntiSamy may be disabled via a simple portlet preference called "cleanContent". To disable content scanning, simply set "cleanContent" to "false". A sample alternate "Advanced CMS" configuration with content scanning disabled is included at the bottom of the distributed portlet.xml file.
CKEDITOR configuration
In addition to AntiSamy, the editor used (CKEDITOR) does its own filtering and transformation. To disable CKEDITOR' content filtering and rely only on AntiSamy, modify WEB-INF/jsp/configureContent.jsp to have
allowedContent: true;
Registering as a uPortal Portlet Publishing Type
In uPortal, the Simple Content Portlet may be registered as a pre-configured portlet publishing type. Registering the portlet in this manner will create a new option in the initial "portlet type" screen of the portlet administration wizard and will pre-configure some of the settings of the portlet. You will need to execute an ant deploy-war to deploy this file to Tomcat.
To register this new portlet type, first create a new directory in the uPortal source tree at uportal-war/src/main/resources/org/jasig/portal/channels/CMS. Copy the file from docs/cpd/cms.cpd in the portlet into this new directory.
Next, import the portlet's .channel file into your portal. From the uPortal base directory:
| Code Block |
|---|
ant crn-import -Ddir=/path/to/SimpleContentPortlet/docs/import -Dpattern=cms.channel-type |