Re: Content Types

2012-05-21 Thread Sezai Komur
Is splitting this document library up into multiple document libraries an option? Sezai. On Mon, May 21, 2012 at 4:41 PM, Ajay akhanna...@gmail.com wrote: Hi Guys, I have a client using a document library with 30 content types and each has different template. He wants to make it more

Re: Content Types

2012-05-21 Thread Ajay
I have suggested splitting, but he does seem too keen. We are looking at renaming CT by prefixing the division name before the CT name On Mon, May 21, 2012 at 8:55 PM, Sezai Komur sharepointse...@gmail.comwrote: Is splitting this document library up into multiple document libraries an option?

RE: Content Types and SharePoint 2010

2011-04-20 Thread Paul Noone
And still she gets awarded an MVP. :) From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Aaron Saikovski Sent: Monday, 18 April 2011 2:09 PM To: ozMOSS Subject: RE: Content Types and SharePoint 2010 Have a chat to Elaine Van Bergen about this. She has some very

RE: Content Types and SharePoint 2010

2011-04-17 Thread Prashanth Thiyagalingam
SystemPage CT has already got the build-in Title field inherited from 'Item' CT, and this is what is causing the duplicate error. Date: Mon, 18 Apr 2011 10:29:26 +1000 Subject: Content Types and SharePoint 2010 From: a...@hobsonator.com To: ozmoss@ozmoss.com We have run into an

Re: Content Types and SharePoint 2010

2011-04-17 Thread Alex Hobson
In MOSS 2007 the SystemPage CT did not have the attribute Inherits=TRUE so when our Common CT inherited from SystemPage and we changed the DisplayName we did not have an issue. If you have a look the Document (0x0101) and Item (0x01) CTs you will see what i mean. The Item CT has the Title

Re: Content Types and SharePoint 2010

2011-04-17 Thread Sezai Komur
RemoveFieldRef / ? http://msdn.microsoft.com/en-us/library/aa543602.aspx http://sharepointlive.blogspot.com/2009/05/content-types-inheritance-how-to-remove.html http://www.u2u.info/Blogs/karine/Lists/Posts/Post.aspx?ID=6

Re: Content Types and SharePoint 2010

2011-04-17 Thread Alex Hobson
Yeah saw that element. In my Common CT i have added the RemoveFieldRef element to remove the Title field but to no effect. The Title field will remain. If i add the FieldRef for Title after the RemoveFieldRef i again have duplicate columns. On Mon, Apr 18, 2011 at 1:24 PM, Sezai Komur

RE: Content Types and SharePoint 2010

2011-04-17 Thread Brian Farnhill
Sent: Monday, 18 April 2011 1:59 PM To: ozMOSS Subject: Re: Content Types and SharePoint 2010 Yeah saw that element. In my Common CT i have added the RemoveFieldRef element to remove the Title field but to no effect. The Title field will remain. If i add the FieldRef for Title after

RE: Content Types and SharePoint 2010

2011-04-17 Thread Aaron Saikovski
Sent: Monday, 18 April 2011 12:02 PM To: ozMOSS Subject: RE: Content Types and SharePoint 2010 You could just accept that doing things declaratively through CAML is just horrible and write some code to fix your columns up in the feature receiver :) [Description: Description: avatarpic-l] Brian

Re: Content Types and SharePoint 2010

2011-04-17 Thread Alex Hobson
] *On Behalf Of *Alex Hobson *Sent:* Monday, 18 April 2011 1:59 PM *To:* ozMOSS *Subject:* Re: Content Types and SharePoint 2010 Yeah saw that element. In my Common CT i have added the RemoveFieldRef element to remove the Title field but to no effect. The Title field will remain. If i add

RE: Content Types

2010-02-21 Thread Paul Noone
Hi Peter, This is pretty unusual because these content types should be sealed. Anyways...I think this is what you're after. Page Layout Content Types Article Page /_layouts/CreatePage.aspx Redirect Page Welcome Page Publishing Content Types Page

RE: Content Types

2010-02-18 Thread Tommy Segoro
Article Page is what you'll be interested in if you want to create publishing content types for WCM. From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Peter Milliner Sent: Friday, 19 February 2010 12:44 PM To: ozmoss@ozmoss.com Subject: Content Types Hello all,

RE: Content Types - Exporting and importing

2009-11-02 Thread MacDonald, Mike
To clarify - I created a list level content type and want to convert it to a site level for use elsewhere. Is that possible? From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of MacDonald, Mike Sent: Monday, November 02, 2009 9:46 AM To: ozMOSS Subject: Content

RE: Content Types - Exporting and importing

2009-11-02 Thread Wes MacDonald
From: ozmoss-boun...@ozmoss.com [ozmoss-boun...@ozmoss.com] On Behalf Of MacDonald, Mike [...@ibtteam.com] Sent: Monday, November 02, 2009 11:56 AM To: ozMOSS Subject: RE: Content Types - Exporting and importing To clarify – I created a list level content type and want to convert

RE: Content Types - Exporting and importing

2009-11-02 Thread Paul Noone
Mike, if you're not that keen on coding you can grab SPSourcehttp://spsource.codeplex.com/ to suck down the columns as XML schema definitions for re-use in a Site Column featurehttp://blogit.create.pt/blogs/andrevala/archive/2008/03/26/SharePoint-2007-Deployment_3A00_-Site-Column-Features.aspx.

RE: Content Types - Exporting and importing

2009-11-02 Thread Daniel W. Brown
column. Content Types should be just how it's done :P From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Paul Noone Sent: Tuesday, 3 November 2009 8:22 AM To: ozMOSS Subject: RE: Content Types - Exporting and importing Mike, if you're not that keen on coding you can grab

RE: Content Types - Exporting and importing

2009-11-02 Thread Paul Noone
Subject: RE: Content Types - Exporting and importing Ø For future reference, the predicament you currently find yourself in is precisely why Site Columns should always be used for these purposes. Their early should either be functionality to create a content type from a list .. or my preference

RE: Content Types - Exporting and importing

2009-11-02 Thread Paul Turner
...@ozmoss.com [ozmoss-boun...@ozmoss.com] On Behalf Of Daniel W. Brown [dan...@danielbrown.id.au] Sent: Tuesday, 3 November 2009 8:21 AM To: ozMOSS Subject: RE: Content Types - Exporting and importing For future reference, the predicament you currently find yourself in is precisely why Site

RE: Content Types - Exporting and importing

2009-11-02 Thread Daniel W. Brown
8:28 AM To: ozMOSS Subject: RE: Content Types - Exporting and importing Agreed, agreed! And there should be an easy way to either lock them down or reparent them in the event they become orphaned through misadventure! From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf

RE: Content Types - Exporting and importing

2009-11-02 Thread Paul Noone
And you would be just the man to write it, yes? ;) From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Daniel W. Brown Sent: Tuesday, 3 November 2009 8:56 AM To: ozMOSS Subject: RE: Content Types - Exporting and importing LOL Paul :P You're a man full of ideas

RE: Content Types - Exporting and importing

2009-11-02 Thread Daniel W. Brown
[mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Paul Noone Sent: Tuesday, 3 November 2009 8:32 AM To: ozMOSS Subject: RE: Content Types - Exporting and importing And you would be just the man to write it, yes? ;) From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf

RE: Content Types - Exporting and importing

2009-11-02 Thread Paul Noone
: Tuesday, 3 November 2009 8:59 AM To: ozMOSS Subject: RE: Content Types - Exporting and importing Haha, normally I'd jump on it, but I'm a bit under the hammer at the moment :( I'll make you a deal.. come down and present at the user group and I'll write it :P However on a more serious note. I will add

RE: Content Types - Exporting and importing

2009-11-02 Thread Paul Turner
] On Behalf Of Paul Noone [paul.no...@ceosyd.catholic.edu.au] Sent: Tuesday, 3 November 2009 8:38 AM To: ozMOSS Subject: RE: Content Types - Exporting and importing Brilliant. As for presenting to SPUG, I keep telling you, unless the title of my presentation is “101 SharePoint Bugs That Only I