It says that you can use following configuration code to convert a page into extension node
wpsconfig.{bat|sh} enable-page-as-extension-node
-DPageUniqueName=extensionNode
But it seems that this task was renamed in the WPS 6.1 and you can call it like this
ConfigEngine.sh action-enable-page-as-extension-node-wp.dynamicui.config
-DPageUniqueName=pageUniqueName
I tried running this task on my WPS 6.1.5 but it always failed so i looked into what is going on and it turns out that this task actually creates a xmlaccess and invokes it for some reason the task was failing so i tried executing the xmlaccess manually and it worked and i was able to mark that page as extension node
<?xml version="1.0" encoding="UTF-8"?>
<request
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="PortalConfig_1.3.xsd"
type="update"
create-oids="true">
<!-- Locate the tpl transformation -->
<portal action="locate">
<web-app action="locate" active="true"
uid="wps.dynamicui.transformationapp.webmod">
<transformation-app action="locate" active="true"
uid="wps.dynamicui.transformationapp">
<transformation action="locate" active="true"
objectid="theTransformation" name="DynamicUITransformation" >
</transformation>
</transformation-app>
</web-app>
<!-- Enable page as task page container -->
<content-node action="update"
uniquename="pageUniqueName">
<transformationinstance action="update"
transformationref="theTransformation"/>
</content-node>
</portal>
</request>
3 comments:
The task was probably failing because it seems to be configured for a default virtual portal. If you specify -DVirtualPortalContext= at the end of your commandline, it works (at least for me).
Thanks for info
Web Design Company in Bangalore
Website development in Bangalore
Thanks for info
Customized Crm Solutions
Post a Comment