Create a 'custom' List with Pages

Create a 'custom' List with Pages

• donbox5

  Hi,

  I haven't tried the alternatives posted here yet, but I see others have.

  But, if using the default Page list for everything is the way to go and use custom properties/fields to filter them out, I have another question:
  If I have a custom property/field named 'Show in navigation', how do I stop the default navigation menu from showing the Pages that have this property/field set to false

  
  

• Jon Prudhomme

  I got the following answer to the same question at a different forum:

  Create a custom Content Type that is suited for your type of Page and create a List that holds items of that Content Type. For the fields in the Content Type you create custom Site Columns.
  
  If you wish to do it in code you create a feature that does the above. For info on how to do that you need to read up on Features, Content Types and Site Columns on the microsoft web.
  
  Features:
  http://msdn2.microsoft.com/en-us/library/ms439657.aspx
  
  Content Types:
  http://msdn2.microsoft.com/en-us/library/ms467362.aspx
  

  
  

• Marcus Weber

  After posting my own thread on this very topic somewhere yesterday, I've been searching more and came across this one.

  I have been trying to figure out a solution to this very problem since last year now.

  There seems to be some confusion here between publishing pages and web part pages. This problem does NOT apply to web part pages. Web part pages can be placed in any document library that will accept a web part page (as expected).

  The problem is only with MOSS publishing pages, which "by design" get put into the /Pages/ document library. Interestingly enough, once they are in the /Pages/ library they can be MOVED to a different library that will accept publishing pages (or any sub type). Unfortunately though it can't be moved into the root of the site (eg for the home page) so it seems we are stuck with a "basic page" or a web part page for the default.aspx in the root.

  The main issue I have is for the users when they want to create a new page... the UI seems to indicate that they are about to create a new publishing page inside a custom library (navigate into the library and select new page)... but strangely the created page ends up in the /Pages/. This would cause untold misery for users and support personnel alike.

  Possibly a solution is to implement (as suggested above) I suppose an override for the "new > page" menu item button on the editing toolbar... but I'm not sure if this approach will be able to solve the problem. I think maybe the "create new page" page or whatever object/method it references to actually create the page would have to be modified. I don't know about you guys but the thought of attempting that makes me shudder.

  The fallback solution I am thinking of implementing requires scrapping the use of publishing pages altogether and reverting to the use of only web part pages. Using this approach I can create my site structure properly and have my own custom nav controls working easily. But it has a number of drawbacks for myself (and probably everyone else) - firstly web parts make for non-XHTML-compliant pages, which is important in my case. Secondly, we lose the ability to use page layouts (maybe "web part page templates" are equivalently usable). And lastly by using web part pages we lose the "enterprise content management" functionality and the content management side of things is not as user friendly.

  Another suggestion I have seen is to write a custom HttpModule to filter the /Pages/ from the URL. But the way I see it, this is going to cause more problems than it's going to solve...

  So, if someone from Microsoft (or just someone who has solved this problem before ) could please help out myself and any other SharePoint newbies on this matter, it would be greatly appreciated.

  Any information at all regarding publishing pages and /Pages/ library would be great. Especially I'd like to know about why this behaviour was "by design" and why there isn't a checkbox somewhere to turn it off.

  Thanks!

  -Adrian

  Edit:

  Ishai - "The "Create Page" link is a built-in menu item that redirects you to the "new page" screen for the "pages" library.". Correct me if I'm wrong but when I'm in my custom library that will accept publishing pages, and I click "new page", the breadcrumbs indicate that we are still in the custom library, and not /Pages/. Also, I am unable to use your filtering idea of the /Pages/ list, as the URL of each page is important.

  Helge - "..create a List that holds items of that Content Type". I tried creating a list that held items of my own content type (inheriting from Page, I added it to the "List Content Types"), but when I went to add the content type to the list, I couldn't select my content type because it was not in the list provided. It seems that lists will only accept certain content types (I think those inheriting from Item).

  Wes is right. THIS HAS GOT TO BE BASIC.

  
  

• JIM.H.

  Hi Ishai,

  I tried option 1.

  - created a new document library for pages (/mycustom pages) 
  - allowed management of content types
  - added the article page content types
  
  i can't seem to handle @creation a new page still wants to be stored the in the /pages folder. Not in  /mycustom pages folder

  regards, Joost

  
  
  

• Will Merydith

  I am dealing with the same situation. We need to create custom document libraries that support the Page content type. Apparently, you can define a custom ListTemplate and ListInstance using CAML and features. You can use the C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES\Publishing feature as a template for your custom document library. So far I have successfully created a new document library using this approach, but am having trouble associating my content type with my custom library. I have to associate the Page content type with my library manually in the UI after it is created, rather than defining it in the feature with CAML. I am also running into a problem deleting the custom library after it is created.

  Check out this url for about creating custom lists: http://msdn2.microsoft.com/en-us/library/aa543477.aspx

  
  

• AndyL

  Joost,

  The "Create Page" link is a built-in menu item that redirects you to the "new page" screen for the "pages" library.

  You have three options:

  1. train your authors that when they want to create a new page in the "non-pages" library, they should go to that library and click "new" there
  2. create a new menu item in the "site actions" menu bar that will redirect people to the new page screen of the second document library (see an article of mine for something similar: http://spstips.blogspot.com/2007/01/how-to-add-print-list-option-to-list.html)
  3. I am not sure how, but in sps2003 we had a drop down box for choosing a document library when creating a new page. maybe that can be re-enabled.

  Ishai Sagi
  www.spstips.blogspot.com

  
  
  

• Dillso

  First, you dont have to set up a seperate "Pages" library, you can just add a column to the existing one, and filter based on the value the user who created the page put in that column.

  But to answer your question - just create a new document library, and tell it (when creating) that the default document type should be web part page.

  Ishai Sagi
  www.spstips.blogspot.com

  
  
  

• jankowiak

  Hi Ishai,

  i did your provided solution but still when i create a new page it will always be referenced to the /pages folder. Isn't there another way

  I want to have two pages libraries with different permissions. Instead of applying every new page to the same default .pages library

  tnx, Joost

  
  
  

• Dinesh Patel

  Did you solve this, I have the same problem.

  Heres what I need, just like you described.

  1) I have site, and multiple subsites and multiple subs of those subs

  2) Each site and subsite needs to have its own page libraries

  3) Pages will be grouped and security must be administrativable by group.

  4) We want to use a template like the article template.

  How the heck can this be done

  I will be for ever in debt if someone can help me solve this, I have been going crazy for 2 months play with different ideas with document libraries, custom fields, content types and other things. THIS HAS GOT TO BE BASIC. Everyone would have a need to do this.

  Thanks, Wes

  
  
• Create a 'custom' List with Pages