Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

"_catalogs" vs "Library"

  Asked By: Harshini    Date: Jul 25    Category: Sharepoint    Views: 4548

<Module Name="PageLayouts" Url="_catalogs/masterpage"

Can anyone tell me a reason why master pages and page layouts are in
"_catalogs" but Style exists in a library called "Style Library"

Doesn't that mean that style exists in the database, and that the master
pages exist "unghosted" (I never remember which is which) on the system
until you customize them?

If I want to install my own style sheet as a feature is it appropriate
to use:

<Module Name="BYUIStyle" Url="Style%20Library/en-us/Core%20Styles"
Path="Style"> ?

There is no better means of promoting another person's change of heart

than allowing our own heart to be changed.



8 Answers Found

Answer #1    Answered By: Cathy Cameron     Answered On: Jul 25

<Module Name="PageLayouts" Url="_catalogs/masterpage"

Can anyone tell me a reason  why master  pages and page  layouts are in
"_catalogs" but style  exists in a library  called "Style Library"

Doesn't that mean that style exists  in the database, and that the master
pages exist  "unghosted" (I never remember which is which) on the system
until you customize  them?

If I want to install  my own style sheet  as a feature  is it appropriate
to use:

<Module Name="BYUIStyle" Url="Style%20Library/en-us/Core%20Styles"
Path="Style"> ?

There is no better means of promoting  another person's change  of heart

than allowing  our own heart to be changed.

Answer #2    Answered By: Kerri Steele     Answered On: Jul 25

So is the style  Library an appropriate place for me to put my own custom
styles? Or should I put it somewhere else in the event that I don't
enable publishing?

Right now I have Publishing as a required dependency, because I was
hoping to use changing of page  Layouts on the fly.

On a tangent: Publishing uses the System/PageLayout content type and
System/WebPublishingPage whose text fields only accept 255 characters
because they inherit from Document. I added my own content type which
inherits from Item instead of from Document, but I lose the ability to
switch page layouts  on the fly. Which part of the Publishing feature  can
I associate to my own feature so I can use my content type, but still
switch the page layouts like the Publishing feature content types let
you do?

Answer #3    Answered By: Alisha Itagi     Answered On: Jul 25

The Style Library is an appropriate place, but I wouldn't use it if you
may not enable publishing. I don't know if it even exists  if you don't
enable publishing. _catalogs is there whether it's a publishing site or

As to the custom content type. I don't know that you would be able to
associate something from Publishing with your custom content type. I
think you are stuck with either using the one that inherits from
document or writing your own. Not sure why the 255 character limit
other than the fact that a URL can only be 255 characters long. That's
not an MS thing that's an Internet standard. You can write your own
Page layout content types, but I believe they have to be in the same
inheritance tree or publishing won't work.

Answer #4    Answered By: Octavio Dotson     Answered On: Jul 25


"The reason  there is a 255 character limit for Multiline Text Fields in
Document (Forms/Picture) Libraries is that the OLE property stream
doesn't support more than 255 characters. Having more than 255
characters would cause problems demoting properties into documents."


I tried Using a content type inherited from a publishing page  to build
our Page Layouts. We couldn't put more than 255 characters in the
multi-line text fields. I read that this is because it inherits from
Document which has the described limitation. Changing to a content type
inheriting from Item fixed the problem, however I had to manually
associate the content type into sharepoint designer, and there is no way
to change  the page layout now.

Answer #5    Answered By: Judy Pittman     Answered On: Jul 25

The 255 character limit has to do with an OLE limitation when promoting  and
demoting properties between the Library and the document. The property in the
list CAN be set to store more but will be truncated if users edit the document
after the property has been set.

Answer #6    Answered By: Tricia Mullins     Answered On: Jul 25

What does it mean to promote and demote properties between the library
and document?
Is there something that I was doing wrong in my page  layout that wasn't
letting me use more than 255?

Answer #7    Answered By: Himanshu Gohil     Answered On: Jul 25

Instance/Content pages  (ASPX) are considered "documents" by SharePoint. The
values for the Field Controls are stored as properties of that document and are
therefore subject to the limitations of OLE.

Answer #8    Answered By: Ashton Schroeder     Answered On: Jul 25

That is what I was talking about. What are the circumstances then that the
properties are NOT truncated.
We wanted to use publishing pages  as a web editor. It works fine as long as our
content type inherits from Item, and not from Document. I wish there was a way
to create content pages using the Publishing page  content type so that we can
change layouts  on the fly.

Didn't find what you were looking for? Find more on "_catalogs" vs "Library" Or get search suggestion and latest updates.