SharePoint 2013 Design Manager Converted Master Page & Focus on Content



Lets suppose a designer creates the design concepts first in html and then we try to convert the html into SharePoint 2013 Master Page using Design Manager. All goes well if your html meets the basic requirements detailed in the MSDN Article http://msdn.microsoft.com/en-us/library/jj822370.aspx.

One problem I noticed is that "Focus On Content" functionality (as shown below) which hides the Quick launch bar, does not work properly.




For focus on content functionality to work, a DIV with ID "contentBox" should be the outer DIV of the default content DIV because SharePoint uses the "contentBox" id to manipulate left margins as soon as the Quick Launch is hidden. See below screenshot of out of the box Seattle master page html file.



Comparing the converted master page html from out of the box Seattle master page html revealed that this outer DIV is missing from the converted file. So, in order to make focus on content work, add the missing html into the converted master page.

Comments

Post a Comment

Popular posts from this blog

PowerApps Form for SharePoint and Access Denied Errors

Image
Error When using SharePoint's Online's customise form option to create PowerApps forms, we may encounter the error below: An error occurred on the server. Server Response: Access denied. You do not have permission to perform this action or access this resource.  This is often caused by lack of permissions on underlying lists. Scenario I was using multiple list data sources in a single PowerApps list form. Form had staged input screens for related data and a group of end users was not allowed access to the list corresponding to the last stage of input. Nonetheless, when the form opened for any user, PowerApps was trying to load all the data sources resulting in above error. The Fix I could conveniently fix the error by granting at least read-only access to end users on all lists. However, the list causing error had confidential data only restricted to few users.    An easy fix is to add an empty folder, break it's inheritance and assign less privi...
Read more

Prevent site owners from creating subsites in SharePoint 2010

Image
If your users are naughty enough and you want to keep them from adding new sub sites for a specific web application. Just follow the steps below: This is specially useful when the naughty users are site owners such as in case of My Sites. 1. From Central Administration, Go to “Manage Web Application” screen. 2. Select a web application and click the “Permission Policy” button from the ribbon. 3. A screen will pop up with all existing permission levels. 4. Select “Add Permission Policy Level” link from the screen. 5. On “Add Permission Policy Level” screen, name the permission level appropriately. 6. Under Site Permissions category, select the “Deny” option for “Create Subsites” permission and save it. 7. You will see a new Permission Policy Level in the list of existing ones. 8. From the ribbon, click “User Policy” button. 9. A screen will pop up with all existing user policies. 10. Click “Add Users” link from Policy For Web Application screen. 11. A wizard will open, allowing you to s...
Read more

Getting Page Field Value in custom publishing page layout

I wanted to create a custom publishing page layout which should render certain UI elements based on the page metadata. For e.g. a page metadata field called "Page Type" being used to display different links on pages (created with the page layout). Surprisingly, first step in the process i.e. reading the page field using SharePoint Javascript API proved to be rather painful as my good friend google wasn't willing to put it on my plate. Finally came up with some code to get this done so sharing below:---- Include this code into your custom publishing page layout to query page metadata fields within the layout: /**************************************************************************************/ var pageItem; //variable for list item of page being displayed (which uses this page layout) var pageFieldNameVar = '[internal name of a custom page field]' ; //variable for page field to be retrieved var context; // This variable will cont...
Read more