Hot answers tagged

12

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" />-->


7

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 ...


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 ...


5

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 ...


3

Typically the Style Resources Reader group has restricted read to the root style library. This group contains all authenticated users by default. First check to see if this group exists on the library and does have the all authenticated users in it. Second, check to make sure all of your assets are checked in as major versions and approved if necessary. ...


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.


3

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

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 ...


2

You should be overriding the styles with a custom CSS rather than changing the core one. Why not do that instead?


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

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 ...


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

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) -> ...


2

This is a bit tricky. There are some issues with the style menus. Basically, when it need to apply a style, it changes the vicinity as well. One thing you can do is get the class some-random-other-class and apply the parent div the 'row class' style as it describes here. Then take the parent of row class and assign cont class style there. Another good old ...


2

On Elements.xml, use ListUrl instead of ListTemplateId


2

I would argue that the reason these libraries have unique permissions is precisely the opposite of what Ankit Kumar is suggesting. In Ankit's answer: these libraries deal with configuration of the site collection and is generally used for referring any scripts /site images and any style sheets. Hence these library have unique permission where ...


2

There are two Publishing features that need to be enabled, one at the site collection level and one at the web (aka site) level. A key concept to understand here is that when you create a site collection, it has what is known as a "Root Web", which is the top site in the site collection. Because it's the top site in the site collection, it has some special ...


1

Style Library is located on the top level publishing web site. So you need to enable the publishing feature on the root site as well.


1

It is by design, I think this has some connection with Publishing. But one thing I know for sure, If you change the permission on any of these System Libraries, you will break the things in your Site collection. Typically peopler removes the Style Resource Reader group from the permission as this include the All authenticated User in it. But as soon you ...


1

Fixed the issue by following this article. I have set special permissions for the groups that require access to master's Style Library. To do that I had to stop inheriting permissions.


1

To everyone who responded: Thanks for your response! Upon my request, one of the users sent me the source code. My styles were being loaded, so my changes to the master page (and probably my earlier changes to the custom stylesheet) were there. It appears that the problem is in how I was targeting in CSS. For some background, I was attempting to add some ...


1

If you are experiencing an issue where you see the changes, but other users do not, try the following steps: Confirm that the style sheet and/or master page is checked in AND that a major version is published If required, you may need to confirm that the published version is ALSO approved Confirm that the correct master page is being loaded for users Have ...


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

This works fine for me, in the html master file : <!--SPM:<SharePoint:CssRegistration ID="CustomCSS" name="&#60;% $SPUrl:~SiteCollection/_catalogs/masterpage/css/custom.css%&#62;" After="corev15.css" runat="server"/>-->


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

What happens when you view the document library using the Open with Explorer functionality? Do you see the files there? You need to make sure you file's type attribute is set to GhostableInLibrary Ref: http://msdn.microsoft.com/en-us/library/ms441170.aspx This article provides a good walk-through for deploying branding solutions even if you do not use ...


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.



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