There is a package Pier-Jetsam-Environment whose purpose is to place all of the setup and configuration for an instance of pier under the control of the root frame component that you choose in /seaside/config, or that you embed in your seaside application. This configuration includes... css, javascript libraries (e.g NiftyCorners, Scriptaculous etc), default environment, initialization of custom environments, the forbidden request page, the "settings" parameters for pages etc. It is a bit experimental, but works for me so it is current code. There is a frame component which provides the traditional admin interface complete with tree view, and there is a frame component which supports the Content with style css framework. see: http://www.contentwithstyle.co.uk/Articles/17/ and there is a standard frame component which supports blueprint css. The simplest way to set up a basic pier site is to have two applications, one for users and an authenticated one for admins. best regards Keith

Keith Hodges wrote: Can you elaborate on this please. By two applications, do you mean two Seaside applications? I am assuming that each application uses the same Pier Kernel? If yes then how does one configure this? How do you set up one application to be authenticated, is it by using WAAuthConfiguration? Thanks, Frank

Hi Keith, I seem to be having a dependency problem when loading Pier-Jetsam-Environment from http://source.lukas-renggli.ch/pieraddons (error attached below). Sorry if this is an obvious thing, I'm not used to work with Monticello. This package depends on the following classes: WACss PRPierMain You must resolve these dependencies before you will be able to load these definitions: PRPierFrameAdminLibrary PRPierFrameAdminLibrary classSide>>settingsDescription PRPierFrameAdminLibrary>>borderContentsPreformatted PRPierFrameAdminLibrary>>colorAnchor PRPierFrameAdminLibrary>>colorBodyText PRPierFrameAdminLibrary>>colorBoxBackground PRPierFrameAdminLibrary>>colorBroken PRPierFrameAdminLibrary>>colorFooterBackground PRPierFrameAdminLibrary>>colorHeaderBackground PRPierFrameAdminLibrary>>colorHeaderTab PRPierFrameAdminLibrary>>colorHeaderTabActive PRPierFrameAdminLibrary>>colorHeaderTabAnchorActive PRPierFrameAdminLibrary>>colorHeaderTabAnchors PRPierFrameAdminLibrary>>colorHeaderTitle PRPierFrameAdminLibrary>>colorPreformattedBackground PRPierFrameAdminLibrary>>colorProtected PRPierFrameAdminLibrary>>colorSearchBackground PRPierFrameAdminLibrary>>colorSearchBackgroundSelected PRPierFrameAdminLibrary>>colorSearchBorder PRPierFrameAdminLibrary>>colorValidationMessage PRPierFrameAdminLibrary>>css0500layout PRPierFrameAdminLibrary>>css1000Basic PRPierFrameAdminLibrary>>css1500Header PRPierFrameAdminLibrary>>css1600HeaderTabs PRPierFrameAdminLibrary>>css1700HeaderSearch PRPierFrameAdminLibrary>>css2000Box PRPierFrameAdminLibrary>>css4000Contents PRPierFrameAdminLibrary>>css5000Footer PRPierFrameAdminLibrary>>css6000PatchBluePrint PRPierFrameAdminLibrary>>pencilLogoPng PRPierMain>>forbidden: PRPierMain>>kernelRoot PRPierMain>>start: Thanks, Andrés Keith Hodges escribió:

Maybe something else is missing? After loading Seaside28Jetsam-kph.70 when trying to load Pier-Jetsam-Environment-kph.17 I get: This package depends on the following classes: PRPierMain You must resolve these dependencies before you will be able to load these definitions: PRPierMain>>forbidden: PRPierMain>>kernelRoot PRPierMain>>start: Any hints? Thanks in advance, Andrés Keith Hodges escribió:

Thanks for the quick response Keith. I've downloaded the one-click image, where Pier seems to be running ok. I also tried updating to the latest Pier-Seaside version (Pier-Seaside-tg.306) and yet the PRPierMain class is not in my image. Could you tell me which package should I load? Thanks again, Andrés Keith Hodges escribió:

PRPierMain was required to run Pier on older versions of Seaside. All the functionality has now been moved to PRPierFrame. Cheers, Lukas On Sep 9, 2008, at 23:30 , Andres Fortier wrote: -- Lukas Renggli http://www.lukas-renggli.ch