Use uncompressed CSS for logging and tracing client side rendering
Overview
By default, WebSphere Portal uses compressed Cascading Style Sheets (CSS) for logging and tracing. However, CSS can be difficult to read and edit when compressed. To use uncompressed CSS, make several changes to the page builder theme.
To use uncompressed CSS, edit...
$PORTAL_HOME/theme/wp.mashup.cc.theme/installedApps/wp.mashup.cc.theme.ear/PageBuilder2.war/themes/html/PageBuilder2/head.jsp
.and change
<link rel="stylesheet" href="${ccConfig ['cc.builder.context']}/css/portal_editmode_widgets.css" type="text/css" />...to...
<link rel="stylesheet" href="${ccConfig ['cc.builder.context']}/css/portal_editmode_widgets.css.uncompressed.css" type="text/css" />
- ...and...
<link rel="stylesheet" href="${ccConfig ['cc.builder.context']}/css/portal_editmode_widgets${mmBidiSuffix}.css" type="text/css"...to...
<link rel="stylesheet" href="${ccConfig ['cc.builder.context']}/css/portal_editmode_widgets${mmBidiSuffix}.css.uncompressed.css" type="text/css" />
- Change
<link rel="stylesheet" href="<r:url uri="dav:fs-type1/common-resources/ibm/css/common${bidiSuffix}.css" allowRelativeURL="true" mode="download" lateBinding="false"/>" type="text/css" />to
<link rel="stylesheet" href="<r:url uri="dav:fs-type1/common-resources/ibm/css/common${bidiSuffix}.css.uncompressed.css" allowRelativeURL="true" mode="download" lateBinding="false"/>" type="text/css" />
- Change
<link rel="stylesheet" href="<r:url uri="${themeWebDAVBaseURI}css/master${bidiSuffix}.css" allowRelativeURL="true" mode="download" lateBinding="false"/>" type="text/css" />to
<link rel="stylesheet" href="<r:url uri="${themeWebDAVBaseURI}css/master${bidiSuffix}.css.uncompressed.css" allowRelativeURL="true" mode="download" lateBinding="false"/>" type="text/css" />
- Change
<link rel="stylesheet" href="${dojoRoot}/com/ibm/widgets/css/widgets_combined.css" type="text/css" />to
<link rel="stylesheet" href="${dojoRoot}/com/ibm/widgets/css/widgets_combined.css.uncompressed.css" type="text/css" />
Save and close the file head.jsp.
Copy the file head.jsp to custom theme directory.
Redeploy theme. For instructions, see the topic about Deploy the theme.
Refresh browser cache. The following files are in a read only space in the portal. If you modify them, copy them from that location to custom theme directory, together with dependent files. If you do not do this, updates to the portal can overwrite changes.
$PORTAL_HOME/ui/wp.mashup.cc.deploy/installedApps/MashupCommonComponent.ear/mm.builder.war/css/portal_editmode_widgets.css.uncompressed.css
$PORTAL_HOME/ui/wp.mashup.cc.deploy/installedApps/MashupCommonComponent.ear/mm.builder.war/css/portal_editmode_widgets_rtl.css.uncompressed.css
In WebDAV: /common-resources/ibm/css/common.css.uncompressed.css and /common-resources/ibm/css/commonRTL.css.uncompressed.css
In WebDAV: /themes/PageBuilder2/css/master.css.uncompressed.css and /themes/PageBuilder2/css/masterRTL.css.uncompressed.css
$PORTAL_HOME/theme/wp.theme.dojo/installedApps/dojo.ear/dojo.war/v1.4.3/com/ibm/widgets/css/widgets_combined.css.uncompressed.css
Parent
Logging and tracing client side rendering
Related tasks
Deploy the theme
By default, WebSphere Portal uses compressed Cascading Style Sheets (C... By default, WebSphere Portal uses compressed Cascading Style Sheets (C... By default, WebSphere Portal uses compressed Cascading Style Sheets (C...