sharepoint - MOSS 2007 - Custom Aspx Pages Created With Feature -
(I have also asked this question.)
I have a SharePoint feature that I can use To add some custom ASPX files to the Library Library.
When I activate this feature, I can see the pages in the in-browser and they can appear in the SPDsizer, but when I see "all site contents"
Feature element file:
& lt ;? Xml version = "1.0" encoding = "utf-8" & gt; & Lt; Element id = "9e85eb79-6d8d-4ff3-b0d4-64d55c3bb577" xmlns = "http://schemas.microsoft.com/sharepoint/" & gt; & Lt; Module name = "page" url = "page" & gt; & Lt; File path = "example.aspx" Url = "Example.aspx" IgnoreIfAlreadyExists = "False" & gt; & Lt; Property name = "title" value = "example" /> & Lt; Property name = "content type" value = "page" /> & Lt; / File & gt; & Lt; / Module & gt; & Lt; / Elements & gt;
Aspx file:
& lt;% @ page language = "c #" inheritance = "system web.ui page, system web, Version = 2.0.0.0, culture = neutral, public keychain = b 03 f5f7f11d50a3a "masterpagefile =" ~ masterrelale / default.master "%> & Lt;% - left intentionally empty - & gt;
(yup, it's empty!)
addendum
When I look at "in-browser pages" then I mean Manually navigate their URLs: http: // myserver: pORT / subsite / pages / example.aspx
When I see the "All Site Content" page "I" "Looking at the contents of the list: http: // myserver: PORT / subsite / pages / form / allItems.aspx
I got an answer on SharePoint Overflow:
Type =" Gossetin Library "in the file node Should be, because "Page" is a document library. Whenever you ever provision a file in the document library, you need a ghost-fixed library set.
Example:
& lt ;? Xml version = "1.0" encoding = "utf-8" & gt; & Lt; Element id = "9e85eb79-6d8d-4ff3-b0d4-64d55c3bb577" xmlns = "http://schemas.microsoft.com/sharepoint/" & gt; & Lt; Module name = "page" url = "page" & gt; & Lt; File path = "Example.aspx" Url = "Example.aspx" type = "GhostableInLibrary" IgnoreIfAlreadyExists = "False" & gt; & Lt; Property name = "title" value = "example" /> & Lt; Property name = "content type" value = "page" /> & Lt; / File & gt; & Lt; / Module & gt; & Lt; / Elements & gt;
So in the end I'm using XML ...
& Lt; / File & gt; & Lt; / Module & gt; & Lt; / Elements & gt;
Comments
Post a Comment