ozmoss@ozmoss.com
Sent: Tuesday, 27 September 2011 3:04 PM
Subject: RE: MOSS - Web Part chrome is locked
Hi Jorge,
Found it. It can be set as a property of the file element within the module in
elements.xml.
e.g.
Module...
File...
PropertyName=ChromeTypeType=chrometypeNone/Property
Incredibly
10:17 AM
To: ozMOSS
Subject: Re: MOSS - Web Part chrome is locked
Hi Paul,
This change to elements.xml won't help. Similar change has to be applied to
.webpart file:
...
data
properties
property name=ChromeType Type=stringNone/property
Regards,
Shahram.
From: Paul Noone paul.no
September 2011 10:17 AM
To: ozMOSS
Subject: Re: MOSS - Web Part chrome is locked
Hi Paul,
This change to elements.xml won't help. Similar change has to be applied to
.webpart file:
...
data
properties
property name=ChromeType Type=stringNone/property
Regards,
Shahram.
From: Paul Noone
Subject: RE: MOSS - Web Part chrome is locked
Hi Shahram,
That hasn’t been my experience. It’s possible that it’s an either or (by design
or otherwise) but the properties added to the webpart file seem to apply
directly to its properties in the gallery, not a page instance. In any case
I’ve
[mailto:ozmoss-boun...@ozmoss.com] On Behalf Of
Nigel Witherdin
Sent: Wednesday, 28 September 2011 12:47 PM
To: OzMoss
Subject: RE: MOSS - Web Part chrome is locked
DocumentTemplate is an optional parameter for a ListInstance element, so
presumably if you omit it, then no document template would
.aspx
From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of
Jorge Carvalho
Sent: Monday, 19 September 2011 9:32 PM
To: ozMOSS
Subject: RE: MOSS - Web Part chrome is locked
Hi Paul,
The CreatechildControls method creates the controls on runtime when the web
part
Hi Paul,
The CreatechildControls method creates the controls on runtime when the web
part is rendered, not when it is provisioned.
You're resetting the Chrome type every time you display the web part.
You can define custom settings when you are provisioning the web part as part
of a web
