1) how can i access _layout/1033/styles/custom.css file with SharePoint Designer ?
2) if i created a folder named 1033 through SharePoint Design in Style Library. What setting i have to make in master page to pick localized folder.
Thanks
_layout is a virtual directory mapped to the 14 hive. Altering of these files directly is not recommend and I believe is not supported as these files can be overwritten at runtime.
If you must use sharepoint designer then your best bet is to make a copy of this file and place it in the style library.Then update your site to use the new CSS file loaded in your style library.
Related
I was trying to find any tool that I can use to create ONET file from the existing SharePoint site. Unfortunately wasn't able to find. Does anybody know anything about that? There should be something besides of manual way to do that... Any MS solutions, third party tools?
As John Saunders is alluding, the simplest approach would be to let SharePoint create it for you. It's not exactly sitting in the site though; you can't just open the site in SharePoint Designer & grab it - but there is a way to get it:
Save the site as a Site Template (with or without content, doesn't matter - but without will be faster/smaller)
Download the STP/WSP from the Site Template (SP2007)/Solutions (SP2010/13) Gallery to your desktop
Change the file extension to .CAB
Use an archive tool (i.e. 7-zip) to unpack the CAB file
Within the unpacked CAB you will see a folder whose name will be the original name of your Site Template + "WebTemplate"
Within that folder will be a sub-folder whose name is just the original name of your Site Template
Within that folder is the ONet.xml file
I am new to sharepoint and have a scenario
1) I have a aspx page which displays some data from a xml.
2) The data is populated in a table in the aspx page using a code behind .cs file.
3) I use some dll's which I have made to access the data.
Note:- This things are done on my local pc which does not have a sharepoint server installed.
Now my question is
1) I want a way using which I can use this page as a webpart in a sharepoint site.
2) Can you please guide me a by which the compiled dll of the web application can be used as webpart.
Note:- I have access to put files on the server but cannot develop anything on that
You can use the User Control in SharePoint and add it to your site page..
OR
Use Visual Studio and create an empty SharePoint project (deploy as farm solution).
Then, right click project and add mapped layouts folder.
Rename this folder to whatever name you want to appear (this folder will get created on the servers layout folder in the hive) after you deploy the solution.
Add your aspx page and cs into this folder
Then, double click on package.package (its inside package, above layouts folder, under project)--> Advanced --> Add (existing assembly) and add your dll references here.(this will add the dlls under your sites sharepoint web.config.
After deploy, you can access page using: http://sharepointsite/_layouts/foldername/youraspxfilename.aspx
Let us know about the progress.
How can I move a document library from one site to another on the same server.
Both source and destination sites are under the same root site.
The Sharepoint Content Deployment Wizard is awesome for this sort of thing. Highly recommended and open source.
I've had success simply opening up explorer view on both sites and dragging and dropping. I guess it depends on how complex your migration is.
I have been told to edit this file in Sharepoint Designer:
/_layouts/KWizCom_WikiPlus/CreateNew.aspx
I found it in the Windows File Explorer at:
\12\TEMPLATE\LAYOUTS\KWizCom_Wikiplus
I can't seem to find it in Sharepoint Designer?
The _layouts folder is protected by SharePoint Designer because changing the OOTB files in that directory puts SharePoint into an unsupported state. For more information, see here and here.
For custom or third party files under _layouts, if you try to open them directly with a URL (http://myserver/_layouts/KWizCom_Wikiplus/CreateNew.aspx), you will receive an error: Files in the _layouts folder are not available for editing. You can open them in SharePoint Designer with an UNC path rather than a URL (\\myserver\c$\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\LAYOUTS\KWizCom_Wikiplus\CreateNew.aspx), but at this point SharePoint Designer is not any different than Visual Studio or Notepad as you will probably only have Code View available since ~/ and virtual directory URLs will not be resolved.
I have not used Wiki Plus, but note that not only will this change affect all web applications and site collections on the server, but any changes you make will be wiped out if an updated version of Wiki Plus is deployed to the server.
This file is effectively present in every site at http::/{site url}/_layouts/KWizCom_WikiPlus/CreateNew.aspx. To change it across all of them you would edit the file from the file system.
There are many reasons why editing the file on the file system may be a very bad idea. At minimum you might save a copy of the original and the updated file. Better still, you could put any file you're editing this way under version control.
I am working with a Sharepoint document library and I'm trying to locate the source of the document library page. I'm working on the Sharepoint server. I just can't find it, where should it be stored?
Thank you!
SharePoint does not store the pages directly in the filesystem. The mechanism is a little less straightforward.
To understand this mechanism, You have to understand the concepts of Ghosting/Unghosting, and the ASP.NET Virtual Path Provider. The SharePoint stores the pages in the Database as BLOBS, and serves them up using the ASP.NET Virtual path provider.
The ASP.NET Virtual Path Provider provides an abstraction between ASP.NET and FileSystem. Instead of getting a System.IO.FileStream object directly from the filesystem, the provider uses MapPathBasedVirtualPathProvider and the MapPathBasedVirtualFile classes to get the FileStream object.
This abstraction allows ASP.NET to serve up pages from anywhere, without having to store the pages in an actual file system. This concept is used to implement Ghosting/Unghosting which basically means having a single copy of the page, and serving them up as different pages.
SharePoint leverages this new feature in ASP.NET 2.0, along with the improved BLOB storage functionality in SQL Server 2005 to serve up pages.
Your question is not very clear...
Are you refering to the "source" code of the document library pages?
It depends if you have edited them with SharePoint Designer or not. If not they should be located under 12 hive (c:\program files\common files\microsoft shared\web server extensions\12). If any modification were done using SPD2007 the files will be stored in the content database.
...or are you refering to the "source" where the files are stored?
All the files saved in document libraries are stored in the content database as blobs in the AllUserData table.
You the pages appear as 'aspx' pages, they are not stored on the server anywhere as aspx pages. All pages are either stored in the DB as a BLOB, or 'put together' at runtime from information stored in the DB. SharePoint is an odd monster :)
If you are going to edit the look, there are a few options:
SharePoint Designer (I hate this app)
Make another 'web part page' that includes the document library inside of it while changing the content around it (easiest and best approach IMO)
make a specialized web-part (most
difficult)
SharePoint takes a whilet o get the full grasp of... it is strange.
When you create a document library template files from the "12 hive" are ghosted into the SharePoint content database (SQL). The only proper way to edit those pages at that point is to use Microsoft SharePoint Designer.
Open SharePoint Designer and open the SharePoint web site in question and you will see your document library listed in the file explorer. Under your document library you will see a Forms folder, that Forms folder is what contains the source files that are rendered to the browser.
Here is a screen shot:
If I understand what Sacha and Naspinski are saying, when I am creating a new Document library, the look of the page is retrieved from the 12 hive and stored (ghosted?) into the DB. The page is no more stored into the 12 hive, as for each document library I will have a somehow "customized page". Is that true?
There are two types of pages in SharePoint2010.Application page and site page.SharePoint store application page directly in File system.For site pages , if the page is in a ghosted state , the page in stored in the file system.If the page has been customized,the file is then stored in the content database.