Tag Info

New answers tagged

1

Don't modify anything in default seattle.master . you can create copy of that master page and modify it and then set modified copy as default master page in sharpeoint designer.Here is a good link which may solve your problem. 1.Open SharePoint Designer and connect to the sitecollection where you wish to add the custom style 2.After connecting to your ...


0

Most likely the problem was in relative path which in the case of master pages is calculated in relation to the mater page gallery (/_catalogs/masterpage) instead of the site or site collection root (/). In many cases the URL such as "SiteAssets" will turn to "/_catalogs/masterpage/SiteAssets" when rendered, that will cause the unexpected behavior as ...


-2

Well, Publishing feature has got nothing to do with JQuery file. The possible reason for this behavior could be - Publishing feature will usually have additional/different tags in masterpage which could interfere with rendering of the page making it faster, I believe this is the case for you. This is the Lazy loading mechanism in which not all SharePoint ...


0

Use ScriptLink <SharePoint:ScriptLink language="javascript" name="~sitecollection/customer/_catalogs/masterpage/script/jquery-1.11.1.min.js" runat="server" Localizable="false" /> Below is how I recently implemented branding <!--SPM:<SharePoint:CssRegistration ID="CssRegistration1" name="&#60;% ...


0

The aspx markup contains references to content placeholders which should be part of master page. Try this example


1

I would first check to see if the js and css script and link tags are present in the browser. Load your site in the browser and view source. Can you find valid tags that should be telling the browser to request the css and js files? Next, use Fiddler or the net tab in Firebug and reload your page again. Are the css and js files actually being requested by ...


2

There is no explicit DENY when it comes to SharePoint permissions. In this case I would not use that particular group. I would create a new SharePoint group with all of the same members minus the individual(s) you do not want to have access to that page. I would stay away from assigning individual permissions on a user-to-user basis. You are absolutely ...


1

I am afraid you cannot achieve this as OOTB because you cannot assign distinct permissions to user in a Group. I.e if you create a SharePoint Group(defined at site collection level) and assign a permission level that will apply to all the user who are members of the group. What i am thinking, you can create another group called Members-1 and put the user ...


0

You can "remove" that element with an inline style. e.g. <div id="titlerow" style="display:none" class="ms-dialogHidden ms-core-header ms-tableRow"> or css, #titlerow{display:none;}


1

Maybe my answer is a bit late, but it might help some else.. I agree with Paul that it depends on how you activate the look. A composed look consists out of the composed look item (in the themes gallery) as well as the actual resources required for the look (.spfont, .spcolor, .master, etc.). The composed look item is there so the composed look is ...


0

We've run into this problem and have had to fix it via the master page. If you don't have that luxury, the only other thing I can think of is to have the IT folks set up a group policy to enforce it globally. http://msdn.microsoft.com/en-us/library/dn321457.aspx


0

The issue is that you should copy seattle.html which will auto create a .master page for you, and there is a link between the files. To resolve the issue, create a copy of seattle.html Now you have both a seattle_copy(1).html and seattle_copy(1).master. Next rename seattle_copy(1).html to for example test.html. A pop-up appears asking you to update ...


1

You can't change the .master file when it's bound like this, you can only edit the .html file. It will re-generate the .master when you save the .html. This is due to the Design Manager packet in SP2013. Here's the MSDN article on this feature set: http://msdn.microsoft.com/en-us/library/office/jj822363(v=office.15).aspx


0

If it's on premise and you have access to a server in the farm (either an application server or a web front end) you can leverage the SharePoint 2013 Management Shell. RDP to the box, copy up the assets, and run the SharePoint 2013 Management Shell as an administrator. Use the SharePoint 2013 commandlets and the server-side object model to upload the files ...


1

By Default you can not use different css for modal popup. Add the s4-notdlg class to the elements you don’t want to render in a popup. Using javascript you can find the page is either opened in modal popup or full window based on the situation you can apply or load different CSS. isDlg=1 is added in the URL if it is opened in a modal popup.



Top 50 recent answers are included