Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

depths of onet.xml and schema.xml

  Asked By: Denny    Date: Jul 12    Category: Sharepoint    Views: 4039

I have been trying with custom site definitions for a week. They are
interesting. What are the best sites/blogs for folks who have plumbed the
depths of onet.xml and schema.xml etc.

Simple stuff is done pretty simply, but when you want to do a bunch of
stuff, the pile of hay eventually collapes with a resounding clunk as my
browser says "error" and "see troubleshooting for help" (lol @ as if) when I
access a site created from my more and more modified template.

Also, there are a few things I was simply not able to do:

1) Figure out all the things I have to do to all the files to add a document
library to my site definition.

2) Figure out how to 'uncheck' the 'overwrite existing files?" checkbox on
the upload.aspx(s). This one mystified me as I tryed a number of

3) Figure out what 'List' and 'Template' directories I can delete after I
use the 'Path="STS"' command on onet.xml for my lists that I want to keep
the same as STS. I really want to delete that which I do not need under my
template directory.

4) Figure out how to make a 'List Web Part' specific to my subsites to show
on the home default page. I can't seem to find the way to access the basic
underlying Web Part for lists and then insert into this the specific list
(i.e. the subsites) I am interested in. I figured I could avoid programming
(more importantly maintenance) by using the generic list web part and
specifying a view or service.

I am off to do the following: make a site similar to what I want then export
it as a template and the examine the manifest.xml file for clues. If anyone
has any other suggestions or solutions to my problems, I'd appreciate
hearing them.



1 Answer Found

Answer #1    Answered By: Guadalupe Bullock     Answered On: Jul 12

1. Check out “Creating a list  Definition” in the SDK

2. There’s a blog floating around on bypassing adding a listing for document to a SharePoint area when you upload  the document. This is a similar  problem so tracking that down might help.

3. You can pretty much strip the system down to a very bare minimum and still have it work. Try building from the ground up and adding the lists  you want. There are a few that are needed and cannot be removed, but for the most part  there is a sweet spot for a Minimal site  definition (although it won’t have much functionality)

4. Check out the AllUserWebPart in ONET.XML to get started (or if it’s a list you can use the List element in the Configuration section, it’s not just for defining lists but also for placing them)

Didn't find what you were looking for? Find more on depths of onet.xml and schema.xml Or get search suggestion and latest updates.