Tag Info

New answers tagged

1

After a while I discovered that just editing (adding a space) to the master page in SharePoint Designer fixed it. I then copied the resulting saved SharePoint Designer master page back into my solution and deployed that and it worked fine. Comparing the two files, the master page that had been provided to me originally had some extra attributes in the ...


0

Fixed this problem, instead adding new controls, I just used paddings and margins, plus, I hid iframe which created white background (needed IE specific css): -ms-filter:"progid:DXImageTransform.Microsoft.Alpha(Opacity=0)"; filter: alpha(opacity=0);


0

IMO there should be nothing you can't do with CSS. You can fairly easily discover and override default CSS styles and take advantage of selectors to do and undo styling throughout the markup. However, there are other approaches, in case you want to go that way: UseSimpleRendering JQuery.wrap()


0

perhaps you have the url wrong this Url="_catalogs\masterpage" should be Url="_catalogs/masterpage"


0

To avoid applying your customizations to dialogs add the CSS class s4-notdlg to all HTML elements you want to hide. If you are applying custom CSS to standard HTML elements you'd need to use the CSS class ms-dialog to reset them to their respective default values. If you need help to identify those elements either post the relevant code or use tools like ...


1

In new versions of SharePoint the new masterpages often contains elements of the masterpages from the previous version of SharePoint to support upgraded sites so no functionality is lost. This element is the legacy statusbar from SharePoint 2010. DeltaPageStatusBar is the one used in SharePoint 2013, making the legacy statusbar redundant. It causes no harm ...


1

this container is for displaying status informations. And you are right with your research that also information about the page status (e.g. checked out or checked in) will displayed. This is a system element of the Masterpage structure and I think required. In cause of this, it is not good or recommended to remove or rename the element. SharePoint 2013 ...


0

if you don't want to use the webprovisioned method / event receiver then their is one more alternative. You have to manually update the your master page. check the below blog for more detail. http://jeffreypaarhuis.com/2011/10/21/your-master-page-automatically-on-newly-created-subsites/


3

Create an Event Receiver. In Visual Studio, right click project => Add new item => Event Receiver => Web Events, Handle the following events: A Site is being provisioned. The following override will be generated and fire on every new site creation. Just insert the code within: public override void WebProvisioned(SPWebEventProperties properties) { ...


0

Check web.config to have the following section completely. <httpHandlers> <remove verb="*" path="*.asmx" /> <add verb="*" path="*.asmx" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" /> <add verb="*" ...


0

You could try to stick with the AdditionalPageHead DelegateControl and add something like this to your ASCX WebControl: <script runat="server"> protected override void OnLoad(EventArgs e) { base.OnLoad(e); Control formControl = Page.Form; LiteralControl literalControl = new LiteralControl(); ...


1

The probably simplest method would be to add the following CSS to your masterpage, assuming your custom searchbox has an HTML element ID of #Searchbox: <style> #aspnetForm[action*="settings.aspx"] #SearchBox, #aspnetForm[action*="addanapp.aspx"] #SearchBox { display: none; } </style>


0

Applying the CSS class s4-notdlg to all HTML elements of your custom masterpage you want to hide should do the trick.


2

Your user control needs to target a delegate control placed in the page body not AdditionalPageHead. AdditionalPageHead targets the html head element and is used for adding additional things to the head, like css and javascript files. A delegate control in the body is the appropriate place for an asp:button to live. So within the masterpage, you would ...


1

You haven't added your control. You've just registered it. After the registration you need to add another line like so: <!--SPM:<LogOut:LogOutUserControl id="LlgOutUserControl" runat="server" />-->


0

Sorry I can't post code right now, but if you are still having a problem next week, I'll post back. I created a plugin awhile back to do this: make elements sticky. It supports sharepoint and I'm currently using it in SP2013 (o365) with a few small apps. The plugin is: http://purtuga.github.io/jquery.stickOnScroll/ You will need to use the set the ...


0

I found out that I need to use another control to achieve the results I wanted. With this snippet inside the page layout (eg inside the PlaceHolderPageTitleInTitleArea placehoder) it renders me the path nicely to the current page/element: <!--MS:<asp:sitemappath runat="server" sitemapproviders="SPSiteMapProvider,SPXmlContentMapProvider" ...


1

The relationship between .html and .master is a bridge. It has been implemented so that developers who are not familiar with ASP.NET masterpages and SharePoint can use the .html file to do the changes in a "environment" they are more or less familiar with. I'm going to assume this is an on-premise solution, so yes, downloading and putting the .js file in ...


1

Aside from any API calls, why not just modify the master pages to include some javascript that sets a variable telling which master it is Var master="masters?asps"


0

When viewing SharePoint 2010 from the Chrome browser, intermittently the page will load but fail to call it’s JavaScript initialization functions leaving the page only partially functional. Put this code at the bottom of the master page file just before the closing body tag. PS : ...


1

If your comments are an actual script tag in your master page - you have a syntax error on your master page which will kill all the rest of the javascript on the page. You're missing a dot and javascript is case sensitive, so you need 'document.getElementsByName' not 'documentGetElementsByName' var logoImg = document.getElementsByName(...) I'm also ...


0

To check whether javascript is working or not do the following 1) Insert a Script Editor in your web page. 2) Enter the following code inside the editor. alert("javascript is working");


0

how you want to detect. there are couple of ways to check which master page is being used. if you don’t have the Publishing feature activated navigate to http://your_server.com/sites/examples/_Layouts/ChangeSiteMasterPage.aspx If you do have the Publishing feature enabled you can go to Master Page on the Site Settings page, under Look and Feel ...



Top 50 recent answers are included