The problem is not the Module Name it's the Path= property. Path is the
relative location in the 12 hive where you are getting the file  from.
Since you specify PageLayouts or style  it is looking for a PageLayouts
or Style directory in the root of your site definition or Feature
definition directory. It's expecting to find the file in that location.
I normally put the file in the root of the Feature and set path to
Path="". I'm also not sure of the URL property you specified. Did you
check that address in SharePoint Designer? I think for a custom style
sheet you actually want URL="_styles". I don't think these are in a
Library either so it would just be Type="Ghostable"

If I leave Path="Styles" and Module="BYUIStyles" the error  says
"BYUIStyles" does not exist

The URL "Style Library/en-us/Core Styles" is correct.

My feature  has a prerequisite of the publishing feature so the Style
Library exists already. That is exactly where I wanted it put.

The error  "specified list  does not exist" was because I tried first with
%20 where the spaces were, and I forgot to delete one of the 0's at one
point.

I did an stsadm -o installfeature [] -force, but when I didn't recycle
the App pool it kept trying to use the old URL I specified. "Styles" is
the correct path in the 12 hive at Templates\features\BYUIPublishing\
and BYUIStyles seems to be just an identifier?????

Is it used elsewhere?

_styles did not work.

Where does _catalogs physically exist?

How do I create one like it called _styles?

You can't use a feature  to copy/ghost a file  to the 12 hive. You use a
Feature to copy/ghost a file from the 12 hive to a library or virtual
directory on the site.

_catologs doesn't physically exist. It's a location on a provisioned
site where the galleries are created. If you pull a SharePoint site up
in SharePoint designer you will see this location in the root of the
site. Take a look at the following MSDN article on how to provision a
file using a Feature.

msdn2.microsoft.com/en-us/library/ms441170.aspx
<msdn2.microsoft.com/en-us/library/ms441170.aspx>

So if I understand now:

MSDN "If you are instead provisioning a file  outside a document library,
specify Type="Ghostable"."

Is that what you meant by copy/ghost a file from the 12 hive to a
virtual directory (Ghostable = Directory, GhostableInLibrary= Library)?

Right now I manually place my feature  folder in the 12 hive, and I've
wanted to "provision??" the file to a style  library.

I'm interested in knowing how to do what microsoft has done and have a
directory like _catalogs that has several lists within it.

MSDN says:

"If you provision files to a subdirectory through the Module element,
Windows SharePoint Services automatically ensures that the directory
structure is created to match your files."

I assume that is talking about a subdirectory when you specify "URL" I
was hoping I could use

'<Module Name="MPages" List="116" Url="_style/BYUIStyle">'

And it would create a location for multiple custom style libraries to be
created.

MSDN "If you are instead provisioning a file  outside a document library,
specify Type="Ghostable"."

Is that what you meant by copy/ghost a file from the 12 hive to a
virtual directory (Ghostable = Directory, GhostableInLibrary= Library)?

Reply> Correct. If you take a look at the module  entry for the
default.aspx file in most of the site definitions you will see that it
doesn't have a Type entry because Ghostable is the default and the
default.aspx normally goes in the root of the site (unless it's a
publishing site). For a publishing site it would be ghostable in
library because you are putting it into the pages library.

Right now I manually place my feature  folder in the 12 hive, and I've
wanted to "provision??" the file to a style  library.

I'm interested in knowing how to do what microsoft has done and have a
directory like _catalogs that has several lists within it.

MSDN says:

"If you provision files to a subdirectory through the Module element,
Windows SharePoint Services automatically ensures that the directory
structure is created to match your files."

I assume that is talking about a subdirectory when you specify "URL" I
was hoping I could use

'<Module Name="MPages" List="116" Url="_style/BYUIStyle">'

And it would create a location for multiple custom style libraries to be
created.

Reply> I know you can create a subdirectory structure that way. I'm not
sure you can provision a list  that way. Normally lists are provisioned
first in a site definition and then referenced in the module. You could
try it, but I don't think it will work. Without the list entry you
would get a subdirectory called _style/BYUIStyle off the root of the
site. With the list entry I think you will get an error  because it will
be looking for a list instance but not finding it.

Yeah, I got an error  

Thank you. The part about Lists being provisioned in a site definition,
I think is the part I was missing. I've been trying to start small with
creating feature  definitions and I've obviously hit the point where I
have to jump to a larger scope.

It was also useful to hear why sometimes default.aspx is found from the
root of a site. I never could figure out how they did that.

When you say you can "create a subdirectory structure [using a module]",
is that referring to a subdirectory structure within a list  that has
already been provisioned? I'm wondering if I'm missing that there are
other types of subdirectory structures.

SharePoint websites can have subdirectories just like any other website.
Its just that they are stored in the database so you have to create them
differently. So lets say you wanted to put a masterpage in a
subdirectory on a site called MP and then reference it in an aspx page
using Masterfile=~site/MP/mymaster.master. You could create a module
that would create the subdirectory by adding a URL element to the Module
declaration. That would create the subdirectory. Then the file  element
would specify that that is where the master  file should be placed.
Since its just a subdirectory you can create it on the fly with a
module.

In a Feature there is no Module= It is module  Name=. When you say
Module= it thinks you are referencing a module entry named BYUIStyles.
That Module does not exist. Take a look at the following MSDN entry.

msdn2.microsoft.com/en-us/library/ms441170.aspx
<msdn2.microsoft.com/en-us/library/ms441170.aspx>

Your right, it was Module Name="BYUIStyles" that I meant to say.

Thank you for the reference

Hello Guys,

I'm new to SharePoint; where I have the version SharePoint 2010.

I'm trying to restore the definition of not physically existing folder whish is (_admin) and the page is webapplicationlist.aspx?

I got the red message of: "The file at the specified URL does not exist in this site."


Could you advise please ?

Regards,