Keep master page stories from clear style overrides...

Hi everyone,
I am finding the stories in the document and applying clear style overrides through javascript. When i am doing this my master page story items are also get affected. Is there any option or way to skip those master page stories?
Please suggest and help me out.
Thanks in advance
Thiyagu

Hi Thiyagu,
you are asking for the structure of the DOM (document object model).
There are several charts of the hierarchical structure of the DOM, e.g. in tree view.
You may search for them with Google.
To find out, who's the parent of an object, you can check the name of the constructor of it's parent:
myObject.parent.constructor.name
You can also climb up the parents within a loop.
To catch the constructor of a selected object and it's parents, grandparents ... up to the 'primal father' APPLICATION in a loop you may try this short and simple code:
var myData = new Array;
if (app.selection.length > 0)
     var myObject = app.selection[0];
     myData.push(myObject.constructor.name);
     do
          myObject = myObject.parent;
          myData.push(myObject.constructor.name)
     } while (myObject.constructor.name != 'Application')
     alert('Genealogy\r' + myData.join('\r'));
But there are also parents like parentTextFrame or parentStory.
This special parents your would not find out with the simple code above.
To read more about this basic things about the structure of the document object model (and other basics) I want to recommend Peter Kahrel's Scripting InDesign CS3/4 with JavaScript to you.
Martin

Similar Messages

  • How do I keep the page format from changing on my IPAD as I switch between pages

    How do I keep my page format from changing on my IPAD as I switch from page to page.

    Can you provide more information. Switching from page to page in what app? How if the format changing?

  • Tying a Master Page to a Paragraph Style

    As a relative newbie to InDesign (and indeed book layout) I'm really chuffed that my first attempt looks pretty good now I have the first proof in my hands. Have had a few small tweaks to sort out and one thing that I have found cumbersome is that I have 3 master pages - the A-master for almost all the book with running headers and page numbers, the B-master for the first page in each chapter which has no running header and has some page decoration and the C-master for the special pages in the front matter that don't have page numbers and running headers. As we've gone through and made some adjustments the pages have shifted slightly and of course I've found that the B-masters get out of sync because the content shuffles but the master page allocation doesn't get tied to the page with teh Chapter Heading style on it. Is there an easy (or even not so easy) way to tie these together to avoid having to resync, double and triple check them?
    M

    mark_hayhurst wrote:
    As a relative newbie to InDesign (and indeed book layout) I'm really chuffed that my first attempt looks pretty good now I have the first proof in my hands. Have had a few small tweaks to sort out and one thing that I have found cumbersome is that I have 3 master pages - the A-master for almost all the book with running headers and page numbers, the B-master for the first page in each chapter which has no running header and has some page decoration and the C-master for the special pages in the front matter that don't have page numbers and running headers. As we've gone through and made some adjustments the pages have shifted slightly and of course I've found that the B-masters get out of sync because the content shuffles but the master page allocation doesn't get tied to the page with teh Chapter Heading style on it. Is there an easy (or even not so easy) way to tie these together to avoid having to resync, double and triple check them?
    M
    I don't know if there's an existing script for this; others on the forum may know.
    However, Autoflow Pro, a commercial InDesign plug-in from in-tools.com can do this. There's a free trial.
    HTH
    Regards,
    Peter
    Peter Gold
    KnowHow ProServices

  • Some elements on the master page move from page to page. What did I do wrong?

    I can't figure out how to solve my problem.
    The location of the logo and menu (which are on my master page) is correct on the homepage: http://psychocegep.com/
    However, the those elements move when I go on another page. It is even more annoying on this page : http://psychocegep.com/matiere.html
    In fact, the whole page goes down and it creates a blank space at the very top.
    The problem does not occur on my iMac computer, but is present on every other computer.
    What should I do to keep the logo and the menu static?

    Hello,
    Could you please check if it happens when you preview the site in a web browser via Adobe Muse?
    Do you have Menu added on a Master page or on the page itself?
    Please check if some of the element on the page (http://psychocegep.com/matiere.html) has been marked as footer which might be creating issues.
    Regards,
    Sachin

  • When using Internet Explorer and Adobe Reader xi, I cannot find how to keep the Page thumbnails from hiding. We want them open.  Please help!

    In Internet Explorer, when opening a PDF using the IE addon Adobe Reader XI, the Page Thumbnail toolbar is shrunk to the left (hidden).  Our users access the thumbnails constantly and we need this to remain open by default but I cannot find anywhere that this option is set.  I would expect there to be a pin icon to click to keep it open.  In the stand alone product Adobe Reader, we found that you can click "Restore last view settings when reopening documents." in Documents prefs but this doesn't work for new documents (only previously opened docs) AND doesn't work in Internet Explorer at all.
    Any help would be greatly appreciated!
    Marc

    That would be something you could set at document level in document properties but would require Acrobat to make permanent.

  • Editable text box on each page, but generated from Master Page?

    I want to create a blank text box that lives on the Master Page so that it shows up on each page in the document, but I then would enter custom text into the field on each page ( or just leave it blank).
    I know, I know, I can do simply copy a text box from one page, and paste in place on all subsequent pages... or set it up once on a page, then just keep duplicating that page... or some other work around. But simple as those work arounds are, I'd just like a blank text box show up automatically on each page as a master page item, then I can enter text as a see fit and not have to do any duplicating tricks. I've looked up a few tutorials, but none solve for my need.
    So I guess the real question is, does InDesign allow the content of a master page text field to be individually edited on the pages of the document itself?

    It's bet to NEVER use the override master page items command since it overrides ALL master items. That's like using a wrecking ball as a flyswatter. And you don't need to put random text in the frame either (especially since you said you don't want to use it on some pages, though it might be best for those if you create another master without the frame). To override any master object hold Cmd (Mac) or Ctrl (Windows) + Shift and click on it with the selection tool.

  • How to use Ajax Web method in v4.master page to pass value to server side from JavaScript?

    Hi,
    I am customizing my v4.master page. Just adding jquery "Multiselect" dropdown .
    I want to pass selected value to code behind to perform some database activities.
    Here no code behind for me. Just i have added "Server side script" as a code behind.
    How to pass the value?
    Anyone give me the idea on it.
    Thanks & Regards
    Poomani Sankaran

    try using asp.net variables as per below links:
    http://sharepoint.stackexchange.com/questions/88777/how-to-use-a-variable-in-the-masterpage
    http://sharepoint.stackexchange.com/questions/80074/how-can-i-use-the-current-language-as-a-variable-in-my-masterpage
    https://msdn.microsoft.com/en-us/library/ms476046%28v=office.12%29.aspx
    http://www.dotnetfunda.com/articles/show/1507/how-to-access-master-page-variableproperty-from-the-content-page
    Please mark answer as correct if it is correct else vote for it if you find it useful Happy SharePointing

  • Custom Master Page Issue in Intranet

    Hi All,
    I hope someone can assist with this, we implemented this particular SharePoint 2007 portal approximately 5 years ago.  An outside consultant created this custom master page, for some reason out of nowhere we are experiencing this bizarre issue with
    the master page and checking in and out documents. I have attached an image showing the error message being displayed below(couldn't attach until my account was verified but it states 'Error invalid viewstate, port 52208, user agent Mozilla/4.0..., viewstate,
    referrer, path).  I came across one source on the web that stated something about the search box code and it causing issues out of nowhere on the master page.  So in my dev environment I made the change and removed the following code from the master
    page below.
    <td style="padding-top:8px;" valign=top>
                <asp:ContentPlaceHolder id="PlaceHolderSearchArea" runat="server">
                <SharePoint:DelegateControl runat="server" ControlId="SmallSearchInputBox"/>
                </asp:ContentPlaceHolder>
    </td>
    As soon as this code is removed and the page is published again everything begins to work again, the problem is I can't remove search from this intranet portal as it is heavily used.  Any assistance would be greatly appreciated.

    By any chance, do you still have access to the solution package in which the master page was contained? Normally, you would see another .ascx user control overriding the delegate search control in there. I'm almost positive that this custom control is
    what causing this issue.
    Nikolas Charlebois-Laprade Microsoft Certified Professional & Software Engineer http://nikcharlebois.com

  • Having issues with custom master pages and device channels

    I'm working in Sharepoint 2013 and am attempting to create a custom master page that is to be used by mobile devices. I have created an html file and a custom css file that includes snippets from the design manager. The file appears to preview fine in a
    browser from Microsoft Web Expression. I have loaded the html file into sharepoint via design manager, so the master file is there as well. The css files are in the style library for the site collection and I have created a device channel including user agent
    strings for iphones going back to the iPhone 4 and operating systems going back to iOS 6. I have obviously assigned my custom "mobile" master for that device channel and I have turned off mobile browsing. However when I open the site on my phone
    it shows the normal full desktop view and not my custom master. I will include my html code, my css and a screenshot of my device channel below. Please help!
    <?xml version="1.0" encoding="utf-8"?><!--SPG:
    This HTML file has been associated with a SharePoint Master Page (.master file) carrying the same name. While the files remain associated, you will not be allowed to edit the .master file, and any rename, move, or deletion operations will be reciprocated.
    To build the master page directly from this HTML file, simply edit the page as you normally would. Use the Snippet Generator at https://otterbein.sharepoint.com/sites/Committees/_layouts/15/ComponentHome.aspx?Url=https%3A%2F%2Fotterbein%2Esharepoint%2Ecom%2Fsites%2FCommittees%2F%5Fcatalogs%2Fmasterpage%2Fmobile%5Ftest%5Fmaster%2Emaster to create and customize useful SharePoint entities, then copy and paste them as HTML snippets into your HTML code. All updates to this file will automatically sync to the associated Master Page.
    -->
    <!-- _lcid="1033" _version="16.0.3611" _dal="1" -->
    <!-- _LocalBinding -->
    <!DOCTYPE html[]>
    <html xmlns:mso="urn:schemas-microsoft-com:office:office" xmlns:msdt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882">
    <head>
    <link href="https://otterbein.sharepoint.com/sites/Committees/Style Library/mobile_corev15.css" rel="stylesheet" type="text/css" />
    <meta http-equiv="X-UA-Compatible" content="IE=10" />
    <!--CS: Start Head Snippet-->
    <!--SPM:<%@Register Tagprefix="SharePoint" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"%>-->
    <!--SPM:<%@Register Tagprefix="WebPartPages" Namespace="Microsoft.SharePoint.WebPartPages" Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"%>-->
    <!--SID:00 -->
    <meta name="GENERATOR" content="Microsoft SharePoint" />
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <meta http-equiv="Expires" content="0" />
    <!--SPM:<SharePoint:RobotsMetaTag runat="server"/>-->
    <!--MS:<SharePoint:PageTitle runat="server">-->
    <!--SPM:<asp:ContentPlaceHolder id="PlaceHolderPageTitle" runat="server">-->
    <!--SPM:<SharePoint:ProjectProperty Property="Title" runat="server"/>-->
    <!--SPM:</asp:ContentPlaceHolder>-->
    <!--ME:</SharePoint:PageTitle>-->
    <!--SPM:<SharePoint:StartScript runat="server"/>-->
    <!--MS:<SharePoint:CssLink runat="server" Version="15">-->
    <!--PS: Start Preview-->
    <link href="https://otterbein.sharepoint.com/sites/Committees/Style Library/mobile_corev15.css" rel="stylesheet" type="text/css" /><!--PE: End Preview-->
    <!--ME:</SharePoint:CssLink>-->
    <!--SPM:<SharePoint:CacheManifestLink runat="server"/>-->
    <!--SPM:<SharePoint:PageRenderMode runat="server" RenderModeType="Standard"/>-->
    <!--SPM:<SharePoint:ScriptLink language="javascript" name="core.js" OnDemand="true" runat="server" Localizable="false"/>-->
    <!--SPM:<SharePoint:ScriptLink language="javascript" name="menu.js" OnDemand="true" runat="server" Localizable="false"/>-->
    <!--SPM:<SharePoint:ScriptLink language="javascript" name="callout.js" OnDemand="true" runat="server" Localizable="false"/>-->
    <!--SPM:<SharePoint:ScriptLink language="javascript" name="sharing.js" OnDemand="true" runat="server" Localizable="false"/>-->
    <!--SPM:<SharePoint:ScriptLink language="javascript" name="suitelinks.js" OnDemand="true" runat="server" Localizable="false"/>-->
    <!--SPM:<SharePoint:CustomJSUrl runat="server"/>-->
    <!--MS:<SharePoint:SoapDiscoveryLink runat="server">-->
    <!--PS: Start Preview--><link href="https://otterbein.sharepoint.com/_vti_bin/spsdisco.aspx" rel="alternate" type="text/xml" /><!--PE: End Preview-->
    <!--ME:</SharePoint:SoapDiscoveryLink>-->
    <!--MS:<SharePoint:AjaxDelta id="DeltaPlaceHolderAdditionalPageHead" Container="false" runat="server">-->
    <!--MS:<asp:ContentPlaceHolder id="PlaceHolderAdditionalPageHead" runat="server">-->
    <!--ME:</asp:ContentPlaceHolder>-->
    <!--MS:<SharePoint:DelegateControl runat="server" ControlId="AdditionalPageHead" AllowMultipleControls="true">-->
    <!--ME:</SharePoint:DelegateControl>-->
    <!--MS:<asp:ContentPlaceHolder id="PlaceHolderBodyAreaClass" runat="server">-->
    <!--ME:</asp:ContentPlaceHolder>-->
    <!--ME:</SharePoint:AjaxDelta>-->
    <!--SPM:<SharePoint:CssRegistration Name="Themable/corev15.css" runat="server"/>-->
    <!--SPM:<SharePoint:AjaxDelta id="DeltaSPWebPartManager" runat="server">-->
    <!--SPM:<WebPartPages:SPWebPartManager runat="server"/>-->
    <!--SPM:</SharePoint:AjaxDelta>-->
    <!--CE: End Head Snippet-->
    <!--[if gte mso 9]><xml>
    <mso:CustomDocumentProperties>
    <mso:ContentType msdt:dt="string">Design File</mso:ContentType>
    <mso:ContentTypeId msdt:dt="string">0x0101000F1C8B9E0EB4BE489F09807B2C53288F0054AD6EF48B9F7B45A142F8173F171BD10003D357F861E29844953D5CAA1D4D8A3A</mso:ContentTypeId>
    <mso:HtmlDesignAssociated msdt:dt="string">1</mso:HtmlDesignAssociated>
    <mso:HtmlDesignFromMaster msdt:dt="string"></mso:HtmlDesignFromMaster>
    <mso:HtmlDesignConversionSucceeded msdt:dt="string">True</mso:HtmlDesignConversionSucceeded>
    <mso:HtmlDesignStatusAndPreview msdt:dt="string">https://otterbein.sharepoint.com/sites/Committees/_catalogs/masterpage/mobile_test_master.html, Conversion successful.</mso:HtmlDesignStatusAndPreview>
    </mso:CustomDocumentProperties>
    </xml><![endif]-->
    <link href="https://otterbein.sharepoint.com/sites/Committees/Style Library/mobile_corev15.css" rel="stylesheet" type="text/css" />
    </head>
    <body style="width: 330; margin-right: 0px">
    <div id="ms-designer-ribbon" style="width:312px">
    <!--SPM:<%@Register Tagprefix="SharePoint" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"%>-->
    <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;">
    <!--MS:<SharePoint:EncodedLiteral runat="server" text="&#60;%$Resources:wss,master_turnonaccessibility%&#62;" EncodeMethod="HtmlEncode">-->
    <!--ME:</SharePoint:EncodedLiteral>-->
    </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;">
    <!--MS:<SharePoint:EncodedLiteral runat="server" text="&#60;%$Resources:wss,master_turnoffaccessibility%&#62;" EncodeMethod="HtmlEncode">-->
    <!--ME:</SharePoint:EncodedLiteral>-->
    </a>
    </div>
    <!--SID:02 {Ribbon Snippet}-->
    <!--PS: Start Preview--><!--PE: End Preview-->
    </div>
    <!--MS:<SharePoint:SPSecurityTrimmedControl runat="server" AuthenticationRestrictions="AnonymousUsersOnly">-->
    <!--SPM:<wssucw:Welcome runat="server" EnableViewState="false"/>-->
    <!--ME:</SharePoint:SPSecurityTrimmedControl>-->
    <div id="s4-workspace" style="left: 0px; top: 0px; width: 329">
    <div id="s4-bodyContainer" style="width: 328">
    <table style="width: 312px">
    <tr>
    <td style="width: 312px; background: #666666; text-align:center">
    <div class="js-callout-menuAction" style="background:rgb(102, 102, 102); color:white; width:295px; padding:8px; height:64px; overflow:hidden;">In true previews of your site, the SharePoint ribbon will be here.</div></td>
    </tr>
    <tr>
    <td style="width: 312px; background: #CB1920; text-align:center">
    <img alt="Otterbein Logo" src="https://otterbein.sharepoint.com/sites/Committees/Style%20Library/otterbein-logo_towers_white_mobile.png" style="padding:5px"><br>
    <div data-name="SiteTitle" style="width: 295px; color:white; padding-bottom:5px; text-indent:5px" class="ms-chkmark-container-centerer"><!--CS: Start Site Title Snippet--><!--SPM:<%@Register Tagprefix="SharePoint" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=16.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"%>--><!--MS:<SharePoint:AjaxDelta runat="server" ForeColor="White">--><!--PS: Start of READ-ONLY PREVIEW (do not modify)--><!--PE: End of READ-ONLY PREVIEW--><!--MS:<SharePoint:SPLinkButton runat="server" ForeColor="White" NavigateUrl="~site/">--><!--PS: Start of READ-ONLY PREVIEW (do not modify)--><!--PE: End of READ-ONLY PREVIEW--><!--MS:<SharePoint:ProjectProperty runat="server" Property="Title">--><!--PS: Start of READ-ONLY PREVIEW (do not modify)-->
    <span style="font-size:xx-large">Committees<!--PE: End of READ-ONLY PREVIEW--><!--ME:</SharePoint:ProjectProperty>--><!--PS: Start of READ-ONLY PREVIEW (do not modify)--><!--PE: End of READ-ONLY PREVIEW--><!--ME:</SharePoint:SPLinkButton>--><!--PS: Start of READ-ONLY PREVIEW (do not modify)--><!--PE: End of READ-ONLY PREVIEW--><!--ME:</SharePoint:AjaxDelta>--><!--CE: End Site Title Snippet--></span>
    </div>
    <div WebPartID="00000000-0000-0000-0000-000000000000" HasPers="true" id="WebPart" width="250px" class="ms-WPBody noindex " OnlyForMePart="true" allowDelete="false" style="padding-top:15px; padding-bottom:15px"><div componentid="ctl00_ctl03_csr" id="ctl00_ctl03_csr"><div id="SearchBox" name="Control"><div class="ms-srch-sb ms-srch-sb-border" id="ctl00_ctl03_csr_sboxdiv">
    <input type="text" value="Search..." maxlength="2048" accessKey="S" title="Search..." id="ctl00_ctl03_csr_sbox" autocomplete="off" autocorrect="off" onkeypress="EnsureScriptFunc('Search.ClientControls.js', 'Srch.U', function() {if (Srch.U.isEnterKey(String.fromCharCode(event.keyCode))) {$find('ctl00_ctl03_csr').search($get('ctl00_ctl03_csr_sbox').value);return Srch.U.cancelEvent(event);}})" onkeydown="EnsureScriptFunc('Search.ClientControls.js', 'Srch.U', function() {var ctl = $find('ctl00_ctl03_csr');ctl.activateDefaultQuerySuggestionBehavior();})" onfocus="EnsureScriptFunc('Search.ClientControls.js', 'Srch.U', function() {var ctl = $find('ctl00_ctl03_csr');ctl.hidePrompt();ctl.setBorder(true);})" onblur="EnsureScriptFunc('Search.ClientControls.js', 'Srch.U', function() {var ctl = $find('ctl00_ctl03_csr'); if (ctl){ ctl.showPrompt(); ctl.setBorder(false);}})" class="ms-textSmall ms-srch-sb-prompt ms-helperText" style="width: 250px; height: 18px" /><a title="Search" class="ms-srch-sb-searchLink" id="ctl00_ctl03_csr_SearchLink" onclick="EnsureScriptFunc('Search.ClientControls.js', 'Srch.U', function() {$find('ctl00_ctl03_csr').search($get('ctl00_ctl03_csr_sbox').value);})" href="javascript: {}"><img src="/sites/Committees/_catalogs/theme/Themed/EF0ED6F1/searchresultui-61174269.themedpng?ctag=55" class="ms-srch-sb-searchImg" id="searchImg" alt="Search" /></a></div></div></div><noscript><div id="ctl00_ctl03_noscript">It looks like your browser does not have JavaScript enabled. Please turn on JavaScript and try again.</div></noscript><div id="ctl00_ctl03" style="color:White;border-color:White;border-width:0px;border-style:Solid;text-align:center;"></div><div class="ms-clear"></div></div>
    <div data-name="TopNavigationNoFlyoutWithStartNode"><!--CS: Start Top Navigation Snippet--><!--SPM:<%@Register Tagprefix="SharePoint" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=16.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"%>--><!--MS:<SharePoint:AjaxDelta runat="server" CssClass="ms-displayInline ms-core-navigation ms-dialogHidden" Width="312px" BlockElement="True" ID="DeltaTopNavigation">--><!--PS: Start of READ-ONLY PREVIEW (do not modify)--><!--PE: End of READ-ONLY PREVIEW--><!--MS:<SharePoint:DelegateControl runat="server" Id="topNavigationDelegate" ControlId="TopNavigationDataSource">--><!--PS: Start of READ-ONLY PREVIEW (do not modify)--><span style="display:none">
    <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">PortalSiteMapDataSource</span> - topSiteMap</td>
    </tr>
    <tr>
    <td></td>
    </tr>
    </table>
    </span><!--PE: End of READ-ONLY PREVIEW--><!--MS:<Template_Controls>--><!--MS:<asp:SiteMapDataSource ShowStartingNode="True" SiteMapProvider="SPNavigationProvider" ID="topSiteMap" runat="server" StartingNodeUrl="sid:1002">--><!--ME:</asp:SiteMapDataSource>--><!--ME:</Template_Controls>--><!--ME:</SharePoint:DelegateControl>--><a name="startNavigation"></a><!--MS:<asp:ContentPlaceHolder ID="PlaceHolderTopNavBar" runat="server">--><!--MS:<SharePoint:AspMenu runat="server" UseSeparateCss="false" AdjustForShowStartingNode="False" StaticDisplayLevels="2" AccessKey="1" SkipLinkText="" ItemWrap="True" EnableViewState="False" MaximumDynamicDisplayLevels="0" UseSimpleRendering="True" DataSourceID="topSiteMap" Orientation="Vertical" ID="TopNavigationMenu">--><!--PS: Start of READ-ONLY PREVIEW (do not modify)-->
    <div id="zz7_TopNavigationMenu" class=" noindex ms-core-listMenu-verticalBox">
    <ul id="zz9_RootAspMenu" class="root ms-core-listMenu-root static">
    <li class="static">
    <a class="static menu-item ms-core-listMenu-item ms-displayInline ms-navedit-linkNode" href="/sites/Committees/SitePages/Home.aspx" accesskey="1">
    <span class="additional-background ms-navedit-flyoutArrow">
    <span class="menu-item-text">Committees</span></span></a></li>
    <li class="static ms-verticalAlignTop ms-listMenu-editLink ms-navedit-editArea">
    <span class="ms-navedit-editSpan" id="zz7_TopNavigationMenu_NavMenu_Edit">
    <a id="zz7_TopNavigationMenu_NavMenu_EditLinks" class="ms-navedit-editLinksText" href="#" onclick="g_QuickLaunchMenu = null; EnsureScriptParams('quicklaunch.js', 'QuickLaunchInitEditMode', 'zz7_TopNavigationMenu', 1, 0, 1, '\u002fSITES\u002fCOMMITTEES'); cancelDefault(event); return false;" title="Edit Links">
    <span class="ms-displayInlineBlock">
    <span class="ms-navedit-editLinksIconWrapper ms-verticalAlignMiddle">
    <img class="ms-navedit-editLinksIcon" src="/sites/Committees/_catalogs/theme/Themed/EF0ED6F1/spcommon-B35BB0A9.themedpng?ctag=55" alt="Edit Links" /></span><span class="ms-metadata ms-verticalAlignMiddle">Edit Links</span></span></a><span id="zz7_TopNavigationMenu_NavMenu_Loading" class="ms-navedit-menuLoading ms-hide"><a id="zz7_TopNavigationMenu_NavMenu_GearsLink" href="#" onclick="HideGears(); return false;" title="This animation indicates the operation is in progress. Click to remove this animated image."><img id="zz7_TopNavigationMenu_NavMenu_GearsImage" src="/_layouts/15/images/loadingcirclests16.gif?rev=38" alt="This animation indicates the operation is in progress. Click to remove this animated image." /></a></span><div id="zz7_TopNavigationMenu_NavMenu_ErrorMsg" class="ms-navedit-errorMsg">
    </div>
    </span></li>
    </ul>
    </div>
    <!--PE: End of READ-ONLY PREVIEW--><!--ME:</SharePoint:AspMenu>--><!--ME:</asp:ContentPlaceHolder>--><!--PS: Start of READ-ONLY PREVIEW (do not modify)--><!--PE: End of READ-ONLY PREVIEW--><!--ME:</SharePoint:AjaxDelta>--><!--CE: End Top Navigation Snippet-->
    </div>
    <br>
    </td>
    </tr>
    <tr>
    <td style="width: 312px">
    <div class="DefaultContentBlock" style="border:medium black solid; background:yellow; color:black;">
    This area will be filled in by content you create in your page layouts.
    </div>
    </td>
    </tr>
    <tr>
    <td style="width: 312px; background:#CCCCCC"><!--CS: Start Content Editor Snippet--><!--SPM:<%@Register Tagprefix="WebPartPages" Namespace="Microsoft.SharePoint.WebPartPages" Assembly="Microsoft.SharePoint, Version=16.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"%>--><!--MS:<WebPartPages:ContentEditorWebPart xmlns:WebPartPages="namespace" runat="server" webpart="true">--><!--PS: Start of READ-ONLY PREVIEW (do not modify)--><div class="ms-webpart-chrome ms-webpart-chrome-fullWidth "><div WebPartID="00000000-0000-0000-0000-000000000000" HasPers="true" id="WebPart" width="312px" class="ms-WPBody noindex " OnlyForMePart="true" allowDelete="false" style=""><div class="ms-rtestate-field"></div></div></div><!--PE: End of READ-ONLY PREVIEW--><!--MS:<WebPart xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/WebPart/v2">--><!--MS:<Title>--><!--SPM:$Resources:core,ContentEditorWebPartTitle;--><!--ME:</Title>--><!--MS:<FrameType>--><!--SPM:None--><!--ME:</FrameType>--><!--MS:<Description>--><!--SPM:$Resources:core,ContentEditorWebPartDescription;--><!--ME:</Description>--><!--MS:<IsIncluded>--><!--SPM:true--><!--ME:</IsIncluded>--><!--MS:<ZoneID>--><!--SPM:ImportedPartZone--><!--ME:</ZoneID>--><!--MS:<PartOrder>--><!--SPM:0--><!--ME:</PartOrder>--><!--MS:<FrameState>--><!--SPM:Normal--><!--ME:</FrameState>--><!--MS:<Height>--><!--ME:</Height>--><!--MS:<Width>--><!--ME:</Width>--><!--MS:<AllowRemove>--><!--SPM:true--><!--ME:</AllowRemove>--><!--MS:<AllowZoneChange>--><!--SPM:true--><!--ME:</AllowZoneChange>--><!--MS:<AllowMinimize>--><!--SPM:true--><!--ME:</AllowMinimize>--><!--MS:<AllowConnect>--><!--SPM:true--><!--ME:</AllowConnect>--><!--MS:<AllowEdit>--><!--SPM:true--><!--ME:</AllowEdit>--><!--MS:<AllowHide>--><!--SPM:true--><!--ME:</AllowHide>--><!--MS:<IsVisible>--><!--SPM:true--><!--ME:</IsVisible>--><!--MS:<DetailLink>--><!--ME:</DetailLink>--><!--MS:<HelpLink>--><!--ME:</HelpLink>--><!--MS:<HelpMode>--><!--SPM:Modeless--><!--ME:</HelpMode>--><!--MS:<Dir>--><!--SPM:Default--><!--ME:</Dir>--><!--MS:<PartImageSmall>--><!--ME:</PartImageSmall>--><!--MS:<MissingAssembly>--><!--SPM:Cannot import this Web Part.--><!--ME:</MissingAssembly>--><!--MS:<PartImageLarge>--><!--SPM:/_layouts/15/images/mscontl.gif--><!--ME:</PartImageLarge>--><!--MS:<IsIncludedFilter>--><!--ME:</IsIncludedFilter>--><!--MS:<ExportControlledProperties>--><!--SPM:true--><!--ME:</ExportControlledProperties>--><!--MS:<ConnectionID>--><!--SPM:00000000-0000-0000-0000-000000000000--><!--ME:</ConnectionID>--><!--MS:<ID>--><!--SPM:g_4a85e298_8d8c_4770_9fc1_a5f6d6456ec7--><!--ME:</ID>--><!--MS:<ContentLink xmlns="http://schemas.microsoft.com/WebPart/v2/ContentEditor">--><!--ME:</ContentLink>--><!--MS:<Content xmlns="http://schemas.microsoft.com/WebPart/v2/ContentEditor">--><!--ME:</Content>--><!--MS:<PartStorage xmlns="http://schemas.microsoft.com/WebPart/v2/ContentEditor">--><!--ME:</PartStorage>--><!--MS:<ID>--><!--SPM:g_90f063ab_d6a1_4718_b306_b3ade5119bd1--><!--ME:</ID>--><!--ME:</WebPart>--><!--ME:</WebPartPages:ContentEditorWebPart>--><!--CE: End Content Editor Snippet--></td>
    </tr>
    </table>
    </div>
    </div>
    </body>
    </html>
    User agent strings for mobile Channel
    Apple-iPhone3C1/1001.403
    Apple-iPhone3C3/1001.403
    Apple-iPhone4C1/1001.403
    Apple-iPhone5C1/1001.405
    Apple-iPhone5C2/1001.405
    Apple-iPhone2C1/1001.523

    Hi,
    The issue is likely not your HTML Master Page but your user agent string. Try a user agent string of just "iphone". To test your master page, you could also set the user agent to "MSIE", which should cause this master page to load for
    any version of IE. This will help you debug the master page as well in your normal browser.
    Eric Overfield - PixelMill -
    ericoverfield.com -
    @EricOverfield

  • ID Master Pages vs Powerpoint / Captivate Master Slides

    Hello,
    I'm new to InDesign and I just can't get the way Master Pages are supposed to work.
    I though they were pages like the ones in Powerpoint or Captivate : you put placeholders on the page and format them the way you want, then when you create new pages based on those masters you just fill in the pre-formatted fields.
    This is not the case in InDesign. Everything's locked ! What's the point ?
    It's fine for background pictures, pages numbers and that kind of stuff but why would you put text and image placeholders you just can't edit ?
    Of course, you can override item but you just lose link to the master page.
    A simple example : I made a master page with chapter title on a line (white on a grey background) with automatic numbering and a block of text underneath.
    Now, if I apply this master to a page, I just can't type in text, autonumbering is useless. I have to overide elements but what if I change title background color and decide text should be on two columns ? If I reapply Master on my page, I get modified stuff underneath overidden elements !
    I hope you see what I mean and that you will give me clues to the best approach to InDesign master pages.
    Thanks.
    PJ

    Make the border and column guid lines in page layout.
    Use text frames with 2 columns best practice is to set up them via object styles.
    Set a pragraph style for your text.
    Set another paragraph style for your headline: Make column Span over all with a specified distance after, Paragraph Ruler for the Grey bar, white text
    But don't use Character Styles, except for single words, automatic numbers, all things which are different from the residing pargraph properties.
    Avoid overrides on pages, as these are causing problems in syntax and in editing later. Beter is to use a different master page, where you can use overrides.
    E.g. it makes problems when you have overrides and want to reapply the same master again.
    Or it makes problems when you create PDFs for unlimitted access or when you export EPUBs or HTML.

  • 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&amp;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&amp;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"?><!--SPG:
    This HTML file has been associated with a SharePoint Master Page (.master file) carrying the same name.  While the files remain associated, you will not be allowed to edit the .master file, and any rename, move, or deletion operations will be reciprocated.
    To build the master page directly from this HTML file, simply edit the page as you normally would.  Use the Snippet Generator at http://win-6q11jqp4kh5:1111/sites/firstbank/_layouts/15/ComponentHome.aspx?Url=http%3A%2F%2Fwin%2D6q11jqp4kh5%3A1111%2Fsites%2Ffirstbank%2F%5Fcatalogs%2Fmasterpage%2FFirstBankHtml%2Emaster
    to create and customize useful SharePoint entities, then copy and paste them as HTML snippets into your HTML code.   All updates to this file will automatically sync to the associated Master Page.
    -->
    <!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" />
            <!--CS: Start Page Head Contents Snippet-->
            <!--SPM:<%@Register Tagprefix="SharePoint" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"%>-->
            <!--SPM:<%@Register Tagprefix="WebPartPages" Namespace="Microsoft.SharePoint.WebPartPages" Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"%>-->
            <!--SPM:<%@Register Tagprefix="UC1" TagName="TopMenuControl" Src="~/_controltemplates/15/FirstBankUC/TopMenu.ascx" %>-->
            <!--SPM:<%@Register Tagprefix="UC2" TagName="BottomInterestRates" Src="~/_controltemplates/15/FirstBankUC/InterestRates.ascx" %>-->
            <!--SID:00 -->
            <meta name="GENERATOR" content="Microsoft SharePoint" />
            <meta http-equiv="Content-type" content="text/html; charset=utf-8" />
            <meta http-equiv="Expires" content="0" />
            <!--MS:<SharePoint:RobotsMetaTag runat="server">-->
                <!--PS: Start of READ-ONLY PREVIEW (do not modify)--><!--PE: End of READ-ONLY PREVIEW-->
            <!--ME:</SharePoint:RobotsMetaTag>-->
            <!--MS:<SharePoint:PageTitle runat="server">-->
                <!--PS: Start of READ-ONLY PREVIEW (do not modify)--><!--PE: End of READ-ONLY PREVIEW-->
                <!--MS:<asp:ContentPlaceHolder id="PlaceHolderPageTitle" runat="server">-->
                    <!--MS:<SharePoint:ProjectProperty Property="Title" runat="server">-->
                        <!--PS: Start of READ-ONLY PREVIEW (do not modify)-->firstbank<!--PE: End of READ-ONLY PREVIEW-->
                    <!--ME:</SharePoint:ProjectProperty>-->
                <!--ME:</asp:ContentPlaceHolder>-->
                <!--PS: Start of READ-ONLY PREVIEW (do not modify)--><!--PE: End of READ-ONLY PREVIEW-->
            <!--ME:</SharePoint:PageTitle>-->
            <!--MS:<SharePoint:StartScript runat="server">-->
                <!--PS: Start of READ-ONLY PREVIEW (do not modify)--><!--PE: End of READ-ONLY PREVIEW-->
            <!--ME:</SharePoint:StartScript>-->
            <!--MS:<SharePoint:CssLink runat="server" Version="15">-->
                <!--PS: Start of READ-ONLY PREVIEW (do not modify)--><link rel="stylesheet" type="text/css" href="assets/css/corev15V1.css" /><!--PE: End of READ-ONLY PREVIEW-->
            <!--ME:</SharePoint:CssLink>-->
            <!--MS:<SharePoint:CacheManifestLink runat="server">-->
                <!--PS: Start of READ-ONLY PREVIEW (do not modify)--><!--PE: End of READ-ONLY PREVIEW-->
            <!--ME:</SharePoint:CacheManifestLink>-->
            <!--MS:<SharePoint:PageRenderMode runat="server" RenderModeType="Standard">-->
                <!--PS: Start of READ-ONLY PREVIEW (do not modify)--><!--PE: End of READ-ONLY PREVIEW-->
            <!--ME:</SharePoint:PageRenderMode>-->
            <!--MS:<SharePoint:ScriptLink language="javascript" name="core.js" OnDemand="true" runat="server" Localizable="false">-->
                <!--PS: Start of READ-ONLY PREVIEW (do not modify)--><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><!--PE: End of READ-ONLY PREVIEW-->
            <!--ME:</SharePoint:ScriptLink>-->
            <!--MS:<SharePoint:ScriptLink language="javascript" name="menu.js" OnDemand="true" runat="server" Localizable="false">-->
                <!--PS: Start of READ-ONLY PREVIEW (do not modify)--><!--PE: End of READ-ONLY PREVIEW-->
            <!--ME:</SharePoint:ScriptLink>-->
            <!--MS:<SharePoint:ScriptLink language="javascript" name="callout.js" OnDemand="true" runat="server" Localizable="false">-->
                <!--PS: Start of READ-ONLY PREVIEW (do not modify)--><!--PE: End of READ-ONLY PREVIEW-->
            <!--ME:</SharePoint:ScriptLink>-->
            <!--MS:<SharePoint:ScriptLink language="javascript" name="sharing.js" OnDemand="true" runat="server" Localizable="false">-->
                <!--PS: Start of READ-ONLY PREVIEW (do not modify)--><!--PE: End of READ-ONLY PREVIEW-->
            <!--ME:</SharePoint:ScriptLink>-->
            <!--MS:<SharePoint:ScriptLink language="javascript" name="suitelinks.js" OnDemand="true" runat="server" Localizable="false">-->
                <!--PS: Start of READ-ONLY PREVIEW (do not modify)--><!--PE: End of READ-ONLY PREVIEW-->
            <!--ME:</SharePoint:ScriptLink>-->
            <!--MS:<SharePoint:CustomJSUrl runat="server">-->
                <!--PS: Start of READ-ONLY PREVIEW (do not modify)--><!--PE: End of READ-ONLY PREVIEW-->
            <!--ME:</SharePoint:CustomJSUrl>-->
            <!--MS:<SharePoint:SoapDiscoveryLink runat="server">-->
                <!--PS: Start of READ-ONLY PREVIEW (do not modify)--><link type="text/xml" rel="alternate" href="http://win-6q11jqp4kh5:1111/sites/firstbank/_vti_bin/spsdisco.aspx" /><!--PE:
    End of READ-ONLY PREVIEW-->
            <!--ME:</SharePoint:SoapDiscoveryLink>-->
            <!--MS:<SharePoint:AjaxDelta id="DeltaPlaceHolderAdditionalPageHead" Container="false" runat="server">-->
                <!--PS: Start of READ-ONLY PREVIEW (do not modify)--><!--PE: End of READ-ONLY PREVIEW-->
                <!--MS:<asp:ContentPlaceHolder id="PlaceHolderAdditionalPageHead" runat="server">-->
                <!--ME:</asp:ContentPlaceHolder>-->
                <!--MS:<SharePoint:DelegateControl runat="server" ControlId="AdditionalPageHead" AllowMultipleControls="true">-->
                    <!--PS: Start of READ-ONLY PREVIEW (do not modify)-->
    [ 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" ]<!--PE: End of READ-ONLY PREVIEW-->
                <!--ME:</SharePoint:DelegateControl>-->
                <!--MS:<asp:ContentPlaceHolder id="PlaceHolderBodyAreaClass" runat="server">-->
                <!--ME:</asp:ContentPlaceHolder>-->
                <!--PS: Start of READ-ONLY PREVIEW (do not modify)--><!--PE: End of READ-ONLY PREVIEW-->
            <!--ME:</SharePoint:AjaxDelta>-->
            <!--MS:<SharePoint:CssRegistration Name="assets/css/corev15V1.css" runat="server">-->
                <!--PS: Start of READ-ONLY PREVIEW (do not modify)--><link rel="stylesheet" type="text/css" href="assets/css/corev15V1.css" /><!--PE: End of READ-ONLY PREVIEW-->
            <!--ME:</SharePoint:CssRegistration>-->
            <!--MS:<SharePoint:AjaxDelta id="DeltaSPWebPartManager" runat="server">-->
                <!--PS: Start of READ-ONLY PREVIEW (do not modify)--><!--PE: End of READ-ONLY PREVIEW-->
                <!--MS:<WebPartPages:SPWebPartManager runat="server">-->
                    <!--PS: Start of READ-ONLY PREVIEW (do not modify)--><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><!--PE: End of READ-ONLY PREVIEW-->
                <!--ME:</WebPartPages:SPWebPartManager>-->
                <!--PS: Start of READ-ONLY PREVIEW (do not modify)--><!--PE: End of READ-ONLY PREVIEW-->
            <!--ME:</SharePoint:AjaxDelta>-->
            <!--CE: End Page Head Contents Snippet-->
            <meta charset="utf-8" />
            <!--DC:-->
            <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" />
            <!--[if gte mso 9]><xml>
    <mso:CustomDocumentProperties>
    <mso:DefaultCssFile msdt:dt="string"></mso:DefaultCssFile>
    <mso:PublishingPreviewImage msdt:dt="string"></mso:PublishingPreviewImage>
    <mso:HtmlDesignPreviewUrl msdt:dt="string"></mso:HtmlDesignPreviewUrl>
    <mso:ContentTypeId msdt:dt="string">0x0101000F1C8B9E0EB4BE489F09807B2C53288F0054AD6EF48B9F7B45A142F8173F171BD10003D357F861E29844953D5CAA1D4D8A3A</mso:ContentTypeId>
    <mso:MasterPageDescription msdt:dt="string"></mso:MasterPageDescription>
    <mso:UIVersion msdt:dt="string">;#15;#</mso:UIVersion>
    <mso:PublishingHidden msdt:dt="string">0</mso:PublishingHidden>
    <mso:HtmlDesignAssociated msdt:dt="string">1</mso:HtmlDesignAssociated>
    <mso:HtmlDesignFromMaster msdt:dt="string"></mso:HtmlDesignFromMaster>
    <mso:HtmlDesignStatusAndPreview msdt:dt="string">http://win-6q11jqp4kh5:1111/sites/firstbank/_catalogs/masterpage/FirstBankHtml.html, Conversion successful.</mso:HtmlDesignStatusAndPreview>
    <mso:HtmlDesignConversionSucceeded msdt:dt="string">True</mso:HtmlDesignConversionSucceeded>
    </mso:CustomDocumentProperties>
    </xml><![endif]-->
        </head>
        <body>
            <!--CS: Start Ribbon Snippet-->
            <!--SPM:<%@Register Tagprefix="SharePoint" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"%>-->
            <!--SPM:<%@Register Tagprefix="wssucw" TagName="Welcome" Src="~/_controltemplates/15/Welcome.ascx"%>-->
            <div id="ms-designer-ribbon">
                <!--SID:02 {Ribbon}-->
                <!--PS: Start of READ-ONLY PREVIEW (do not modify) --><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><!--PE: End of READ-ONLY PREVIEW -->
            </div>
            <!--CE: End Ribbon Snippet-->
            <div id="s4-workspace">
                <div id="s4-bodyContainer">
    <div data-name="ContentPlaceHolderMain">
                            <!--CS: Start PlaceHolderMain Snippet-->
                            <!--SPM:<%@Register Tagprefix="SharePoint" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral,
    PublicKeyToken=71e9bce111e9429c"%>-->
                            <!--MS:<SharePoint:AjaxDelta ID="DeltaPlaceHolderMain" IsMainContent="true" runat="server">-->
                                <!--PS: Start of READ-ONLY PREVIEW (do not modify)--><!--PE: End of READ-ONLY PREVIEW-->
                                <!--MS:<asp:ContentPlaceHolder ID="PlaceHolderMain" runat="server">-->
                                <!--ME:</asp:ContentPlaceHolder>-->
                                <!--PS: Start of READ-ONLY PREVIEW (do not modify)--><!--PE: End of READ-ONLY PREVIEW-->
                            <!--ME:</SharePoint:AjaxDelta>-->
                            <!--CE: End PlaceHolderMain Snippet-->
                        </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

  • Auto master page application

    I wrote this script to see if I could hook master pages to a paragraph style and I have a couple of questions.
    1. Currently I'm using the "onIdle" event type is there a better event type that could be used that would still run without interrupting the user?
    I was thinking the "afterAttributeChanged" event type might work better. When is this one called? Is it called for every attribute change in the layout window?
    2. I'm also searching for the pages that I want to change via grep and grabbing the page with paragraphs[i].parentTextFrames[0].parentPage;
    Is this the most efficient way to do this?
    Here's what I have so far:
    #targetengine "session"
    var doc = app.activeDocument;
    var chapterStyleGroup = doc.paragraphStyleGroups.itemByName("Chapter");
    var chapterTitle = chapterStyleGroup.paragraphStyles.itemByName("ChapterTitle");
    var aMaster = doc.masterSpreads.itemByName("A-Master");
    var cMaster = doc.masterSpreads.itemByName("C-Chapter Open");
    var chapterPages = [];
    app.findGrepPreferences = NothingEnum.nothing;
    app.findGrepPreferences.appliedParagraphStyle = chapterTitle;
    var paras = app.findGrep();
    for (var i=0, l=paras.length; i<l; i++) {
              var parentPage = paras[i].parentTextFrames[0].parentPage;
              chapterPages.push(parentPage);
              parentPage.appliedMaster = cMaster;
    var listenerTask = app.idleTasks.add({sleep: 5000});
    listenerTask.addEventListener("onIdle", checkPages);
    function checkPages() {
              var savedPrefs = app.findGrepPreferences.properties;
              app.findGrepPreferences = NothingEnum.nothing;
              app.findGrepPreferences.appliedParagraphStyle = chapterTitle;
              var paras = app.findGrep();
              for (var i=0, l=paras.length; i<l; i++) {
                        var parentPage = paras[i].parentTextFrames[0].parentPage;
                        if (chapterPages[i] !== parentPage) {
                                  chapterPages[i].appliedMaster = aMaster;
                                  parentPage.appliedMaster = cMaster;
                                  chapterPages.splice(i,1,parentPage);
              app.findGrepPreferences.properties = savedPrefs;

    Peter, without threading, the individual text boxes on the master page do number correctly. They are empty text boxes except for an invisible character such as a hard return, and once I have the invisible character in place, the numbers appear.
    Because 1-6 already number and appear correctly, it doesn't make sense to me to thread them together, although I did try it including from caption 6 back to caption 1...this resulted in caption 1 disappearing and all the other captions reducing by increments of one (1-5).
    I'm not sure if I'm 'placing' my list incorrectly (that term doesn't quite make sense to me ~ I thought you define a list and then apply it directly or through a paragraph style?) or what, but do you have any other suggestions?

  • Adding Custom Breadcrumb for SharePoint 2013 Custom Master-Page With A Custom Separator.

    Hi All,
    I have successfully converted an HTML file to a SharePoint 2013 Custom Master-Page with relevant style sheets. But when I used within the SharePoint site I could not find the breadcrumb. So I want to know how to do that? For that breadcrumb I need a custom
    separator like an arrow like in the below.
    As you can see the separator is a custom built one. To have this custom separator in my HTML I have used the following code snippet.
    <div class="breadcrumb-desktop">
    <span class="breadcrumb-links"><a href="#">SharePoint Site Home</a></span>
    <span class="breadcrumb-links"><a href="#">Sub Link 01</a></span> Active Page
    </div>
    The styles are as like in the below.
    .breadcrumb-desktop {
    width: 100%;
    font-family: Arial;
    padding: 23px 0 40px;
    float: left;
    font-size: 0.75em;
    line-height: 1.25;
    .breadcrumb-desktop > span.breadcrumb-links:after {
    content: " \203A ";
    white-space: pre;
    I have tried the following code snippet within the SharePoint site as
    <!--MS:<asp:sitemappath runat="server" sitemapproviders="SPSiteMapProvider,SPXmlContentMapProvider" rendercurrentnodeaslink="false" hideinteriorrootnodes="true">-->
    <!--ME:</asp:sitemappath>-->
    But it did not display as I wanted.
    So how am I supposed to insert these to my Custom Master-Page's breadcrumb and style them? Please could someone help me to solve this?
    Thanks and regards,
    Chiranthaka

    Hi Chiranthaka,
    Please use the following code snippet in your html master page.
    <div class="CustomBreadcrumbs">
    You are here:
    <!--SPM:<SharePoint:AjaxDelta id="DeltaPlaceHolderPageTitleInTitleArea" runat="server">-->
    <!--SPM:<asp:ContentPlaceHolder id="PlaceHolderTitleBreadcrumb" runat="server">-->
    <!--MS:<asp:sitemappath runat="server" sitemapproviders="SPSiteMapProvider,SPXmlContentMapProvider" rendercurrentnodeaslink="false" hideinteriorrootnodes="true">-->
    <!--ME:</asp:sitemappath>-->
    <!--SPM:</asp:ContentPlaceHolder>-->
    <!--SPM:</SharePoint:AjaxDelta>-->
    </div>
    Here is a thread for your reference:
    https://social.msdn.microsoft.com/Forums/office/en-US/daabd903-df98-41da-80d8-6a942d06980e/add-breadcrumb-to-custom-master-page-html-file?forum=sharepointcustomization
    We can also customize a breadcrumb control, then add it in master page.
    http://msreddysharepoint.blogspot.com/2013/01/custom-breadcrumb-navigation-in.html
    Best Regards
    Dennis Guo
    TechNet Community Support

  • How do I create an underlying master page for my master pages (without messing them up)?

    I created a Muse site long ago, and wanted to fix my SEO easily overall by better analytics among other things.
    Perhaps I am doing this the wrong way but I was thinking I could create a master page that I could just drop the html I needed into, and thus not fuss too much with my other pages. The problem is I already have master pages that my site is based on (before you could do this), and it would be much easier to have those master pages stem from one source (a Master master page?).
    Everytime I try to do this it changes my current master and final pages. Anyway I can create and invisible master so this doesn't happen?
    What should I do instead?
    THANK YOU.
    William

    Thanks,
    Your intructions were my plan untill I realized that in doing so, it changed the backgrounds etc of my current masterpages. I realize that this is a lack of planning due to my very rusty design principles, and something I wouldn't have done in my day job if the features had been in place. (so thank you for the new features!) 
    While I realize I could probably fix this by recreating the site with a uniform underlying Primary Master Page feeding into my Secondary Master Pages, I was trying to create a master page that in effect wouldn't change a thing in the other subservient masterpages (thus allowing me freedom to create groups of pages with common analytics or any other types of code).
    Simply when I take your suggestion, things change... can I do this without making things change?
    Not sure if this makes sense. I am trying to avoid coding or a overhaul b/c of time constraints.
    William

  • Can't apply some master pages to topics

    Hello,
    I have already logged a bug report on this, but I am hoping that someone else has encountered it and has a suggested workaround. I have searched the forums, but I didn't see this issue. We recently upgraded to RoboHelp 8, and we have installed 8.0.1.
    Our help projects typically include multiple master pages (formerly called "templates"). Most topics use the main master page, but a few need to use one of our other master pages that is geared toward a different type of user. Most of our projects have at least 3 master pages.
    After conversion from X5 to RoboHelp 8, in some of our help projects, we cannot apply the lesser-used master pages to topics. We can right-click the topic name or within the Design window and open the Topic Properties, and we can select the correct master page, either from the drop-down list or by clicking the Browse button, and we can click Apply. Initially, the topic will show the master page as being selected; however, the header from that master page will not appear grayed out in the Design window for the topic as it should, and when you save and close the topic, the master page is no longer selected for it. This problem does not occur if I select the master page that is used for most topics; that one gets selected and applied correctly.
    This problem has happened to me and to 2 of my coworkers. I got my problem topics and templates to work, but I tried many things repeatedly and cannot pinpoint what made the problem stop happening. I am currently trying to solve the problem in a coworker's project without success.
    Things I have tried:
    1. Deleting and reimporting the master pages that are not working. (When I do this, RoboHelp crashes.)
    2. Comparing the code of the non-working master pages to the code of the master page that does work. I saw no problems.
    3. Deleting the cpd file while the project was closed and then reopening.
    4. Manually changing the tags that appear in the code of the topics to see if I can fool RoboHelp into recognizing the master page. I tried putting in the meta tag and header placeholder tags, but this did not work.
    Has anyone run into this, and if so, have you found a workaround?
    Thank you,
    Tammy

    This was our error, not RoboHelp's. After trying several different things yesterday, I compared the code of a working master page to that of a non-working master page once again. I discovered an error in some JavaScript, and when I removed the extraneous code, the template worked. I apologize for not finding this before posting! I did try several things before I posted.
    Tammy

Maybe you are looking for