08-25-04 09:25 AM
Thanx !!!!!
Silvain
"Michael Harris" <none@none.com> wrote in message
news:cgfpup$4jsu$1@news.boulder.ibm.com...
> The portal administration user interface has extra requirements on the
> theme. Special code must be present in the theme JSP files or the
> administration user interface will not function properly.
>
> First, you must make a copy of your theme files. Create a new theme
> directory and copy all of your theme files into the new directory. Let's
say
> for discussion that you call it "myadmin". Then add the special code to
the
> files in the "myadmin" theme. For Portal 5.0.x, you need to add
> <wps:adminNavHelper/> to Default.jsp of your theme. For previous versions
> of portal, there is more code, but I'm not sure what it is off the top of
my
> head. You will need to inspect the JSP files of the administration theme
in
> that version of portal. Next, create a file in the myadmin directory
named
> "AdminTheme.flag". This special file indicates to the portal that this
theme
> is an administration theme and can only be used on administration pages.
> Then use the administration interface to define the new theme and apply it
> to an administration page.
>
> In older versions of portal, it was important to not apply an
administration
> theme to a standard page (1) for performance and (2) because it might be
> used on an anonymous page. The latest versions of portal (5.0.2 and
later)
> have improved such that you might be able to apply a theme that uses the
> <wps:adminNavHelper/> tag to a normal page (even anonymous) without
> suffering performance penalties. However, this is not supported at this
> time. The "AdminTheme.flag" file is only checked in the portal
> administration user interface. You can use xmlaccess to apply any theme to
> any page. So it if you want to add <wps:adminNavHelper/> to your normal
> theme you could use xmlaccess to apply it to the administration pages.
But
> again, this configuration isn't supported.
>
>
[ Post a follow-up to this message ]
|