The GenticsContentPortlet basically is a variation of the “GenticsContentModule” (Section 4) with some deprecated features removed and some new features added. The following sections will just describe the differences, for additional information see the documentation of the GenticsContentModule.
The following list of features has been removed from the GenticsContentPortlet
<plist>
in the content (can be replaced by Velocity)
<pxnl>
in the content (can be replaced by Velocity)
<insert>
in the content (can be replaced by Velocity)
<pobject>
in the content (can be replaced by Velocity)
Additionally to the Parameters of the GenticsContentModule, the GenticsContentPortlet supports the following pnode parameters.
Table 5.11. Portlet parameters for GenticsContentPortlet
Name | Type | Default | Description |
---|---|---|---|
backendurl | String | NULL | URL to the Gentics Content.Node 5 Backend for support of rendering content which was fetched from the backend. This is also needed for the support of frontend editing in conjunction with Gentics Content.Node 5. The backend URL must be reachable from the Portal Server, NOT the client. |
backendcookie | String | NULL | Comma separated list of names of cookies which need to be forwarded to the request to the backend to fetch the content. |
backendmode | Boolean | false |
This setting switches the source for
fetching the rendered content: When set to
|
proxyprefix | String | /GCN5_Portal/GCN/ |
Prefix for requests which are directed to the backend. The prefix must direct the request to a Proxy Servlet, that proxies the request to the backend (since the backend itself normally is not available via the same hostname). |
nodeidinpathlinks | Rule | true |
This parameter is only interpreted, when the
parameter
|
max-age | Expression | 5184000 |
This parameter controls the value of the response header Examples:
|
Since fetching content from Gentics Content.Node 5 requires a valid Gentics Content.Node 5 Session, this will only work, when the Portal User has logged in and was authenticated via a “GCNAuthenticationManager” (Section 8.3.7) .
Additionally to the Events described for the GenticsContentModule, the GenticsContentPortlet will throw the following events:
Table 5.12. Events of the GenticsContentPortlet
Name | Description | Event properties | ||||
---|---|---|---|---|---|---|
onContentLoadError | This event is triggered when a content cannot be loaded (either from the datasource or from the backend) due to an error in the underlying system. |
|