Tag Info

Hot answers tagged

5

Try this for the first link as it is intended to address exactly what you are seeing, though certain controls do not expand the value. <CustomAction Id="script1" Location="ScriptLink" ScriptSrc="~SiteCollection/Style%20Library/mySolution/custom1.js" /> As to whether it should be in _layouts or Style Library is a debate that has raged since the ...


4

Use SharePoint Designer and follow these steps: Connect to SharePoint site in SharePoint designer. On the left pane click All Files. Then on the list select "Style Library". Select the CSS file you want to edit and then click "Edit file". If check out is required it will do it for you after your confirmation. Make your changes, save the file, and don't ...


4

This issue caused by angle brackets "<" to fix it replace it with "&lt" as below: <!--SPM:<SharePoint:CssRegistration name="&lt;% $SPUrl:~sitecollection/_catalogs/masterpage/css/style.css %&gt;" runat="server" />-->


3

Oh, that is explained by the fact the XSL Style sheet is used by Web parts (Content Query Web Part, Table of Contents, Summary Links) available only on the Standard or Enterprise editions, in the Publishing Sites. SharePoint Foundations does not support Publishing sites.


2

On Elements.xml, use ListUrl instead of ListTemplateId


2

Reference the CSS file in the masterpage being used on the site. Open your masterpage in SharePoint Designer and add this line in the header tag: <SharePoint:CssRegistration runat="server" name="path to css file" after="corev4.css" />


2

Please look at the answers on this question too. It is a complex topic, with no "correct" answer. I think Chris O'Brien summed it up pretty well in his answer. My personal opinion is, that it depends :) In your case, since you want to use the same .js file in two (or more) site collections, I would definitely put it under "_layouts". Another question is: ...


2

i dont think your doing it properly! <SharePoint:CssRegistration Name="<%$SPrl:~sitecollection/Style Library/MyCustomTheme/mycss.css%>" runat="server" After="corev15.css"/> you were doing "<% $SPUrl=~ instead of "<%$SPrl:~ http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.webcontrols.cssregistration.aspx EDIT try ...


2

Your getting confused with the terms. Check in and out is not upload and download! when the file within any document library that is checked in than its locked to all users. You cant make any ammendments to the file and its in public view. At this point if you have the right access you can check out the file. When you check out there is now a lock in ...


2

In addition to the above answer, check in means your changes will be visible to all the users. It does not mean you will get an option to upload from local drive. If you do not have access to SharePoint Designer, you can download your css file, make changes and upload it again. For that file needs to be checked-out first (that means you are making some ...


1

I'll start out by defining two terms, the Host Web and the App Web. The SharePoint site where you install an App is called the Host Web. The SharePoint site where the SharePoint-Hosted App lives is called the App Web. The App Web is a child site of the Host Web. A SharePoint-Hosted App can automatically deploy files inside the App Web using a Module ...


1

you need to show some code! but as you already have the css running on the page it shouldnt be a huge issue! you need to first find out what element you want to show/hide! you can do this in the browser using "F12 developer" in IE or firebug in FireFox. as sharepoint is mainly supporting ie we will go with F12 developer! goto "tools" (top right) -> ...


1

You need to have contribute permission for this library, and use client object model. using (ClientContext clientContext = new ClientContext("http://yoursitecollection")) { Web web = clientContext.Web; List list = web.Lists.GetByTitle("Style library"); FileCreationInformation fileCreationInformation = new ...


1

http://kmukesh.wordpress.com/2012/07/07/upload-file-in-sharepoint-style-library-using-powershell/ ^ The above article answers my question. The boolean passed into Files.Add() dictates whether the file can be overwritten or not.


1

After doing a lot of reading and after debugging the feature receiver, I discovered two things: One of our files (which was introduced after the original version was deployed but before the current version) didn't exist in the Style Library on the SharePoint site. i.e. it had never been deployed. I checked a couple of our test servers and the file wasn't ...


1

You must first look into the best practices for branding SharePoint 2010. As PlanetWilson added earlier you should not consider changing system level css files as it will effect your entire farm. Rather create overrides for styles through a custom css file and include the link to the stylesheet in the masterpage of the site where you want your styles to be ...


1

You need to modify this class :- .ms-vh-icon Apply an override with the background-color:#fff !important and background-image:none.


1

By 'the site itself' I assume you mean that people other than you only see version 1.0. In which case, I would suggest that you make sure you are Publishing your versions, not merely checking them in.


1

Unlike traditional ASP.NET web sites, SharePoint stores much of its information in Database and retrieves them from database so there won't be able to map SharePoint Urls to IIS site structure. For more information. To understand how SharePoint modifies the ASP.NET Pipeline to achieve this, check Microsoft SharePoint Foundation as an ASP.NET Application If ...



Only top voted, non community-wiki answers of a minimum length are eligible