You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-user@portals.apache.org by Dan Olsen <da...@utah.gov> on 2008/03/14 21:39:41 UTC
Default theme
Is there are way to set the default theme for Jetspeed and then disable the theme selectors?
- Dan
AW: AW: Submitting a Form
Posted by David Psiuk <ap...@salesfactory.org>.
System.out.println(java.lang.NoClassDefFoundError == rtfm)
> true
-----Ursprüngliche Nachricht-----
Von: Dan Olsen [mailto:danrolsen@utah.gov]
Gesendet: Freitag, 28. März 2008 19:53
An: Jetspeed Users List
Betreff: Re: AW: Submitting a Form
So I opted to use Struts for a portlet and followed the tutorial found
at http://struts.apache.org/2.x/docs/struts-2-portlet-tutorial.html and
then deployed it to Tomcat. However, I am getting the following error in
the portlet:
----- BEGIN ERROR -----
Failed to load portlet
org.apache.struts2.portlet.dispatcher.Jsr168Dispatcher:
java.lang.NoClassDefFoundError: Could not initialize class
com.opensymphony.xwork2.util.DomHelper$DOMBuilder
----- END ERROR -----
I am assuming I probably need to have put the struts jars and the
xwork2 jars somewhere for the portlet to get access to them but I am not
sure where they should go. I currently have them in the WEB-INF/lib
directory but that doesn't seem to work.
I chose struts because that is the framework we use.
- Dan
>>> "Ron McNulty" <rm...@xtra.co.nz> 3/28/2008 1:27 AM >>>
Hi Dan
Take a look at Spring Portlet MVC. It is a solid framework that will
simplify your life once you have got over the inevitable learning
curve.
There are portlet examples in the distribution.
Regards
Ron
----- Original Message -----
From: "Dan Olsen" <da...@utah.gov>
To: "Jetspeed Users List" <je...@portals.apache.org>
Sent: Friday, March 28, 2008 9:06 AM
Subject: Re: AW: Submitting a Form
> I'm still not sure how all the action stuff works with Jetspeed. I'm
> looking through the source I'm not quite connecting how the whole
form
> request is handled.
>
> Dan
>
>>>> "David Psiuk" <ap...@salesfactory.org> 3/27/2008 11:09 AM >>>
> on js1.x:
>
> in your form, theres a inputfield called "myField".
>
> Then, in your portlet's action (that you call within your form
action),
> you
> access your form fields with:
>
> String myString = rundata.getParameters().getString("myField");
>
> Best regards
>
> David
>
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Dan Olsen [mailto:danrolsen@utah.gov]
> Gesendet: Donnerstag, 27. März 2008 17:51
> An: Jetspeed Users List
> Betreff: Submitting a Form
>
> In my edit.jsp I have a form that I am submitting. How do I catch
the
> submit
> and process the input?
>
>
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail:
jetspeed-user-help@portals.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: AW: Submitting a Form
Posted by Dan Olsen <da...@utah.gov>.
So I opted to use Struts for a portlet and followed the tutorial found
at http://struts.apache.org/2.x/docs/struts-2-portlet-tutorial.html and
then deployed it to Tomcat. However, I am getting the following error in
the portlet:
----- BEGIN ERROR -----
Failed to load portlet
org.apache.struts2.portlet.dispatcher.Jsr168Dispatcher:
java.lang.NoClassDefFoundError: Could not initialize class
com.opensymphony.xwork2.util.DomHelper$DOMBuilder
----- END ERROR -----
I am assuming I probably need to have put the struts jars and the
xwork2 jars somewhere for the portlet to get access to them but I am not
sure where they should go. I currently have them in the WEB-INF/lib
directory but that doesn't seem to work.
I chose struts because that is the framework we use.
- Dan
>>> "Ron McNulty" <rm...@xtra.co.nz> 3/28/2008 1:27 AM >>>
Hi Dan
Take a look at Spring Portlet MVC. It is a solid framework that will
simplify your life once you have got over the inevitable learning
curve.
There are portlet examples in the distribution.
Regards
Ron
----- Original Message -----
From: "Dan Olsen" <da...@utah.gov>
To: "Jetspeed Users List" <je...@portals.apache.org>
Sent: Friday, March 28, 2008 9:06 AM
Subject: Re: AW: Submitting a Form
> I'm still not sure how all the action stuff works with Jetspeed. I'm
> looking through the source I'm not quite connecting how the whole
form
> request is handled.
>
> Dan
>
>>>> "David Psiuk" <ap...@salesfactory.org> 3/27/2008 11:09 AM >>>
> on js1.x:
>
> in your form, theres a inputfield called "myField".
>
> Then, in your portlet's action (that you call within your form
action),
> you
> access your form fields with:
>
> String myString = rundata.getParameters().getString("myField");
>
> Best regards
>
> David
>
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Dan Olsen [mailto:danrolsen@utah.gov]
> Gesendet: Donnerstag, 27. März 2008 17:51
> An: Jetspeed Users List
> Betreff: Submitting a Form
>
> In my edit.jsp I have a form that I am submitting. How do I catch
the
> submit
> and process the input?
>
>
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail:
jetspeed-user-help@portals.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: AW: Submitting a Form
Posted by Ron McNulty <rm...@xtra.co.nz>.
Hi Dan
Take a look at Spring Portlet MVC. It is a solid framework that will
simplify your life once you have got over the inevitable learning curve.
There are portlet examples in the distribution.
Regards
Ron
----- Original Message -----
From: "Dan Olsen" <da...@utah.gov>
To: "Jetspeed Users List" <je...@portals.apache.org>
Sent: Friday, March 28, 2008 9:06 AM
Subject: Re: AW: Submitting a Form
> I'm still not sure how all the action stuff works with Jetspeed. I'm
> looking through the source I'm not quite connecting how the whole form
> request is handled.
>
> Dan
>
>>>> "David Psiuk" <ap...@salesfactory.org> 3/27/2008 11:09 AM >>>
> on js1.x:
>
> in your form, theres a inputfield called "myField".
>
> Then, in your portlet's action (that you call within your form action),
> you
> access your form fields with:
>
> String myString = rundata.getParameters().getString("myField");
>
> Best regards
>
> David
>
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Dan Olsen [mailto:danrolsen@utah.gov]
> Gesendet: Donnerstag, 27. März 2008 17:51
> An: Jetspeed Users List
> Betreff: Submitting a Form
>
> In my edit.jsp I have a form that I am submitting. How do I catch the
> submit
> and process the input?
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: AW: Submitting a Form
Posted by Dan Olsen <da...@utah.gov>.
I'm still not sure how all the action stuff works with Jetspeed. I'm
looking through the source I'm not quite connecting how the whole form
request is handled.
Dan
>>> "David Psiuk" <ap...@salesfactory.org> 3/27/2008 11:09 AM >>>
on js1.x:
in your form, theres a inputfield called "myField".
Then, in your portlet's action (that you call within your form action),
you
access your form fields with:
String myString = rundata.getParameters().getString("myField");
Best regards
David
-----Ursprüngliche Nachricht-----
Von: Dan Olsen [mailto:danrolsen@utah.gov]
Gesendet: Donnerstag, 27. März 2008 17:51
An: Jetspeed Users List
Betreff: Submitting a Form
In my edit.jsp I have a form that I am submitting. How do I catch the
submit
and process the input?
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: AW: Submitting a Form
Posted by Dan Olsen <da...@utah.gov>.
In addition to my previous emails, I want to just simply process the
form data that was submitted in a way that allows me to access the POST
variables in the edit.jsp page. Is this possible?
Dan
>>> "David Psiuk" <ap...@salesfactory.org> 3/27/2008 11:09 AM >>>
on js1.x:
in your form, theres a inputfield called "myField".
Then, in your portlet's action (that you call within your form action),
you
access your form fields with:
String myString = rundata.getParameters().getString("myField");
Best regards
David
-----Ursprüngliche Nachricht-----
Von: Dan Olsen [mailto:danrolsen@utah.gov]
Gesendet: Donnerstag, 27. März 2008 17:51
An: Jetspeed Users List
Betreff: Submitting a Form
In my edit.jsp I have a form that I am submitting. How do I catch the
submit
and process the input?
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
AW: Submitting a Form
Posted by David Psiuk <ap...@salesfactory.org>.
on js1.x:
in your form, theres a inputfield called "myField".
Then, in your portlet's action (that you call within your form action), you
access your form fields with:
String myString = rundata.getParameters().getString("myField");
Best regards
David
-----Ursprüngliche Nachricht-----
Von: Dan Olsen [mailto:danrolsen@utah.gov]
Gesendet: Donnerstag, 27. März 2008 17:51
An: Jetspeed Users List
Betreff: Submitting a Form
In my edit.jsp I have a form that I am submitting. How do I catch the submit
and process the input?
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Submitting a Form
Posted by Dan Olsen <da...@utah.gov>.
In my edit.jsp I have a form that I am submitting. How do I catch the submit and process the input?
Re: Default theme
Posted by Ron McNulty <rm...@xtra.co.nz>.
Hi Phil
Velocity is an open-source Java-based templating language. It is an Apache
project - http://velocity.apache.org/
To see how it is used in Jetspeed, take a look at the directories under
..\Jetspeed-2.1.3\webapps\jetspeed\decorations\layout There is one directory
here (e.g. tigris, bluesky etc) approximately corresponding to a Jetspeed
theme. Also, take a look at
..\Jetspeed-2.1.3\webapps\jetspeed\decorations\portlet These subdirectories
approximately correnspond to WPS skins.
Regards
Ron
----- Original Message -----
From: "PhilJackson" <pj...@hot.rr.com>
To: "Jetspeed Users List" <je...@portals.apache.org>
Sent: Saturday, March 15, 2008 5:27 PM
Subject: Re: Default theme
> Hi Ron,
>
> As I am not doing anything too complex with WPS themes, I am using just
> a text editor - EditPlus! If you have jsp reloading enabled the
> turnaround time is pretty quick. So far the purple screen of death has
> been enough to lead me to the error(s).
>
> What is a Velocity template comprised of?
>
> I have approached the JSP and JSPF files rather gingerly so far, as all
> things Java-related are still new and strange to me. That is where a
> majority of the heavy lifting is going on, along with the properties
> file.
>
> Phil
>
>
>
>
>
> On Sat, 2008-03-15 at 16:54 +1300, Ron McNulty wrote:
>> Hi Phil
>>
>> I am working with both Jetspeed and IBM WPS. I am investigating using
>> Jetspeed for development, and only going to WPS for integration test and
>> production. Main reason is that WPS is a very unfriendly developer
>> environment. (Slow to install, needs a really capable machine, takes
>> forever
>> to start in debug mode and runs like a dog when debugging, stuck on Java
>> 1.4...)
>>
>> Jetspeed themes are Velocity templates, but not at all difficult to
>> build.
>> They are described as "decorators" in the documentation. There is an
>> experimental JSP decorator in the latest release, but I have not tried
>> it.
>>
>> Generally you can copy an existing Jetspeed theme and replace the images
>> &
>> css files with the ones from WPS. Then edit the header.vm and footer.vm
>> files using the WPS JSPs as a guide. For simple jobs, the single column
>> layout is usually OK so you don't need to build a special layout.
>>
>> Regards
>>
>> Ron
>>
>>
>> ----- Original Message -----
>> From: "PhilJackson" <pj...@hot.rr.com>
>> To: "Jetspeed Users List" <je...@portals.apache.org>
>> Sent: Saturday, March 15, 2008 3:05 PM
>> Subject: Re: Default theme
>>
>>
>> > Pardon me,
>> >
>> > I am a fair newbie to IBM WebSphere Portal server and have been working
>> > a bit with themes. Subscribed to this out of curiousity. So a curious
>> > question(s) - does JetSpeed allow different themes to be applied to
>> > different pages? Figuring it must. Are they implemented with a
>> > collection of jsp and jspf files along with CSS, images, and property
>> > files? Really kind of interesting in WPS, uses some odd
>> > portal-specific
>> > tag libraries...
>> >
>> > PhilJ
>> >
>> > On Fri, 2008-03-14 at 18:51 -0700, David Sean Taylor wrote:
>> >> On Mar 14, 2008, at 1:39 PM, Dan Olsen wrote:
>> >>
>> >> > Is there are way to set the default theme for Jetspeed and then
>> >> > disable the theme selectors?
>> >> >
>> >> > - Dan
>> >>
>> >>
>> >> Don't set the decorator on any pages or folders except the root
>> >> folder.metadata
>> >> It will inherit down to all folders and pages
>> >>
>> >> To disable features in the customizer, the settings are in each
>> >> individual decorator.properties:
>> >>
>> >> allow.add.folder=false
>> >> allow.add.page=false
>> >> allow.add.portlet=true
>> >> allow.change.folder.name=false
>> >> allow.change.folder.theme=false
>> >> allow.change.portlet.decorator=false
>> >> allow.change.page.name=false
>> >> allow.change.page.theme=false
>> >> allow.change.layout=true
>> >> allow.delete.folder=false
>> >> allow.delete.page=false
>> >> allow.navigate.folder=false
>> >> allow.navigate.page=false
>> >> max.layout.nesting=2
>> >>
>> >> Note these settings no longer pickup when you edit the
>> >> decorator.properties
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
>> > For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>> >
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
>> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Default theme
Posted by PhilJackson <pj...@hot.rr.com>.
Hi Ron,
As I am not doing anything too complex with WPS themes, I am using just
a text editor - EditPlus! If you have jsp reloading enabled the
turnaround time is pretty quick. So far the purple screen of death has
been enough to lead me to the error(s).
What is a Velocity template comprised of?
I have approached the JSP and JSPF files rather gingerly so far, as all
things Java-related are still new and strange to me. That is where a
majority of the heavy lifting is going on, along with the properties
file.
Phil
On Sat, 2008-03-15 at 16:54 +1300, Ron McNulty wrote:
> Hi Phil
>
> I am working with both Jetspeed and IBM WPS. I am investigating using
> Jetspeed for development, and only going to WPS for integration test and
> production. Main reason is that WPS is a very unfriendly developer
> environment. (Slow to install, needs a really capable machine, takes forever
> to start in debug mode and runs like a dog when debugging, stuck on Java
> 1.4...)
>
> Jetspeed themes are Velocity templates, but not at all difficult to build.
> They are described as "decorators" in the documentation. There is an
> experimental JSP decorator in the latest release, but I have not tried it.
>
> Generally you can copy an existing Jetspeed theme and replace the images &
> css files with the ones from WPS. Then edit the header.vm and footer.vm
> files using the WPS JSPs as a guide. For simple jobs, the single column
> layout is usually OK so you don't need to build a special layout.
>
> Regards
>
> Ron
>
>
> ----- Original Message -----
> From: "PhilJackson" <pj...@hot.rr.com>
> To: "Jetspeed Users List" <je...@portals.apache.org>
> Sent: Saturday, March 15, 2008 3:05 PM
> Subject: Re: Default theme
>
>
> > Pardon me,
> >
> > I am a fair newbie to IBM WebSphere Portal server and have been working
> > a bit with themes. Subscribed to this out of curiousity. So a curious
> > question(s) - does JetSpeed allow different themes to be applied to
> > different pages? Figuring it must. Are they implemented with a
> > collection of jsp and jspf files along with CSS, images, and property
> > files? Really kind of interesting in WPS, uses some odd portal-specific
> > tag libraries...
> >
> > PhilJ
> >
> > On Fri, 2008-03-14 at 18:51 -0700, David Sean Taylor wrote:
> >> On Mar 14, 2008, at 1:39 PM, Dan Olsen wrote:
> >>
> >> > Is there are way to set the default theme for Jetspeed and then
> >> > disable the theme selectors?
> >> >
> >> > - Dan
> >>
> >>
> >> Don't set the decorator on any pages or folders except the root
> >> folder.metadata
> >> It will inherit down to all folders and pages
> >>
> >> To disable features in the customizer, the settings are in each
> >> individual decorator.properties:
> >>
> >> allow.add.folder=false
> >> allow.add.page=false
> >> allow.add.portlet=true
> >> allow.change.folder.name=false
> >> allow.change.folder.theme=false
> >> allow.change.portlet.decorator=false
> >> allow.change.page.name=false
> >> allow.change.page.theme=false
> >> allow.change.layout=true
> >> allow.delete.folder=false
> >> allow.delete.page=false
> >> allow.navigate.folder=false
> >> allow.navigate.page=false
> >> max.layout.nesting=2
> >>
> >> Note these settings no longer pickup when you edit the
> >> decorator.properties
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> > For additional commands, e-mail: jetspeed-user-help@portals.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Default theme
Posted by Ron McNulty <rm...@xtra.co.nz>.
Hi Phil
I am working with both Jetspeed and IBM WPS. I am investigating using
Jetspeed for development, and only going to WPS for integration test and
production. Main reason is that WPS is a very unfriendly developer
environment. (Slow to install, needs a really capable machine, takes forever
to start in debug mode and runs like a dog when debugging, stuck on Java
1.4...)
Jetspeed themes are Velocity templates, but not at all difficult to build.
They are described as "decorators" in the documentation. There is an
experimental JSP decorator in the latest release, but I have not tried it.
Generally you can copy an existing Jetspeed theme and replace the images &
css files with the ones from WPS. Then edit the header.vm and footer.vm
files using the WPS JSPs as a guide. For simple jobs, the single column
layout is usually OK so you don't need to build a special layout.
Regards
Ron
----- Original Message -----
From: "PhilJackson" <pj...@hot.rr.com>
To: "Jetspeed Users List" <je...@portals.apache.org>
Sent: Saturday, March 15, 2008 3:05 PM
Subject: Re: Default theme
> Pardon me,
>
> I am a fair newbie to IBM WebSphere Portal server and have been working
> a bit with themes. Subscribed to this out of curiousity. So a curious
> question(s) - does JetSpeed allow different themes to be applied to
> different pages? Figuring it must. Are they implemented with a
> collection of jsp and jspf files along with CSS, images, and property
> files? Really kind of interesting in WPS, uses some odd portal-specific
> tag libraries...
>
> PhilJ
>
> On Fri, 2008-03-14 at 18:51 -0700, David Sean Taylor wrote:
>> On Mar 14, 2008, at 1:39 PM, Dan Olsen wrote:
>>
>> > Is there are way to set the default theme for Jetspeed and then
>> > disable the theme selectors?
>> >
>> > - Dan
>>
>>
>> Don't set the decorator on any pages or folders except the root
>> folder.metadata
>> It will inherit down to all folders and pages
>>
>> To disable features in the customizer, the settings are in each
>> individual decorator.properties:
>>
>> allow.add.folder=false
>> allow.add.page=false
>> allow.add.portlet=true
>> allow.change.folder.name=false
>> allow.change.folder.theme=false
>> allow.change.portlet.decorator=false
>> allow.change.page.name=false
>> allow.change.page.theme=false
>> allow.change.layout=true
>> allow.delete.folder=false
>> allow.delete.page=false
>> allow.navigate.folder=false
>> allow.navigate.page=false
>> max.layout.nesting=2
>>
>> Note these settings no longer pickup when you edit the
>> decorator.properties
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Default theme
Posted by PhilJackson <pj...@hot.rr.com>.
Pardon me,
I am a fair newbie to IBM WebSphere Portal server and have been working
a bit with themes. Subscribed to this out of curiousity. So a curious
question(s) - does JetSpeed allow different themes to be applied to
different pages? Figuring it must. Are they implemented with a
collection of jsp and jspf files along with CSS, images, and property
files? Really kind of interesting in WPS, uses some odd portal-specific
tag libraries...
PhilJ
On Fri, 2008-03-14 at 18:51 -0700, David Sean Taylor wrote:
> On Mar 14, 2008, at 1:39 PM, Dan Olsen wrote:
>
> > Is there are way to set the default theme for Jetspeed and then
> > disable the theme selectors?
> >
> > - Dan
>
>
> Don't set the decorator on any pages or folders except the root
> folder.metadata
> It will inherit down to all folders and pages
>
> To disable features in the customizer, the settings are in each
> individual decorator.properties:
>
> allow.add.folder=false
> allow.add.page=false
> allow.add.portlet=true
> allow.change.folder.name=false
> allow.change.folder.theme=false
> allow.change.portlet.decorator=false
> allow.change.page.name=false
> allow.change.page.theme=false
> allow.change.layout=true
> allow.delete.folder=false
> allow.delete.page=false
> allow.navigate.folder=false
> allow.navigate.page=false
> max.layout.nesting=2
>
> Note these settings no longer pickup when you edit the
> decorator.properties
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Default theme
Posted by David Sean Taylor <da...@bluesunrise.com>.
On Mar 14, 2008, at 1:39 PM, Dan Olsen wrote:
> Is there are way to set the default theme for Jetspeed and then
> disable the theme selectors?
>
> - Dan
Don't set the decorator on any pages or folders except the root
folder.metadata
It will inherit down to all folders and pages
To disable features in the customizer, the settings are in each
individual decorator.properties:
allow.add.folder=false
allow.add.page=false
allow.add.portlet=true
allow.change.folder.name=false
allow.change.folder.theme=false
allow.change.portlet.decorator=false
allow.change.page.name=false
allow.change.page.theme=false
allow.change.layout=true
allow.delete.folder=false
allow.delete.page=false
allow.navigate.folder=false
allow.navigate.page=false
max.layout.nesting=2
Note these settings no longer pickup when you edit the
decorator.properties