Adapting the list of required runtime configuration changes for the theme

We must adapt the list of required runtime configuration changes for the theme.

1. Modify the dynamic resource references in static resources of the theme static resources. For more information about dynamic resource references, see Copying the theme.

2. Change the common-resources root node.

   1. Open the WAS console.

   2. OpenResources > Resource Environment > Resource Environment Providers > WP GlobalThemeConfig > Custom Properties.

   3. Change behaviors.layout.defaultLayout from dav:fs-type1/layout-templates/2ColumnEqual/ to <context-root-static-war>/layout-templates/2ColumnEqual/. For example, if the context root is /MyStaticContent, the value would be war:MyStaticContent/layout-templates/2ColumnEqual/.

3. Change resources.commonResourcesRootURI from dav:fs-type1/common-resources to war:/common-resources. For example, if the context root is /MyStaticContent, the value would be war:MyStaticContent/common-resources

   1. Open the WAS console.

   2. OpenResources > Resource Environment > Resource Environment Providers > WP ConfigService > Custom Properties.

   3. Create or adapt a regular expression for the refreshPageLayout.template.regexp parameter. The portal default is dav:fs-type1/layout-templates/.*|dav:fs-type1/themes/.*. The following example shows a regular expression:
      dav:fs-type1/layout-templates/.*|dav:fs-type1/themes/.*|war:/themes/.*

      If we do not perform the last step, users must have the Markup Editor role assigned to be able to change a layout.

What to do next

Define the secure locations of layout templates using this setting. If portal receives a request to create or update a page containing a layout link, and that link is matching this regular expression, the markup editor role is not enforced on that layout. Include only locations in the regular expression that are under Access Control enforcement. For example, the layout templates and theme folders can be changed only by users that have the Theme Manager role. References to war files are also usable, as the war file deployment is secured by Java EE rights.

Parent Packaging themes for deployment

Related tasks:

Modify the dynamic resource references for the theme