Master page irregularities between versions?

I'm in CS6 working on a document with another person who has CS4. She has created original book-length documents. I have opened them in CS6 to make changes, and have saved them in .idml for her. When she saves the .idml and reopens it, however, some of the master page items are showing up where they should not (page numbers and runningheads on blank pages, for instance). They don't show up in my CS6 file, the .idml file when I open it in CS6, or in the pdf I made from the CS6 file, but they are in her saved .idml files, and it's a problem I can recreate opening them in CS4 and saving them. This makes both of us nervous that other mystery problems will crop up in these files. Anyone know what's going on here? Thanks in advance for any info on this.

Hi There!
Unfortunately, you will find inconsistencies between most versions, which is only due to the improved features (some will disagree) as they are added. I know I shouldn't bring this up, but do you still have CS4/CS5/CS5.5? If so, as Peter states, you should just open any projects up in their respective app. Sorry if I've been redundant...
Cheers!
-Mikey

Similar Messages

How to reduce the weight of SharePoint master page.

Hi
I have given my sharePoint master page (without any additional content) & source-generated in browser.
we want to reduce the weight of the page(source)
can anyone tell me what are the things from the below-master page I can remove.
our master page is for simple static html pages (so no need of view state etc.)
mailny there are lot of js links. can we reduce this. if so what link we can remove?
and Iam getting viewstate also(is this for ribbon?)
==================Eg. We want to remove ==================================
<input type="hidden" name="__VIEWSTATE" id="__VIEWSTATE" value="/wEPDwUBMA9kFgJmD2QWAgIBD2QWBgIBD2QWBAIFD2QWAmYPZBYCAgMPFgIeE1ByZXZpb3VzQ29udHJvbE1vZGULKYgBTWljcm9zb2Z0LlNoYXJlUG9pbnQuV2ViQ29udHJvbHMuU1BDb250cm9sTW9kZSwgTWljcm9zb2Z0LlNoYXJlUG9pbnQsIFZlcnNpb249MTUuMC4wLjAsIEN1bHR1cmU9bmV1dHJhbCwgUHVibGljS2V5VG9rZW49NzFlOWJjZTExMWU5NDI5YwFkAhEPZBYCAgMPZBYCZg9kFgJmDzwrAAYAZAIFD2QWAgICD2QWAgICD2QWBgIDD2QWAgIBD2QWAmYPDxYCHgdWaXNpYmxlaGRkAgUPZBYCAgMPZBYCZg9kFgQCAg9kFgoCAQ8WBh4TQ2xpZW50T25DbGlja1NjcmlwdAWHAUVuc3VyZVNjcmlwdEZ1bmMoJ3NoYXJpbmcuanMnLCAnRGlzcGxheVNoYXJlZFdpdGhEaWFsb2cnLCBmdW5jdGlvbiAoKSB7IERpc3BsYXlTaGFyZWRXaXRoRGlhbG9nKCdcdTAwMmZzaXRlc1x1MDAyZmZpcnN0YmFua1x1MDAyZicpOyB9KR4oQ2xpZW50T25DbGlja1NjcmlwdENvbnRhaW5pbmdQcmVmaXhlZFVybAWHAUVuc3VyZVNjcmlwdEZ1bmMoJ3NoYXJpbmcuanMnLCAnRGlzcGxheVNoYXJlZFdpdGhEaWFsb2cnLCBmdW5jdGlvbiAoKSB7IERpc3BsYXlTaGFyZWRXaXRoRGlhbG9nKCdcdTAwMmZzaXRlc1x1MDAyZmZpcnN0YmFua1x1MDAyZicpOyB9KR4YQ2xpZW50T25DbGlja05hdmlnYXRlVXJsZGQCAw8WCB8BaB8CBXt3aW5kb3cubG9jYXRpb24gPSAnamF2YXNjcmlwdDpFbnN1cmVDaGVja291dEFuZENoYW5nZUxheW91dE1vZGVUb0VkaXQoXCdhOWYzZTQ0MS1iMDkwLTRiODctODRkMi1mYWEyMzZhZjAxZDRcJywyOSxmYWxzZSk7JzsfA2QfBAVmamF2YXNjcmlwdDpFbnN1cmVDaGVja291dEFuZENoYW5nZUxheW91dE1vZGVUb0VkaXQoXCdhOWYzZTQ0MS1iMDkwLTRiODctODRkMi1mYWEyMzZhZjAxZDRcJywyOSxmYWxzZSk7ZAIFDxYCHwFoZAILDxYCHwFoZAISD2QWAmYPDxYGHhxQcmV2aW91c0F1dGhvcmluZ0l0ZW1WZXJzaW9uBQIxMR4aUHJldmlvdXNBdXRob3JpbmdJdGVtT3duZXIFAjI5HhxQcmV2aW91c0F1dGhvcmluZ0NvbnRyb2xNb2RlCysEAWRkAgMPDxYCHglBY2Nlc3NLZXkFAS9kZAIHD2QWAgIBD2QWAgIBD2QWCAIBDw8WBB4EXyFTQgICHghDc3NDbGFzcwUXbXMtcHJvbW90ZWRBY3Rpb25CdXR0b25kZAIDD2QWAmYPDxYEHwkCAh8KBRdtcy1wcm9tb3RlZEFjdGlvbkJ1dHRvbmRkAgUPDxYGHwFoHwkCAh8KBRdtcy1wcm9tb3RlZEFjdGlvbkJ1dHRvbmRkAgcPFgIfAWhkAhQPZBYCAgEPFgIfAAsrBAFkZC2rCaEGQ5Bkx348fvXxdWvFUanr0OGG+QIgiKd2k5Tz"
/>
<script type="text/javascript" src="/_layouts/15/init.debug.js?rev=Hj977U2n5ZIN5oS6ATVanQ%3D%3D"></script>
<script type="text/javascript" src="/ScriptResource.axd?d=HCvGktx1A8A1lPZ_uUB9cGFlYk3HE_mWfN2BaMhCiXhEC0xNyXeG83EOG9vsM4AmfPSa5taspY6EXh9PxbHLYzWtkcG86D_c9EC6SLdKd37Gu3SyyGjJCi_sI2xSqbDH3NIT9xXdebl4q-d4eNVUlwffzNurI4I_1RnznQoxjFJX02JqTYb-le9qw53raxgq0&t=6119e399"></script>
<script type="text/javascript" src="/_layouts/15/blank.js?rev=ZaOXZEobVwykPO9g8hq%2F8A%3D%3D"></script>
<script type="text/javascript" src="/ScriptResource.axd?d=b-pFE2MM677quNb0_5VStXi9opok7kYtAYU_KkApt4G5-TnDhtoCVwrUmOen_-CqUIisaQf36RheGO3mh0InVT5q6WDz0yEh2SpgFy4NS-3ks2YPydbrpbaHUUQOeZBvxZkIDclTh0KezpCLIOKGHGtP1WozsMT5yy77vMh0mvBgk_sgs01gInqNy4LwGjXz_IiAvU7rcFTwLtwaokhh3A2&t=6119e399"></script>
<script type="text/javascript">RegisterSod("initstrings.js", "\u002f_layouts\u002f15\u002f1033\u002finitstrings.debug.js?rev=I1g8M0L6SHEhFP0dpcdMAg\u00253D\u00253D");</script>
<script type="text/javascript">RegisterSod("strings.js", "\u002f_layouts\u002f15\u002f1033\u002fstrings.debug.js?rev=Iggk2Q7N9CL63RKBTScOLg\u00253D\u00253D"); RegisterSodDep("strings.js", "initstrings.js");</script>
<script type="text/javascript">RegisterSod("sp.init.js", "\u002f_layouts\u002f15\u002fsp.init.debug.js?rev=K\u00252BPANXVo5GtElzSq70zhSw\u00253D\u00253D");</script>
<script type="text/javascript">RegisterSod("sp.res.resx", "\u002f_layouts\u002f15\u002fScriptResx.ashx?culture=en\u00252Dus\u0026name=SP\u00252ERes\u0026rev=yNk\u00252FhRzgBn40LJVP\u00252BqfgdQ\u00253D\u00253D");</script>
<script type="text/javascript">RegisterSod("sp.ui.dialog.js", "\u002f_layouts\u002f15\u002fsp.ui.dialog.debug.js?rev=EmVQKmKF\u00252BmjLtrcRjI3zww\u00253D\u00253D"); RegisterSodDep("sp.ui.dialog.js", "sp.init.js");
RegisterSodDep("sp.ui.dialog.js", "sp.res.resx");</script>
<script type="text/javascript">RegisterSod("core.js", "\u002f_layouts\u002f15\u002fcore.debug.js?rev=HMlx90NziE60dQZ6I9yj2Q\u00253D\u00253D"); RegisterSodDep("core.js", "strings.js");</script>
<script type="text/javascript">RegisterSod("menu.js", "\u002f_layouts\u002f15\u002fmenu.debug.js?rev=bxANkB9\u00252Fa1ztnGu\u00252FWXYvaw\u00253D\u00253D");</script>
<script type="text/javascript">RegisterSod("mQuery.js", "\u002f_layouts\u002f15\u002fmquery.debug.js?rev=eg22Wtb4UOCtZAR\u00252BS9foWQ\u00253D\u00253D");</script>
<script type="text/javascript">RegisterSod("callout.js", "\u002f_layouts\u002f15\u002fcallout.debug.js?rev=IF6FsxpN89rIqqbAN4WzEA\u00253D\u00253D"); RegisterSodDep("callout.js", "strings.js"); RegisterSodDep("callout.js",
"mQuery.js"); RegisterSodDep("callout.js", "core.js");</script>
<script type="text/javascript">RegisterSod("clienttemplates.js", "\u002f_layouts\u002f15\u002fclienttemplates.debug.js?rev=lLXTuIkEXZ6o9j8Ab8CDAQ\u00253D\u00253D"); RegisterSodDep("clienttemplates.js", "initstrings.js");</script>
<script type="text/javascript">RegisterSod("sharing.js", "\u002f_layouts\u002f15\u002fsharing.debug.js?rev=i3xiltVGmH60p2cMnA\u00252Fqkw\u00253D\u00253D"); RegisterSodDep("sharing.js", "strings.js"); RegisterSodDep("sharing.js",
"mQuery.js"); RegisterSodDep("sharing.js", "clienttemplates.js"); RegisterSodDep("sharing.js", "core.js");</script>
<script type="text/javascript">RegisterSod("suitelinks.js", "\u002f_layouts\u002f15\u002fsuitelinks.debug.js?rev=vvrDF6GGwC8iHM1ukVFXjw\u00253D\u00253D"); RegisterSodDep("suitelinks.js", "strings.js");
RegisterSodDep("suitelinks.js", "core.js");</script>
<script type="text/javascript">RegisterSod("sp.runtime.js", "\u002f_layouts\u002f15\u002fsp.runtime.debug.js?rev=VFkBZgkYpbAZS6abSrBqIg\u00253D\u00253D"); RegisterSodDep("sp.runtime.js", "sp.res.resx");</script>
<script type="text/javascript">RegisterSod("sp.js", "\u002f_layouts\u002f15\u002fsp.debug.js?rev=IR\u00252FvhMqBTNIUqECkE3HAZw\u00253D\u00253D"); RegisterSodDep("sp.js", "sp.runtime.js"); RegisterSodDep("sp.js",
"sp.ui.dialog.js"); RegisterSodDep("sp.js", "sp.res.resx");</script>
<script type="text/javascript">RegisterSod("userprofile", "\u002f_layouts\u002f15\u002fsp.userprofiles.debug.js?rev=SFEKakO2PFSjG0qOjeB4Fw\u00253D\u00253D"); RegisterSodDep("userprofile", "sp.runtime.js");</script>
<script type="text/javascript">RegisterSod("followingcommon.js", "\u002f_layouts\u002f15\u002ffollowingcommon.debug.js?rev=QlAqfMuxiHOMCoHCTvpncg\u00253D\u00253D"); RegisterSodDep("followingcommon.js", "strings.js");
RegisterSodDep("followingcommon.js", "sp.js"); RegisterSodDep("followingcommon.js", "userprofile"); RegisterSodDep("followingcommon.js", "core.js"); RegisterSodDep("followingcommon.js",
"mQuery.js");</script>
<script type="text/javascript">RegisterSod("profilebrowserscriptres.resx", "\u002f_layouts\u002f15\u002fScriptResx.ashx?culture=en\u00252Dus\u0026name=ProfileBrowserScriptRes\u0026rev=PEn82Mp1iMY2FYDo2ApuAQ\u00253D\u00253D");</script>
<script type="text/javascript">RegisterSod("sp.ui.mysitecommon.js", "\u002f_layouts\u002f15\u002fsp.ui.mysitecommon.debug.js?rev=Cbv5CFidFecFvehmi\u00252BlK\u00252Bg\u00253D\u00253D"); RegisterSodDep("sp.ui.mysitecommon.js",
"sp.init.js"); RegisterSodDep("sp.ui.mysitecommon.js", "sp.runtime.js"); RegisterSodDep("sp.ui.mysitecommon.js", "userprofile"); RegisterSodDep("sp.ui.mysitecommon.js", "profilebrowserscriptres.resx");</script>
<script type="text/javascript">RegisterSod("browserScript", "\u002f_layouts\u002f15\u002fie55up.debug.js?rev=pVBnO13dp7gFq\u00252FZalDmroA\u00253D\u00253D"); RegisterSodDep("browserScript", "strings.js");</script>
<script type="text/javascript">RegisterSod("inplview", "\u002f_layouts\u002f15\u002finplview.debug.js?rev=1gK1dBB5qS2N78GzeDqwjA\u00253D\u00253D"); RegisterSodDep("inplview", "strings.js"); RegisterSodDep("inplview",
"core.js"); RegisterSodDep("inplview", "sp.js");</script>
<script type="text/javascript">RegisterSod("offline.js", "\u002f_layouts\u002f15\u002foffline.debug.js?rev=kGGV\u00252F1CHiLpCkfHyY3G5ZA\u00253D\u00253D");</script>
<script type="text/javascript">RegisterSod("sp.core.js", "\u002f_layouts\u002f15\u002fsp.core.debug.js?rev=GMkzPiQMx626LcptMQNo7g\u00253D\u00253D"); RegisterSodDep("sp.core.js", "strings.js"); RegisterSodDep("sp.core.js",
"sp.init.js"); RegisterSodDep("sp.core.js", "core.js");</script>
<script type="text/javascript">RegisterSod("cui.js", "\u002f_layouts\u002f15\u002fcui.debug.js?rev=l3Pt78EOb2DRXM4xdwfiIA\u00253D\u00253D");</script>
<script type="text/javascript">RegisterSod("ribbon", "\u002f_layouts\u002f15\u002fsp.ribbon.debug.js?rev=UX8Ji7oewSCpI\u00252BHzzUQQqA\u00253D\u00253D"); RegisterSodDep("ribbon", "strings.js"); RegisterSodDep("ribbon",
"core.js"); RegisterSodDep("ribbon", "sp.core.js"); RegisterSodDep("ribbon", "sp.js"); RegisterSodDep("ribbon", "cui.js"); RegisterSodDep("ribbon", "sp.res.resx"); RegisterSodDep("ribbon",
"sp.runtime.js"); RegisterSodDep("ribbon", "inplview");</script>
<script type="text/javascript">RegisterSod("WPAdderClass", "\u002f_layouts\u002f15\u002fwpadder.debug.js?rev=02m3ocMoqeXw1OPHrzEAYw\u00253D\u00253D");</script>
<link type="text/xml" rel="alternate" href="/sites/firstbank/_vti_bin/spsdisco.aspx" />
-==============================master page=====================================
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html[]>
<html xmlns:mso="urn:schemas-microsoft-com:office:office" xmlns:msdt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882">
<head>
<meta http-equiv="X-UA-Compatible" content="IE=10" />






<meta name="GENERATOR" content="Microsoft SharePoint" />
<meta http-equiv="Content-type" content="text/html; charset=utf-8" />
<meta http-equiv="Expires" content="0" />







firstbank








<link rel="stylesheet" type="text/css" href="assets/css/corev15V1.css" />








<script type="text/javascript" src="http://win-6q11jqp4kh5:1111/_layouts/15/init.js?rev=zwpf9CD1m7am6imImmQglQ%3D%3D">//<![CDATA[//]]></script><script
type="text/javascript">
//<![CDATA[RegisterSod("initstrings.js",
"\u002f_layouts\u002f15\u002f1033\u002finitstrings.js?rev=uNmvBiHdrBzcPQzXRpm\u00252FnQ\u00253D\u00253D");//]]></script><script type="text/javascript">
//<![CDATA[RegisterSod("strings.js", "\u002f_layouts\u002f15\u002f1033\u002fstrings.js?rev=cSu1pcWiRc999fyCNzJplg\u00253D\u00253D");RegisterSodDep("strings.js",
"initstrings.js");//]]></script><script type="text/javascript">
//<![CDATA[RegisterSod("sp.init.js", "\u002f_layouts\u002f15\u002fsp.init.js?rev=QI1yUCfCoUkadL93jNZLOg\u00253D\u00253D");//]]></script><script type="text/javascript">
//<![CDATA[RegisterSod("sp.res.resx",
"\u002f_layouts\u002f15\u002fScriptResx.ashx?culture=en\u00252Dus\u0026name=SP\u00252ERes\u0026rev=yNk\u00252FhRzgBn40LJVP\u00252BqfgdQ\u00253D\u00253D");//]]></script><script type="text/javascript">
//<![CDATA[RegisterSod("sp.ui.dialog.js",
"\u002f_layouts\u002f15\u002fsp.ui.dialog.js?rev=0xf6wCIW4E1pN83I9nSIJQ\u00253D\u00253D");RegisterSodDep("sp.ui.dialog.js", "sp.init.js");RegisterSodDep("sp.ui.dialog.js", "sp.res.resx");//]]></script><script
type="text/javascript">
//<![CDATA[RegisterSod("core.js",
"\u002f_layouts\u002f15\u002fcore.js?rev=\u00252FmcwmyWAFSbQRHlXU4BIBg\u00253D\u00253D");RegisterSodDep("core.js", "strings.js");//]]></script><script type="text/javascript">
//<![CDATA[RegisterSod("menu.js", "\u002f_layouts\u002f15\u002fmenu.js?rev=pcr83s11QGFA2kLt5rDQ1g\u00253D\u00253D");//]]></script><script
type="text/javascript">
//<![CDATA[RegisterSod("mQuery.js",
"\u002f_layouts\u002f15\u002fmquery.js?rev=VYAJYBo5H8I3gVSL3MzD6A\u00253D\u00253D");//]]></script><script type="text/javascript">
//<![CDATA[RegisterSod("callout.js", "\u002f_layouts\u002f15\u002fcallout.js?rev=ryx2n4ePkYj1\u00252FALmcsXZfA\u00253D\u00253D");RegisterSodDep("callout.js",
"strings.js");RegisterSodDep("callout.js", "mQuery.js");RegisterSodDep("callout.js", "core.js");//]]></script><script type="text/javascript">
//<![CDATA[RegisterSod("clienttemplates.js", "\u002f_layouts\u002f15\u002fclienttemplates.js?rev=vtrc0n3sjgxKB4WQrCEeaA\u00253D\u00253D");RegisterSodDep("clienttemplates.js",
"initstrings.js");//]]></script><script type="text/javascript">
//<![CDATA[RegisterSod("sharing.js", "\u002f_layouts\u002f15\u002fsharing.js?rev=EojJW\u00252FD7vytDfjPyrFWfzw\u00253D\u00253D");RegisterSodDep("sharing.js", "strings.js");RegisterSodDep("sharing.js",
"mQuery.js");RegisterSodDep("sharing.js", "clienttemplates.js");RegisterSodDep("sharing.js", "core.js");//]]></script><script type="text/javascript">
//<![CDATA[RegisterSod("suitelinks.js", "\u002f_layouts\u002f15\u002fsuitelinks.js?rev=LW8KECQqnuLhetUeLd3iSg\u00253D\u00253D");RegisterSodDep("suitelinks.js",
"strings.js");RegisterSodDep("suitelinks.js", "core.js");//]]></script>

















<link type="text/xml" rel="alternate" href="http://win-6q11jqp4kh5:1111/sites/firstbank/_vti_bin/spsdisco.aspx" />







[ MyLinksRibbon "ctl79" ][ SpellCheckV4Action "ctl80" ][ PublishingInformationControl "ctl81" ][ RTEV4Action "ctl82" ][ ProjectPolicyStatusBar "ctl83" ][ InsertMediaRibbonButton "ctl84" ][ SeoBrowserTitle
"ctl85" ][ SeoCustomMeta "ctl86" ]<link rel="canonical" href="http://win-6q11jqp4kh5:1111/sites/firstbank/_catalogs/masterpage/FirstBankHtml.html" />[ SeoNoIndex "ctl88" ][ SeoKeywords "ctl89"
][ SeoMetaDescription "ctl90" ][ SiteStatusBar "ctl91" ][ FollowingScriptControl "ctl92" ]






<link rel="stylesheet" type="text/css" href="assets/css/corev15V1.css" />




<table cellpadding="4" cellspacing="0" style="font:messagebox;color:buttontext;background-color:buttonface;border:
solid 1px;border-top-color:buttonhighlight;border-left-color:buttonhighlight;border-bottom-color:buttonshadow;border-right-color:buttonshadow"><tr><td nowrap="nowrap"><span style="font-weight:bold">SPWebPartManager</span>
- Unnamed63</td></tr><tr><td></td></tr></table>




<meta charset="utf-8" />

<script src="/_layouts/15/SP.Runtime.js">//<![CDATA[
//]]>
</script>
<script src="/_layouts/15/SP.js">//<![CDATA[
//]]>
</script>
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no" />

</head>
<body>



<div id="ms-designer-ribbon">

<div class="DefaultContentBlock" style="background:rgb(0, 114, 198); color:white; width:100%; padding:8px; height:64px; ">The SharePoint
ribbon will be here when your file is either previewed on or applied to your site.</div>
</div>

<div id="s4-workspace">
<div id="s4-bodyContainer">
<div data-name="ContentPlaceHolderMain">









</div>
</div>
</div>
</body>
</html>
S H A J A N

I am not sure if you can really disable something but try to use minimal master page. It will increase performance a lot.
http://www.themossblog.com/sharepoint-general/10-tips-to-improve-sharepoint-performance
http://www.chaitumadala.com/2012/01/how-to-tune-sharepoint-2010-server-for.html
http://sharepointroot.com/2008/12/07/improving-sharepoint-performance-publishing/
If this helped you resolve your issue, please mark it Answered
but our client dont want to change the masterpage. he want to remove content from his existing master page
S H A J A N

How to add left navigation to Custom Master page for Office 365

Hi,
I have created a master page using html, it looks good,
But I could not see the left navigation, which I would like to have.
below is my html page which converted to a master page:
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html[]>
<html xmlns:mso="urn:schemas-microsoft-com:office:office" xmlns:msdt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882">
    <head>
        <meta http-equiv="X-UA-Compatible" content="IE=10" >
        
        
        
        
        <meta name="GENERATOR" content="Microsoft SharePoint" >
        <meta http-equiv="Content-type" content="text/html; charset=utf-8" >
        <meta http-equiv="Expires" content="0" >
        
        
        
            
                
                
            
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
            
            
            
            
            
            
        
        
        
        
            
            
        
        
        <meta name="viewport" content="width=device-width" >
        
        
    </head>
    <body id="test-100">
        
        
        
        
            <div id="TurnOnAccessibility" style="display:none" class="s4-notdlg noindex">
                <a id="linkTurnOnAcc" href="#" class="ms-accessible ms-acc-button" onclick="SetIsAccessibilityFeatureEnabled(true);UpdateAccessibilityUI();document.getElementById('linkTurnOffAcc').focus();return
false;">
                    
                    
                </a>
            </div>
            <div id="TurnOffAccessibility" style="display:none" class="s4-notdlg noindex">
                <a id="linkTurnOffAcc" href="#" class="ms-accessible ms-acc-button" onclick="SetIsAccessibilityFeatureEnabled(false);UpdateAccessibilityUI();document.getElementById('linkTurnOnAcc').focus();return
false;">
                    
                    
                </a>
            </div>
        
        <div id="ms-designer-ribbon">
            
            <div class="DefaultContentBlock" style="background:rgb(0, 114, 198); color:white; width:100%; padding:8px; height:64px;
overflow:hidden;">The SharePoint ribbon will be here when your file is either previewed on or applied to your site.</div>
        </div>
        
            
            
        
        
        <div id="s4-workspace">
            <div id="s4-bodyContainer">
                <header>
                <div data-name="ContentPlaceHolderMain">
                    
                    
                    
                        
                        
                    
                    
                </div>
            </div>
        </div>
    </body>
</html>
Any suggestions here....
Thanks in Advance.
PMMR

Hi,
The Navigation control can be added into your HTML page in the Snippet Gallery:
The two links below about how to create HTML master page and adding snippets needed into it for your reference:
http://borderingdotnet.blogspot.jp/2012/12/how-to-create-html-masterpage-for.html
http://msdn.microsoft.com/en-us/library/office/jj822370(v=office.15).aspx
Feel free to reply if there still any question.
Best regards,
Patrick
Patrick Liang
TechNet Community Support

Working with master pages and page layout, what I have been doing wrong

I have worked on customizing the page layout and the master pages for a couple of site collections.
But now I read two restrictions which I was not following 100%:-
I should avoid directly modifying any default templates, and instead of that I should take a copy and modify the copy. So that any future updates will not override my modifications.
Also I should avoid directly modifying the .aspx files, and instead of that I should edit the html file which will automatically reflect on the .aspx files.
So currently I have these cases inside my SharePoint sites:-
Inside my enterprise wiki site collection, I have being modifying the Enterprisewiki.aspx page layout, for example I added new columns such as Page title and I remove the page rating, also the chnaged the color and format for the page fields.
Inside my team site I took a copy of the seatle.master master page (I name it seatle_copy.master)and I apply my modification to the seatle_copy.master directly and not inside the .html file. Even I do not have a html version for the modified seatle_copy.master?
So can anyone advice how I can fix these two issues. For the first issue how I can make sure that my modifications to the EnterPriseWiki.aspx page layout will not get override during any future update.
also how I can generate an html version for my current seatle_copy.master file so that I can modify the seatle_copy.html instead of the seatle_copy.master in the future?
Please can anyone advice?

Hi johnjohn123,
1. I would definitely make a copy of the EnterpriseWiki.aspx page layout and make changes to that. You can then set your pages to use your custom page layout. Typically, I provision these via Visual Studio and a module for uploading them to the SharePoint
master page gallery.
2. For the master page, the html version is new to 2013 and is meant to simplify branding, however, it's not required. You can still work within master pages and provision those via features if you'd like. The key is to create your own master page and never
modify the default.
If you need code samples for any of the above, let me know and I can supply it.
Shereen Qumsieh http://sharepointdeveloperhq.com @msshushu

Applying Changes to Master Pages

Is there any way to apply a change to a master page to a topic that is already linked to that master page? I tried removing the link, making the change to the master page, and then re-linking the topic, but it the "old" version of the master page gets applied. I also tried making a change to the master page and then using the Apply To All feature when generating, but again, the version applied is the "old" master page.

Hello again Paul
Okay, so the fact you are referring to them as Master Pages would seem to imply you are using RoboHelp 8. When you edit a Master Page in this version you note that there are "Placeholders" on the page. There is a Placeholder for the Body text. You may also add other Placeholders as well as Headers and Footers.
If you inserted the button bar inside the Body placeholder, it would only be related to topics you created using the Master Page as a template. If you later changed this in some way, for example removing or adding a button, it would only be reflected in topics you later created after making the change. Topics created prior to the change will be unfazed.
You can change this behavior by inserting the element just above the Body Placeholder. When content is outside the Placeholder, it gets copied to any topic associated with the Master Page.
As for RoboHelp being "helpful" and leaving the code alone, you are on your own with that. Trial and error will tell you whether RoboHelp will clobber the changes to the code. About the only way to ensure that doesn't happen is by using some custom JavaScript to "write in" the desired code.
Cheers... Rick
Helpful and Handy Links
RoboHelp Wish Form/Bug Reporting Form
Begin learning RoboHelp HTML 7 or 8 moments from now - $24.95!
Adobe Certified RoboHelp HTML Training
SorcererStone Blog
RoboHelp eBooks

Master Pages and Buttons - Bug and Fix Request

I think I'm the only person in the world who has encountered this bug, and I've filled out the bug report form on the Adobe site twice in a couple of years.
Just wondering if anyone else has encountered it, and I'm curious to know if it still exists in Creative Cloud (I'm still using CS6). However, I think this bug appeared in CS5.5, prior to that, results were as one would expect.
So here's the gist of it . . .
Prior versions of InDesign allowed you to put a button on a Master Page, then upon export to PDF the page number would be appended to the button name. CS6 appends random numbers to the button names on export. (It seems the number appended to the button names is the instance count of the button in question.) This problem becomes incrementally worse if you use different combinations of master pages, some with buttons and some without.
Steps to reproduce bug:
Create a button, named "menubutton" and add it to a master page
Apply that master page to 10 pages.
Export the ID file to PDF enabling buttons and interactive elements.
Check the button names in the PDF from Acrobat
Results:
In CS6, this now appends the page number, and an arbitrary number to the button name. CS6 results are like such: "menubutton.Page 1", "menubutton.Page 21", "menubutton.Page 32", "menubutton.Page 43", etc.
Expected results:
The button names should become "menubutton.Page 1", "menubutton.Page 2", "menubutton.Page 2" , etc. (As in prior ID versions)
The problem becomes a lot worse when you use combinations of master pages . . . for example:
Master A – contains one button – menubutton
Master B – contains one button – otherbutton
Apply those masters to alternating pages, like below and export to PDF, this will be the crazy result:
Page 1 (A)        “menubutton.Page 1”
Page 2 (B)        “otherbutton.Page 2”
Page 3 (A)        “menubutton.Page 31”
Page 4 (B)        “otherbutton.Page 41”
Page 5 (A)        “menubutton.Page 52”
Page 6 (B)        “otherbutton.Page 62”
Page 7 (A)        “menubutton.Page 73”
Page 8 (B)        “otherbutton.Page 83”
So, can anyone else attest to this? It makes scripting buttons incredibly hard!

Hi johnjohn123,
1. I would definitely make a copy of the EnterpriseWiki.aspx page layout and make changes to that. You can then set your pages to use your custom page layout. Typically, I provision these via Visual Studio and a module for uploading them to the SharePoint
master page gallery.
2. For the master page, the html version is new to 2013 and is meant to simplify branding, however, it's not required. You can still work within master pages and provision those via features if you'd like. The key is to create your own master page and never
modify the default.
If you need code samples for any of the above, let me know and I can supply it.
Shereen Qumsieh http://sharepointdeveloperhq.com @msshushu

How can I link text boxes between different Master Pages in InDesign?

I want to link text boxes back and forth between different Master Pages in InDesign. How can I do this?

I'm interested to know what it is you're trying to achieve - can you explain what you want your text to do?
Regards,
Malcolm

Copying master pages between documents.

I Am laying out a book with 36 chapters and I formatted my master page and completed Chapter One. Chapter Two is a new document and I want to carry over Master-A to each successive one. I believe there must be a way to do it, but nothing I have tried works. I am using Windows 7 and InDesign 5.5, version 7.5.

I created a new master page template and added my first chapter to it. Everything except the chapter title from the master page footer appeared on the pages. I went to the master pages and deleted the chapter title and then replaced it and reapplied the master to all pages. The chapter title still did not come up on the document pages.

Unable to access version history of master page

Hi,
I think i totally messed up the master pages, i'm not sure what i did, but i edited seattle.html master page and published it. Now i try to access the site, i get error : "Sorry something went wrong....blah..blah "
Now when i tried to restore the version history, it throws an error shown below. Please help me to resolve this. I think i just did it in production server.. a big blunder i guess.
Many thanks !

Hi Alex,
Thanks for your response.
In anxiety i was trying many different things and i found a strange thing. The first screenshot below shows how i tried it earlier. I right click (after checking out the file of course) on the seattle.html and then when i select version history, it doesn't
work.
But in the second screenshot if rather than right clicking, i just click on the file name and then from the next screen, at the right side there is a Version History table listing all the versions. So when i select a version, the Restore button activates
on the Ribbon and now i can restore from here without any issue.
And there is another approach, we can restore through design manager. But if your entire master page is screwed up totally, then you won't be able to go to your _layouts/15/DesignMasterPages.aspx in the first place.
So i would suggest people to try the second method (from designer pane).
Shot 1:
Shot 2:
But in any case, i truly acknowledge your advice and it was a close shave for me :) It was very risky. I'm going ahead with your advice and in fact need some more advice.
I'm going to do the below steps and need your advice on this:
1. I will make a copy of seattle.html and i guess it will create .master for itself.
2. Now i right click on the seattle.html and reset to site definition. So i guess it will like what it was by default.
3. Now I associate the copy i made with my site.
Thanks again !
Kind Regards,
prajK

Difference between Body pages and Master Pages in Adobe forms?

Hi SAP Gurus,
Please can any one tell me the difference between the Body pages and Master Pages in Adobe Forms?
In what scenarios we use Body pages and Master pages?
And also please tell me what is Boiler plates? When these used?
Thanks and Regards
Abinava Siri..

Hi,
Master Pages:
Does not included in the content area
Master page we will design logo,company address and header information
Here we can desing footer information
whatever you desing in the master page it will show for all the body pages
Body pages:
Included in the content area
Where we can design table data, it should repeat for line times.
Regards
Ramakrishna Pathi

Using Version ES4 Livecycle added master page

Using Version ES4 Livecycle added master page and now the master page is showing on PDF view as a blank page. How to remove?

There is probably a better way to do this, but I found a work around. I set the fields on the master page to "Use Global Data" in the Binding tab. This means that the value for that field will be the same for any field with the same name. Then, on my main page, I have a hidden field with the same name that I can populate with ColdFusion and the value will also show in the master page.
If anyone has a more elegant way to do this, please respond. I am new to LiveCycle and I'm sure there are a lot of features that I am not aware of that could help me.

Replace vertical navigation in custom master page from snippet gallery

Hi.
I'm creating a new master page from seattle.master and I'm trying to implement a customized snippet from the snippet gallery into the master page code without success. The following line is straight from a seattle.master page:
<div id="sideNavBox" class="ms-dialogHidden ms-forceWrap ms-noList">
From here, I see where I think the replacement snippet should go; however, there are discrepancies between the structure of the snippet and the code I'm replacing. Also, the snippet from the gallery is calling some ASP registrations that I
don't see in the original master page code.
How can I insert my custom vertical navigation snippet into this master page?

Hi,
You want to replace the entire <div id="sideNavBox" /> found in your custom HTML Master Page. Your custom vertical navigation will need to replace the entire container and all of its child controls.
Your custom vertical navigation snippet should start similar to:
<div data-name="QuickLaunch">



<div id="sideNavBox" class="ms-dialogHidden ms-forceWrap ms-noList">
Design Manager's snippet manager adds the Register tags into the snippet so that the snippet is self-contained. Your HTML Master Page likely contains these Register tags already but you can leave them as Design Manager will handle any duplicates for you.
The structure of the snippet itself appears different because the seattle.html HTML Master Page includes modifications.
Eric Overfield - PixelMill -
ericoverfield.com -
@EricOverfield

How do I create a Master Page?

I'm creating a page layout document with each page containing one or two photos on the left side and a bulleted list for each photo on the right. The doc is 150 pages and I'd like to create two different master pages - a one-photo layout and a two-photo layout. I can't find how to create a master page.
I have added guide lines and then duplicate the page and change the photo and text, but I'd love to create a set of master pages. Seems like a good skill to have. Thanks for any help.

The Pages09_UserGuide.pdf does a poor job of explaining how to create a working template with master layouts.
For a start *Chapter 13 Designing Your Own Document Templates* doesn't acknowledge the difference between *Word Processing mode* and *Layout mode* with all instructions being only for Word Processing mode and even those are incomplete.
Pages in *Layout mode* does not have master pages it has what you might call an internal template, with the page layout being inserted from the Pages button on the toolbar or:
+Menu > Insert > Pages > select from thumbnail+
This is like a page duplicator, with none of it being retrospective as far as I can see. Once you insert a page, changing the original Pages layout does not actually change any page based on it. To change an existing Page design you have to remember its name perfectly down to case sensitive and save a new version over the existing version or go to a completely separate menu item to delete and add designs.
You create the Page designs, I hesitate to call them masters, by laying out a sample page and with an object selected on that page:
+Menu > Format > Advanced > Capture Pages… > Name the Page+
Despite the confusing plural in +Capture Pages…+ it only captures the one page with all other options greyed out.
Worse still it does not seem to retain any of the facing page information except for the header and footer, plunking down the page irregardless of whether it is left or right or part of a pair even though it lets you click +Facing Pages+ in the Inspector.
It is hard for me to imagine how they could have created a more muddled, confusing and incomplete arrangement for tasks that were well established on the Mac back in the early 80's when Apple started the DTP revolution 25 years ago.
I am repeating myself but it seems like a product designed by a committee that never uses it.
Peter

Search for master page usage; better way to use master pages?

Hi all,
I am using Frame 9. I have my files set to always have an even number of pages. For chapters where the text ends on a right-hand page, I assign a custom master page to the final left-hand page -- this custom master page has our logo on it. However, because my files have a lot of conditional text (3 different versions of the publication get generated from the same source files), the lengths of the chapters often change when switching between different conditional versions. So for example, for version 1, I assign the custom master page to the last page of the chapter, which is page 28. Then when I switch my conditional text settings to show version 2, the chapter is now 36 pages long, but my custom master page is still applied to page 28. I have to remove it from page 28 and reassign it to page 38. Here are my questions:
1) Is there a way to search for pages that have a specific master page applied? I hoped that I could generate a list of master page usage using the Special > List Of > References option, but apparently not.
2) Is there any way to get Frame to automatically assign my custom master page when it is appropriate, rather than doing it by hand for each conditional version of each chapter?
Thanks!

kelly.usa wrote:
Hi all,
I am using Frame 9. I have my files set to always have an even number of pages. For chapters where the text ends on a right-hand page, I assign a custom master page to the final left-hand page -- this custom master page has our logo on it. However, because my files have a lot of conditional text (3 different versions of the publication get generated from the same source files), the lengths of the chapters often change when switching between different conditional versions. So for example, for version 1, I assign the custom master page to the last page of the chapter, which is page 28. Then when I switch my conditional text settings to show version 2, the chapter is now 36 pages long, but my custom master page is still applied to page 28. I have to remove it from page 28 and reassign it to page 38. Here are my questions:
1) Is there a way to search for pages that have a specific master page applied? I hoped that I could generate a list of master page usage using the Special > List Of > References option, but apparently not.
2) Is there any way to get Frame to automatically assign my custom master page when it is appropriate, rather than doing it by hand for each conditional version of each chapter?
Thanks!
To identify master pages that control pages in body page view, create an identifier on each master page, as you'd create a watermark with text in a background text frame. Control its visibility with either a condition, or by assigning it a color that's invisible in a color view.
HTH
Regards,
Peter
Peter Gold
KnowHow ProServices

Edit Page options in ribbon disabled after applying modified Seattle Master Page

Hi,
I'm working on a modified version of the Seattle.master page, and I have an odd permissions issue that is seen when my user (a farm admin) tries to edit a page on the site. On some pages, clicking Edit Page doesn't do anything at all. On others, I've been
able to go into edit mode but not do anything with the Edit options afterward. In this scenario, most or all of the useful edit options are disabled, and I cannot use Save, Checkout, Discard the Checkout, Change the Page Layout, etc...
Checking the JavaScript console in IE reveals this JS error that I don't see in the OOTB Seattle:
SCRIPT5007: Unable to set value of the property 'href': object is null or undefined
[our.site.com], line 1128 character 590
Here's the function being referenced:
function _cUpdconetidProjectPropertyTitleGraphic(data, ctrl){ ctrl.href = slNavUrl; }
Other possibly helpful information:
Here is a snippet from the modified Seattle Master Page of where the ribbon code sits:
<div id="s4-workspace" class="ms-core-overlay">
<div id="s4-bodyContainer">
<SharePoint:SPSecurityTrimmedControl runat="server" AuthenticationRestrictions="AnonymousUsersOnly">
<wssucw:Welcome runat="server" EnableViewState="false" />
</SharePoint:SPSecurityTrimmedControl>
<div id="ms-designer-ribbon">
<PublishingRibbon:PublishingRibbon runat="server"/>
</div>
As you can see, I have moved the Ribbon (div#ms-designer-ribbon) from its fixed position outside of the div#s4-workspace to inside of the div#s4-bodyContainer so that it scrolls with the page. Placing the ribbon inside div#s4-bodyContainer shouldn't be an issue,
as I've made a Design Manager Master Page in the past and placed the ribbon there as well without issue.
Does anyone know how I can get this modified Seattle master page to allow editing?

Hi,
Is there any custom JavaScript in it, sometimes error may occur due to some typo.
Suppose that we can do the customization like this: With a copied master page, we can apply a part of the change first, then check it in the browser to make sure it can work without affecting the OOTB features. Then apply other parts one by one with immediate
examinations...
By doing this, it would be easier to find out which step in your whole customization would cause the issue.
Best regards
Patrick Liang
TechNet Community Support

Master page irregularities between versions?

Similar Messages

Maybe you are looking for