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
propertyname=ChromeTypeType=stringNone/property
Regards,
Shahram.
From: Paul Noone paul.no...@ceosyd.catholic.edu.au
To: ozMOSS 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 useful MSDN reference with terrific examples [not]:
http://msdn.microsoft.com/en-us/library/aa544032.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 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 template, or in a feature activated event receiver, I’m not sure how
would you go about defining the default chrome for a particular web part
though…. Anyone?
Cheers,
JC
From:ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of
Paul Noone
Sent: Monday, 19 September 2011 9:37 AM
To: ozMOSS (ozmoss@ozmoss.com)
Subject: MOSS - Web Part chrome is locked
Hi all,
I’m sure I’ve done something silly but I’m unable to change the chrome settings
for a custom web part via the UI.
They always revert to what I’ve defined in CreateChildControls.
protectedoverride void CreateChildControls()
{
if (!error)
{
try
{
base.CreateChildControls();
this.ChromeType = PartChromeType.TitleOnly;
Table table = new Table();
// etc...
row.Controls.Add(cell);
table.Controls.Add(row);
this.Controls.Add(table);
Is there a simple way to prevent this?
Kind regards,
Paul
___
ozmoss mailing list
ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss___
ozmoss mailing list
ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
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 only needed to add the property to the elements module and it works as I’d
hoped.
A slight variation was required.
Property Name=ChromeType Value=TitleOnly /
I’ve also found that many other advertised properties don’t work as expected or
where they’re expected. It’s very, very difficult to get the right info because
a lot of it relates to System.Web.UI.WebControls.WebParts as opposed to what’s
strictly allowed within a feature elements file for SharePoint.
The SharePoint schema reference lacks any detail when it comes to a parameter
set for these elements.
I’ve tried to use the IgnoreIfExists attribute for my list instance and web
part module but they’re apparently invlaid in this context. :\
Regards,
Paul
--
Online Developer/SharePoint Administrator,
ICT Infrastructure Team
CEO Sydney
From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of
Shahram Banihashem
Sent: Wednesday, 28 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 paul.no...@ceosyd.catholic.edu.au
To: ozMOSS 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...
Property Name=ChromeType Type=chrometypeNone/Property
Incredibly useful MSDN reference with terrific examples [not]:
http://msdn.microsoft.com/en-us/library/aa544032.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 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 template, or in a feature activated event receiver, I’m not sure how
would you go about defining the default chrome for a particular web part
though…. Anyone?
Cheers,
JC
From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of
Paul Noone
Sent: Monday, 19 September 2011 9:37 AM
To: ozMOSS (ozmoss@ozmoss.com)
Subject: MOSS - Web Part chrome is locked
Hi all,
I’m sure I’ve done something silly but I’m unable to change the chrome settings
for a custom web part via the UI.
They always revert to what I’ve defined in CreateChildControls.
protected override void CreateChildControls()
{
if (!error)
{
try
{
base.CreateChildControls();
this.ChromeType = PartChromeType.TitleOnly;
Table table = new Table();
// etc...
row.Controls.Add(cell);
table.Controls.Add(row);
this.Controls.Add(table);
Is there a simple way to prevent this?
Kind regards,
Paul
___
ozmoss mailing list
ozmoss@ozmoss.commailto:ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
___
ozmoss mailing list
ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
access denied when activating publishing
I have users who are now getting accessed denied errors when trying to activate the publishing feature on a subsite. They have previously been able to perform this operation on sites within the subsite, but something has changed. As site collection administrator, I can activate the feature without error and therefore assume the issue is permission based. The user belongs to a group ABC - that has full control of the site (unique permissions), but not the site collection root site. I have even tried granting full access at the site collection root site without success. The most frequent cause of this issue in Google is that the site collection does not have the SharePoint Server Publishing Infrastructure feature enabled, but I can confirm this and am able to activate the publishing feature as the site collection admin. The critical error in the log: Publishing Feature activation failed. Exception: Microsoft.SharePoint.SPException: Provisioning did not succeed. Details: Failed to initialize some site properties for Web Any suggestions? Max ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
RE: MOSS - Web Part chrome is locked
Sorry, typo: * IgnoreIfAlreadyExists*
Anyone know how to specify NO documenttemplate for a ListTemplate or Instance?
From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of
Paul Noone
Sent: Wednesday, 28 September 2011 10:43 AM
To: ozMOSS
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 only needed to add the property to the elements module and it works as I’d
hoped.
A slight variation was required.
Property Name=ChromeType Value=TitleOnly /
I’ve also found that many other advertised properties don’t work as expected or
where they’re expected. It’s very, very difficult to get the right info because
a lot of it relates to System.Web.UI.WebControls.WebParts as opposed to what’s
strictly allowed within a feature elements file for SharePoint.
The SharePoint schema reference lacks any detail when it comes to a parameter
set for these elements.
I’ve tried to use the IgnoreIfExists attribute for my list instance and web
part module but they’re apparently invalid in this context. :\
Regards,
Paul
--
Online Developer/SharePoint Administrator,
ICT Infrastructure Team
CEO Sydney
From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of
Shahram Banihashem
Sent: Wednesday, 28 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 paul.no...@ceosyd.catholic.edu.au
To: ozMOSS 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...
Property Name=ChromeType Type=chrometypeNone/Property
Incredibly useful MSDN reference with terrific examples [not]:
http://msdn.microsoft.com/en-us/library/aa544032.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 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 template, or in a feature activated event receiver, I’m not sure how
would you go about defining the default chrome for a particular web part
though…. Anyone?
Cheers,
JC
From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of
Paul Noone
Sent: Monday, 19 September 2011 9:37 AM
To: ozMOSS (ozmoss@ozmoss.com)
Subject: MOSS - Web Part chrome is locked
Hi all,
I’m sure I’ve done something silly but I’m unable to change the chrome settings
for a custom web part via the UI.
They always revert to what I’ve defined in CreateChildControls.
protected override void CreateChildControls()
{
if (!error)
{
try
{
base.CreateChildControls();
this.ChromeType = PartChromeType.TitleOnly;
Table table = new Table();
// etc...
row.Controls.Add(cell);
table.Controls.Add(row);
this.Controls.Add(table);
Is there a simple way to prevent this?
Kind regards,
Paul
___
ozmoss mailing list
ozmoss@ozmoss.commailto:ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
___
ozmoss mailing list
ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
RE: access denied when activating publishing
Are these sites using a custom template or definition? From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Maxine Harwood Sent: Wednesday, 28 September 2011 10:58 AM To: ozMOSS Subject: access denied when activating publishing I have users who are now getting accessed denied errors when trying to activate the publishing feature on a subsite. They have previously been able to perform this operation on sites within the subsite, but something has changed. As site collection administrator, I can activate the feature without error and therefore assume the issue is permission based. The user belongs to a group ABC - that has full control of the site (unique permissions), but not the site collection root site. I have even tried granting full access at the site collection root site without success. The most frequent cause of this issue in Google is that the site collection does not have the SharePoint Server Publishing Infrastructure feature enabled, but I can confirm this and am able to activate the publishing feature as the site collection admin. The critical error in the log: Publishing Feature activation failed. Exception: Microsoft.SharePoint.SPException: Provisioning did not succeed. Details: Failed to initialize some site properties for Web Any suggestions? Max ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
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 be assigned to the
list.
Haven't really checked this though, as I tend to create my ListInstances etc in
code, not declaratively, as it gives you far more power over the configuration
of the list, and allows you to handle conflicts (ie you can handle the case
where a list already exists with the same name/url)
Cheers,
Nigel
From: paul.no...@ceosyd.catholic.edu.au
To: ozmoss@ozmoss.com
Date: Wed, 28 Sep 2011 11:45:40 +1000
Subject: RE: MOSS - Web Part chrome is locked
Sorry, typo: * IgnoreIfAlreadyExists*
Anyone know how to specify NO documenttemplate for a ListTemplate or Instance?
From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of
Paul Noone
Sent: Wednesday, 28 September 2011 10:43 AM
To: ozMOSS
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 only needed to add the property to the elements module and it works as I’d
hoped.
A slight variation was required.
Property Name=ChromeType Value=TitleOnly /
I’ve also found that many other advertised properties don’t work as expected or
where they’re expected. It’s very, very difficult to get the right info because
a lot of it relates to System.Web.UI.WebControls.WebParts as opposed to what’s
strictly allowed within a feature elements file for SharePoint.
The SharePoint schema reference lacks any detail when it comes to a parameter
set for these elements.
I’ve tried to use the IgnoreIfExists attribute for my list instance and web
part module but they’re apparently invalid in this context. :\
Regards,
Paul
--
Online Developer/SharePoint Administrator,
ICT Infrastructure Team
CEO Sydney
From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of
Shahram Banihashem
Sent: Wednesday, 28 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 paul.no...@ceosyd.catholic.edu.au
To: ozMOSS 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...
Property Name=ChromeType Type=chrometypeNone/Property
Incredibly useful MSDN reference with terrific examples [not]:
http://msdn.microsoft.com/en-us/library/aa544032.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 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 template, or in a feature activated event receiver, I’m not sure how
would you go about defining the default chrome for a particular web part
though…. Anyone?
Cheers,
JC
From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of
Paul Noone
Sent: Monday, 19 September 2011 9:37 AM
To: ozMOSS (ozmoss@ozmoss.com)
Subject: MOSS - Web Part chrome is locked
Hi all,
I’m sure I’ve done something silly but I’m unable to change the chrome settings
for a custom web part via the UI.
They always revert to what I’ve defined in CreateChildControls.
protected override void CreateChildControls()
{
if (!error)
{
try
{
base.CreateChildControls();
this.ChromeType = PartChromeType.TitleOnly;
Table table = new Table();
// etc...
row.Controls.Add(cell);
table.Controls.Add(row);
this.Controls.Add(table);
Is there a simple way to prevent this?
Kind regards,
Paul
___
ozmoss mailing list
ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
___ ozmoss mailing list
ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
___
ozmoss mailing list
ozmoss@ozmoss.com
RE: MOSS - Web Part chrome is locked
Hi Nigel,
I think using feature receivers is definitely more robust but it's just
frustrating when you use the XML in a way that's supposed to be supported and
it fails to work. According to some examples I've seen you can event attach
content types to a named list instance without having to mess around in
schema.xml.
Anyway, everything seems to be working with the exception of the if exists
attributes. Might move these into feature activated/deactivated.
Regards,
Paul
--
Online Developer/SharePoint Administrator,
ICT Infrastructure Team
CEO Sydney
From: ozmoss-boun...@ozmoss.com [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 be assigned to the
list.
Haven't really checked this though, as I tend to create my ListInstances etc in
code, not declaratively, as it gives you far more power over the configuration
of the list, and allows you to handle conflicts (ie you can handle the case
where a list already exists with the same name/url)
Cheers,
Nigel
From: paul.no...@ceosyd.catholic.edu.au
To: ozmoss@ozmoss.com
Date: Wed, 28 Sep 2011 11:45:40 +1000
Subject: RE: MOSS - Web Part chrome is locked
Sorry, typo: * IgnoreIfAlreadyExists*
Anyone know how to specify NO documenttemplate for a ListTemplate or Instance?
From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of
Paul Noone
Sent: Wednesday, 28 September 2011 10:43 AM
To: ozMOSS
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 only needed to add the property to the elements module and it works as I'd
hoped.
A slight variation was required.
Property Name=ChromeType Value=TitleOnly /
I've also found that many other advertised properties don't work as expected or
where they're expected. It's very, very difficult to get the right info because
a lot of it relates to System.Web.UI.WebControls.WebParts as opposed to what's
strictly allowed within a feature elements file for SharePoint.
The SharePoint schema reference lacks any detail when it comes to a parameter
set for these elements.
I've tried to use the IgnoreIfExists attribute for my list instance and web
part module but they're apparently invalid in this context. :\
Regards,
Paul
--
Online Developer/SharePoint Administrator,
ICT Infrastructure Team
CEO Sydney
From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of
Shahram Banihashem
Sent: Wednesday, 28 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 paul.no...@ceosyd.catholic.edu.au
To: ozMOSS 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...
Property Name=ChromeType Type=chrometypeNone/Property
Incredibly useful MSDN reference with terrific examples [not]:
http://msdn.microsoft.com/en-us/library/aa544032.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 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 template, or in a feature activated event receiver, I'm not sure how
would you go about defining the default chrome for a particular web part
though Anyone?
Cheers,
JC
From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of
Paul Noone
Sent: Monday, 19 September 2011 9:37 AM
To: ozMOSS (ozmoss@ozmoss.com)
Subject: MOSS - Web Part chrome is locked
Hi all,
I'm sure I've done something silly but I'm unable to change the chrome settings
for a custom web part via the UI.
They always revert to what I've defined in CreateChildControls.
protected override void CreateChildControls()
{
if (!error)
{
try
{
base.CreateChildControls();
this.ChromeType = PartChromeType.TitleOnly;
Table table = new
RE: access denied when activating publishing
Yes, custom template but no changes in the past month. This started occurring in the past 2 days. Going to do a reboot this afternoon as there has been some AD issues on the network, I'll see if that helps? Other than that - I'll try a repair - that's fixed up strange things before.. From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Paul Noone Sent: Wednesday, 28 September 2011 11:48 AM To: ozMOSS Subject: RE: access denied when activating publishing Are these sites using a custom template or definition? From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Maxine Harwood Sent: Wednesday, 28 September 2011 10:58 AM To: ozMOSS Subject: access denied when activating publishing I have users who are now getting accessed denied errors when trying to activate the publishing feature on a subsite. They have previously been able to perform this operation on sites within the subsite, but something has changed. As site collection administrator, I can activate the feature without error and therefore assume the issue is permission based. The user belongs to a group ABC - that has full control of the site (unique permissions), but not the site collection root site. I have even tried granting full access at the site collection root site without success. The most frequent cause of this issue in Google is that the site collection does not have the SharePoint Server Publishing Infrastructure feature enabled, but I can confirm this and am able to activate the publishing feature as the site collection admin. The critical error in the log: Publishing Feature activation failed. Exception: Microsoft.SharePoint.SPException: Provisioning did not succeed. Details: Failed to initialize some site properties for Web Any suggestions? Max ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
