Tag Info

New answers tagged

0

I would recommend to use Content Query Web Part (CQWP). To achieve the custom branding for each web part, you can create custom XSLT styles to be used in the CQWP. This XSLT style definition can be used across all your CQWPs.


0

What you're seeing is correct url (a subsite). From your debug image, it looks like you have apps. Apps in SP 2013 get their own site where the naming convention is ' https://domain-XXXXXXXXXXXXXXXXXX.sharepoint.com/sites/site1/subsite1' To exclude the app sites (example): while (webEnumerator.moveNext()) { var newweb = webEnumerator.get_current(); ...


0

The container should be outside Main. During rendering the actual content will get inserted inside Main. Yes the same rule applies to BootStrap. Use https://responsivesharepoint.codeplex.com/ as a starting point.


0

I tried below on my online setup and it worked properly var context = SP.ClientContext.get_current(); var web = context.get_web(); var site = context.get_site(); var rootWeb = site.get_rootWeb(); var subWebs = rootWeb.get_webs(); context.load(subWebs, 'Include(Title, Url, ServerRelativeUrl,ParentWeb)'); context.executeQueryAsync( function () { ...


5

I'm afraid there is no better solution than to use CSS: To fix the icon in the left corner via CSS is pretty much straight forward because it's no icon is just a character out of the Office 365 icon font. #O365_MainLink_NavMenu{ color: lime; } The small css will turn the icons into lime. (OK it doesn't look nice but shows perfectly how they are ...


0

You have to switch to an ASP.net master page. All placeholder that are unknown to SharePoint will be removed during the conversation from the html master page to the asp.net master page. The registration can be done using the following tags: <asp:ContentPlaceHolder id="NewPlaceHolder" runat="server"> </asp:ContentPlaceHolder>



Top 50 recent answers are included