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
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
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
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
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
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
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
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:
