Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Modifying common files under /_layouts/1033 folder

  Asked By: Krista    Date: Nov 14    Category: Sharepoint    Views: 4956

I have come across one problem in sharepoint.
For example, I want to modify all files under "/layouts/1033" file.
Which approach i should follow, since i dont want to change original
files, as new version or new patch might overwrite all modified files.
I tied to create a new folder for example demo under layouts and
copied 1033 folder under this. Is this approach is fine. As many links
shows respective urls but few url still
shows /_layouts/1033/settings.spx instead
of /_layouts/demo/1033/settings.aspx
Is there any other way in which i can redirect all request to new set
of files under demo folder.



6 Answers Found

Answer #1    Answered By: Justine Barrera     Answered On: Nov 14

While I wouldn't do it myself, you can certainly change  the _layouts
virtual directory in IIS to point somewhere else.

Answer #2    Answered By: Laura Walker     Answered On: Nov 14

Most of the system will try to go into /_layouts/LCID to get images, aspx
pages, etc. (where LCID is 1033 for English portals).

What exactly are you trying to do here? When you say "I want to modify  all
files under /_layouts/1033" are you trying to do something like a global
branding? Frankly I wouldn't bother as you have to deal with:

-215 aspx pages
-6 css files  (with about a million classes in them)
-21 javascript files (about 800k)
-7 html files
-65 gifs

Okay, so you don't have to change  everyone one of them but probably at least
150 of the aspx pages and most of the javascript. That's probably a few
hundred man hours of work (rough guess).

If you're trying for a "I want my portal to look unique" just do basic stuff
with CSS files, a custom logo, and wait for Master pages and vNext as it
will make your life a lot easier.

Answer #3    Answered By: Cory Brooks     Answered On: Nov 14

I have to get a perticular branding for common  files with header &
Header can be solved using alternateHeader attribute of project tag.
style can be achived applying themes. But my concern is footer.
Sharepoint does not have anything for footer(As for as i know...).
So, i have to add footer to all pages. May be some other
customization for common pages. and i dont want to change  original
I am looking for some way to forward request to my own folder
for example  /_layouts/1033/demo
with out much efforts in this.
I dont have to change any functionality provided by sharepoint  as of
now may be some other customization might be required.

Answer #4    Answered By: Ruth George     Answered On: Nov 14

Check out this blog which discusses options for a custom footer:

The AlternateHeader option works, but some pages (I think all the admin
pages) won't pick it up.

The other thing is to probably create  a custom area def and then you can put
whatever you want into the default.aspx. You can also edit the SMARTPGS
files that are the templates for any new Web Part Pages and add them there.

My advice, don't knock yourself out over this as I feel it's not worth the
effort to do all this. I know people will scream that there has to be a
copyright notice or something, but personally I don't think that's worth a
week of someone's time. YMMV.

Answer #5    Answered By: Peter Peterson     Answered On: Nov 14
Answer #6    Answered By: Kalyan Pujari     Answered On: Nov 14

In the word of Willie Wonka from the original Willie Wonka and the
Chocolate Factory:
"Strike that, reverse it." (Bil did say "think") ; )

Willie also said, "A little nonsense now and then, is relished by the
wisest men."

All the admin pages will pick up the AlternateHeader option but all the
direct mode pages will not.

I do not recommend that people use the AlternateHeader option because:
1. You must manually edit all 102 pages in your custom site definition
to add the conditional logic.
2. The conditional logic is server-side code which will cause the page
to fail if it is ever unghosted (it does kinda work as unghost
3. The direct mode page version  of the conditional logic requires that
the <form> tag be moved and cannot use Server.Execute but instead use
Response.Write. This means that the header cannot itself run any
server-side code.
4. It doesn't handle the needs for an alternate footer.
5. etc.

Use one of the other approaches.

I say more in my sharepoint  Advisor article:

Didn't find what you were looking for? Find more on Modifying common files under /_layouts/1033 folder Or get search suggestion and latest updates.