Content place holder in master page

I have created one master page and applied it to SP 2013 site and moved the content place holder at center of the page.
My master page is like top bar as a logo and leftside navigation. So, the content place holder is just down of top bar and right of left navigation.
Now i need to hide/remove all default links appearing at content place holder and have to place my required link. like blogs, news feed. some webpart.
Pleae tell the way how can i hide/remove the default links and put my required links.
Thanks in adv !!

Suggest you for create a new layout page for homepage and set the custom masterpage as default one. And do your customization using new-layout page and set as home page.
For reference
http://msdn.microsoft.com/en-us/library/jj191506%28v=office.15%29.aspx
http://blog.navantis.com/create-a-custom-page-layout-in-sharepoint-2013/
-- Vadivelu B Life with SharePoint

Similar Messages

  • How should I tag content created in a master page when addressing accessibility before exporting to Acrobat?  I can't add the content to the articles pannel because it's locked.  I would also like to know how I shold tag my cove content.  I dont' want rea

    How should I tag content created in a master page when addressing accessibility before exporting to Acrobat?  I can't add the content to the articles panel because it's locked.  I would also like to know how I should tag my cove content.  I don't want the reader to get lost in content other than the body of the report, but I also don't want to ignore some content completely by tagging it as artifacts.  What should I do y'all?
    Thanks,
    Josh

    Hi Rob,
    From the screen shots it looks like your script is not formatted properly (you may refer to 'Paladin Script' in 'Sample Project' to get an idea of how the script should be formatted.).
    Further please follow the steps mentioned below to use Story to PP workflow.
    Create a new Film script in Adobe Story
    Create  scene heading – INT. LOCATION – Day (these will show up in the outline view panel on left hand side)
    Hit enter, hit TAB
    Enter the name of the speaker, hit TAB or ENTER
    Copy over the transcribed text
    Build your script this way
    Number scenes from the production menu
    Export ASTX file for your script : File->Export->.astx
    Open Premiere Pro
    Create a new project, bring in media
    In the project pane, find the "Scene" column
    For the clip that contains the spoken text, assign the same scene number to the clip as you have in the story script (lets say both are scene 1)
    Click out of the scene box in the project panel in Ppro
    Right click on the scene that you just assigned a scene number to and select – attach Story script
    Select the .astx fle you exported in step 8
    Click ok
    You should now see the script data in the metadata panel for the clip in the metadata panel.
    You can now run speech to text based on "Embedded Script metadata" to time align spoken word to the script.
    Let us know if this is helpful.
    Thanks
    Rashi - Story Team

  • Paste In Place to Specify Master Page

    Hi,
    Can you make a script for  app.pasteInPlace() into master A in all my opening document?
    I want to paste in place an object to all the opening document's "master A" by script, is that possible?
    John White

    Hi Jarek,
    I am a beginner for script, it’s so hard to write this script by my self,
    I found somewhere has this script which made by Laubender:
    var oldPasteRem = app.clipboardPreferences.pasteRemembersLayers; 
    //uncheck “Paste Remembers Layers” 
    app.clipboardPreferences.pasteRemembersLayers = false; 
    for (i = 0; i < app.activeDocument.layers.length; i++) { 
        //Maybe the user does not want objects pasted to invisible layers:  
        if(app.activeDocument.layers[i].visible == true && app.activeDocument.layers[i].locked == false) { 
            app.activeDocument.activeLayer = app.activeDocument.layers[i]; 
            app.pasteInPlace(); 
    //Restore the old condition: 
    app.clipboardPreferences.pasteRemembersLayers = oldPasteRem;
    so can you help me to change it’s function for paste in place on master page?

  • Per site, list driven footer and other content areas on a SharePoint 2010 master page?

    So I worked with a vendor to provide a js, a powershell script and <div> content holders in a master page that would pull the content dynamically based on the site or subsite, and more specifically from a custom list in that site. To explain, if I
    have a root site collection but want to be able to have the end user control the site content, such as a custom top navigation (above the global) and custom footer, and custom place holder content that would appear under the navigation; I would like to have
    that content pulled from a list.
    My goal is to not have a "custom master page" for the many many sites we have in our environment. I am using twitter bootstrap as the foundation for the master pages, then a set number of page layouts pending whether they want left nav to show
    or not. I also typically just use the v4.master for the system pages, but am not sure if that is a best practice either being that the list display forms for a publishing site are ugly so need customized per list.
    Has any one done anything like this and if so could you point me in the right direction? Any guidance would be greatly appreciated. Right now am working within SP2010 but will be testing for SP2013 in the near future. 

    Hi,
    Based on my understanding, you might want to display dynamic content in the pages which reference a specific master page, the content stores in a custom list, users
    can update the master page by updating the corresponding list items.
    Then there would be two main steps in a solution like this:
    1. Data retrieving of a list: JavaScript Client Object Model can help to query the needed items from a list;
    JavaScript Client Object Model
    http://msdn.microsoft.com/en-us/library/office/hh185006(v=office.14).aspx
    More information about JavaScript Client Object Model:
    How to: Create, Update, and Delete List Items Using JavaScript
    http://msdn.microsoft.com/en-us/library/office/hh185011(v=office.14).aspx 
    2. Modify the master page: With the data retrieved, we can then change the HTML source code of a page using JavaScript.
    About how to
    modify the HTML using JavaScript:
    http://www.w3schools.com/js/js_htmldom_html.asp
    http://njarb.com/2011/06/update-html-content-using-javascript/
    We can apply the custom JavaScript to the master page, then when users open a page which references this master page, the JavaScript will run, get data from the custom
    list, change the HTML source of the current page and display the content you want.
    Best regards,
    Patrick
    Patrick Liang
    TechNet Community Support

  • Custom Master Page with Top Navigation and Left Navigation

    Hi All,
    I have successfully converted an HTML Page to a SharePoint 2013 Master Page. I also created a Custom Page Layout. Using both them I have created my SharePoint Site with 30+ pages. Each page is consisted with the Top Header Navigation as it is inheriting
    from the Master Page I have used. Now I need the left navigation inherit from the master page also. It gives me the advantage of updating it from the master page and affects it through the entire SharePoint Site. 
    But at the moment I am inserting the Left Nav using a web part as an HTMl code snippet individually for each and every page. If needs a modification I have to go through all the pages and do the modification. This is not convenient also. I want to this left
    nav like the SharePoint Current Navigation alternative but within my Page Layout.
    Is there an option to chat within these forums?
    Could someone help me to solve this problem?
    Thanks and regards,
    Chiranthaka

    Hi,
    In your HTML Page Layout, is your "current navigation" in its own content place holder, such as "PlaceHolderLeftNavBar" or did you add the current nav to the "PlaceHolderMain"?
    Can you add CSS that hides the left nav found in each content page so that you do not have to manually remove the left nav? Then you could simply add the current nav back into the Master Page.
    Eric Overfield - PixelMill -
    ericoverfield.com -
    @EricOverfield

  • Adobe InDesign Button Issue (on master page)

    I created previous page and next page buttons along with a table of contents button on the master page of the document.  The same master is applied to all pages in the document.  My issue is when I export to an interactive PDF, my buttons are only showing up on the first 2 pages of the PDF (it is a 10 page document).  Any ideas?  Is this a setting or something I have checked by mistake?
    Thank you!

    I'm having a similar issue--I have Multiple State Objects that contain text. Some have scrollable text and others do not (because there isn't any need--the text fits in the space without scrolling). When I preview them in Adobe Content Viewer, either desktop or device, the text does not show, except the scrollable frames. When I preview in SWF Preview, that text shows. What's wrong?
    Also, when using the "Paste into" command, sometimes my item pastes to the top of the next spread and never pastes where I cut it from. Is there no way to "paste in place" along with the "paste into" command??? It's a reaal pain to align my object exactly where I want it, then cut it, then "paste into" my frame, and then have the damn thing wind up way off screen, and even on the next spread, where to move it back I have to use the direct selection tool rather than the normal selection tool. I repeat, it's a REAL PAIN!!!

  • Outlines in master pages

    Hello everybody, I have found a problem with the ouline function in the indesign server scripting.
    I don't know if this is the correct section or I must use "Indesign scripting"
    Well, I am going to try to explain my problem:
    I have a script to do (between others) the ouline of all the document. My problem appear when I want to do the outline of some content placed and linked in the master.
    For example, the page number is usually place in the master page and is a link added with a "special character".
    The problem is that althought the outline is correctly made, the content of the box is wrong. It is not the page number, but the character 'A' which appears when the special character is added.
    It seems that the problem is that when the system try to do the outline the content of the link is lost.
    One solution would be to take to the front end the box, i.e. quit that box to the master page, but I don't know how can I do that from the script.
    I hope that everything is well explained and someone could help me.
    Regards

    Hi Alice
    My sincere apologies as "life" has gotten a bit in the way of my forum participation. So I offer my apologies in the delay of replying to you.
    In re-thinking this a bit, the question of why you would want a bookmark in a master page to begin with, comes to mind. As bookmarks typically are used to allow linking to a defined spot on the page, my thought is that perhaps you want a "back to top" that could be used? And if so, you are attempting to insert a bookmark named "top" to each of the topics easily?
    If my hunch is correct, you likely are unaware that you even need a bookmark in order to accomplish the goal. If you are trying to provide a link your users may click to reach the top of the page, simply link them to a pound/hash symbol ( # ) and you have accomplished your goal.
    Otherwise, please explain to me what the behavior is you are trying to create so that I might perform some testing to see if it's possible to achieve and how I might explain it.
    Cheers... Rick

  • Everytime I copy pages from one ID CS3 doc to another, it re-applies the master page objects!!

    Please Help,
    This is a topic I would really like to get to the bottom of.
    We have InDesign CS3 templates for creating our reports.
    These templates contain around 10 different master pages with grey placeholder image boxes and text boxes with dummy text.
    When we copy pages from one ID document to another, all the master page objects that were originally assigned to the pages are re-applied!!
    Resulting in lots of grey dummy boxes and text boxes re-appearing on top of the page items!!
    It's so annoying because we always customise the pages once we've pulled down master pages to work on, so when we copy pages across to other documents we have to apply the blank master to be able to kick out all the master objects easily.  Then we need to add the page numbers and footers back onto the blank master page.
    My question is, is there a way to switch this off, so when I move or copy pages from one document to another, nothing happens relating to master page objects, the pages simply just copy across as they are?
    Please help!  If not I may have to ask an external developer to write a script to fix this, it drives 900 of us crazy!
    thanks in advance for any help.
    Or am I just being ridiculous and not actually realising you can switch this off, doh!
    G

    Just a bit of further clarification on this issue (very few people really understand what's going on with master pages and overridden master page items):
    When you override a master page item, the object is moved to a local page, but a connection is maintained with the original master page item. This a) allows for the override to be removed (and return the object to its original state). This also, b) allows for changes made to the original master page item (other than the changes made to the local item from the point that it was overridden) to effect the local item as well.
    When the connection to the master page item cannot be maintained, the local item gets disconnected totally from the master page, and becomes a regular, run-of-the-mill page item.
    In light of this, there's three ways you can end up with duplicate master items:
    Reapplying a master page (or applying a new one). When you reapply a master, all overridden master page items get detached from the master, and the original mster page item appears again in its original state. Most of the time this produces unwanted duplication of objects. To fix up your page, you have two options: a) Delete the master page item, and b) copying the contents of the original to the new master page item. The disadvantage of "a" is that you end up with an item which is totally detached from the master, and changing the item on the master will have no effect on the local item. The disadavantage of "b" is that it's a lot of work...
    Moving a page to a different document. When you move a page to a different document which has the same master as the one originally applied, the master in the new doc is applied, and the effects are identical to reapplying a master page (i.e. overridden objects are detached). If the applied master (i.e. a master with the same name) does not exist in the new doc, the master is transferred over to the new doc along with the page, and the connections to the master page are preserved (well, re-created actually...). The workarounds in case #1 apply here as well.
    When page sides change in a document, the objects on the facing page appears.
    What happens here is a bit confusing, but here's an approximate explanation:
    When you apply a master to a page or spread in InDesign, what you are actually doing is applying an entire spread to an individual page. You can thing of a master spread as an overlay (or more precisely: underlay) on the page with a window cut out to the exact page dimensions.
    When the page side changes that "window cut-out" shifts to show the master spread items which correspond to the position within the spread of your current page (i.e. recto or verso). All objects which exist outside the window shift out of view (but still exist!).
    When an object is overridden, the position of the object is defined by its location on the local page, NOT its position on the master spread. When the page then changes sides, the object remains where it was on the page (even though the object it's connected to on the master spread moves out of the window of view). A corresponding object on the facing page of the master (if it exists) will then show in addition to the overridden one.
    Now remember: contrary to the first two cases, both objects are based on master ones: one visible one and one invisible one.
    Dealing with this third case requires much more care than the first two.
    The obvious way to deal with this would be similar to the first two, but if you remove the local object and transfer the content to the new maste object, the invisible master object on the non-visible page was actually removed, so when the page sides change again, the object will now be connected to the now-invisible master page item, and the correct master page item will be gone!
    The "correct" way to deal with this would be to transfer the content to the new master page item and remove overrides (not delete!) on the local item (which will make it disappear, because it moves back to the invisible page). Of course, when page sides change again, it becomes necessary to repeat the entire process.
    If the local object gets deleted, then your master spread is missing objects with no visible indicator of the fact. This can lead to confusion when the document might be edited at some later point in time.
    I believe that this complicated and un-intuitive behavior of master pages is part of the reason people tend to avoid using master page items. Documents tend to get messed up in really odd ways... It's a real shame, because extensive use of master page items has a lot of potential for streamlining workflows and saving an awful lot of time. This behavior really puts a damper on really using master pages as templates.
    Getting master page items to work the way they "should" was a big part of what I was trying to accomplish with AutoFlow Pro... When the master page items are defined as such (i.e. given a unique name), AutoFlow Pro solves all three of the above issues by keeping overridden master page items connected to the master page items on the currently applied master (and when a new master is applied as well!).
    (When I have a bit of spare time, I think I'll write this up on my blog with some visuals to make this easier to grasp...)
    Harbs

  • 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

  • Deployed Custom Master Page Not Visible in Designer

    My team has created a custom master page and has packaged and deployed it as a feature. The custom master page file correctly appears in the master pages gallery via the Web UI, but it's not showing up in the Master Pages folder when the site is opened
    in Designer. What are we missing?

    Hi,
    when the master page was deployed by a sandbox solution please make sure that the master page is checked in and approved. SharePoint doesn't check in and approve files that was deployed by a sandbox solution. Also make sure that the correct content type
    is assigned. because otherwise you won't see it too.
    To set the content type of the master page on deployment correct you just need to simply add the following inside the <file>
    <Property Name="ContentType" Value="$Resources:cmscore,contenttype_masterpage_name;" />
    If the master page is a farm  you should also add the content type but it will be checked in automatically. I hope you are on root level of your site collection because the master page will not deployed to the sub sites.
    In SharePoint Designer you also have two different approaches to find the master page.
    Approach 1:
    Use the Master Page Entry on the navigation pane left. The Master Page will only show up if content type ins correctly set.
    Approach 2:
    Go to "All Files" -> _catalogs -> masterpage
    By using approach two you will see the same amount of files that you can review in SharePoint. You will also find the article pages in there.
    Hope this helps
    Kind regards
    Stefan
    http://www.n8d.at/blog
    Follow me on Twitter: StFBauer |
    n8design
    Microsoft Community Contributor 2011
    MCTS - SharePoint / WSS Configuration and Development

  • Hide Master Page

    Hi Folks,
    I have a page with fields in design view, which is placed in the content area of the master page.
    Now, i want to hide this page based on a condition. I am following the below steps to hide it.
    I am writing the below code in the design view page (initialization event, form ready event).
    if ( $.HIDEPAGE_FLAG == "X" ) then
    $.presence = "hidden"
    endif
    The fields present in the design view page are hidden, but I am getting a blank page. I am not able to hide this blank page.
    Can you guys tell if i am missing anything here/how do i hide this blank page ?
    Kind Regards,
    Chaitanya

    Hi Chaitanya,
    Instead of hiding the master page, dont trigger it.  Please find below link, which is used for dynamically trigerring master pages using subform property
    Using Subform to trigger Master Pages dynamically
    If you have only one master page and you dont want to trigger it.. while trigerring form from driver program, don't execute it based on the condition and just print a message accordingly.
    Please let me know, if you see any issues in above procedure
    Thanks,
    Rakesh

  • 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

  • Paste in place to next Master unfunction, can you fix it?

    Hi, everyone
    I got this script, which copy from:
    Paste In Place to Specify Master Page
    I change it into:
    var myDialog = app.dialogs.add({name:"Copy Select item to next Master",canCancel:true});
    with(myDialog){
        with(dialogColumns.add()){
        staticTexts.add({staticLabel:"Select a Master you want to copy to"});
            with(dialogRows.add()){
               var mySelection = dropdowns.add({stringList:["Master A", "Master B","Master C", "Master D", "Master E","Master F", "Master G"], selectedIndex:0});
    if (myDialog.show() == true)
    function main(){
      if("Copy to next Master");
          copy_to_next_master(); 
    function copy_to_next_master() { 
        if (mySelection.selectedIndex == 0){
    var nSel = app.selection.length;   
    for ( var i = 1; i < app.documents.length; i++) {   
            var nextDoc = app.documents[i];   
            if (!nSel) { alert( "Nothing selected!" ); exit(); } 
            for ( var n = 0; n < nSel; n++ ) { 
                var curSel = app.selection[n]; 
                curSel.duplicate( nextDoc.masterSpreads[0] ); 
    alert("Done.\rWhat you select are pasted in place to next documents' Master  A");
        if (mySelection.selectedIndex == 1){
    var nSel = app.selection.length;   
    for ( var i = 1; i < app.documents.length; i++) {   
            var nextDoc = app.documents[i];   
            if (!nSel) { alert( "Nothing selected!" ); exit(); } 
            for ( var n = 0; n < nSel; n++ ) { 
                var curSel = app.selection[n]; 
                curSel.duplicate( nextDoc.masterSpreads[1] ); 
    alert("Done.\rWhat you select are pasted in place to next documents' Master  B");
        if (mySelection.selectedIndex == 1){
    var nSel = app.selection.length;   
    for ( var i = 1; i < app.documents.length; i++) {   
            var nextDoc = app.documents[i];   
            if (!nSel) { alert( "Nothing selected!" ); exit(); } 
            for ( var n = 0; n < nSel; n++ ) { 
                var curSel = app.selection[n]; 
                curSel.duplicate( nextDoc.masterSpreads[2] ); 
    alert("Done.\rWhat you select are pasted in place to next documents' Master  C");
        if (mySelection.selectedIndex == 1){
    var nSel = app.selection.length;   
    for ( var i = 1; i < app.documents.length; i++) {   
            var nextDoc = app.documents[i];   
            if (!nSel) { alert( "Nothing selected!" ); exit(); } 
            for ( var n = 0; n < nSel; n++ ) { 
                var curSel = app.selection[n]; 
                curSel.duplicate( nextDoc.masterSpreads[3] ); 
    alert("Done.\rWhat you select are pasted in place to next documents' Master  D");
        if (mySelection.selectedIndex == 1){
    var nSel = app.selection.length;   
    for ( var i = 1; i < app.documents.length; i++) {   
            var nextDoc = app.documents[i];   
            if (!nSel) { alert( "Nothing selected!" ); exit(); } 
            for ( var n = 0; n < nSel; n++ ) { 
                var curSel = app.selection[n]; 
                curSel.duplicate( nextDoc.masterSpreads[4] ); 
    alert("Done.\rWhat you select are pasted in place to next documents' Master  E");
        if (mySelection.selectedIndex == 1){
    var nSel = app.selection.length;   
    for ( var i = 1; i < app.documents.length; i++) {   
            var nextDoc = app.documents[i];   
            if (!nSel) { alert( "Nothing selected!" ); exit(); } 
            for ( var n = 0; n < nSel; n++ ) { 
                var curSel = app.selection[n]; 
                curSel.duplicate( nextDoc.masterSpreads[5] ); 
    alert("Done.\rWhat you select are pasted in place to next documents' Master  F");
        if (mySelection.selectedIndex == 1){
    var nSel = app.selection.length;   
    for ( var i = 1; i < app.documents.length; i++) {   
            var nextDoc = app.documents[i];   
            if (!nSel) { alert( "Nothing selected!" ); exit(); } 
            for ( var n = 0; n < nSel; n++ ) { 
                var curSel = app.selection[n]; 
                curSel.duplicate( nextDoc.masterSpreads[6] ); 
    alert("Done.\rWhat you select are pasted in place to next documents' Master G");
    but unfunction, can you fix it?
    thanks
    Teetan

    Hi,
    Modifying your code - notice that function main() suppose to be
    1. defined and
    2. called
    Compare it to this code:
    #target  indesign
    var
      myDialog = app.dialogs.add({name:"Copy Selected item(s) to chosen Master",canCancel:true}),
      mStringList = ["Master A", "Master B","Master C", "Master D", "Master E","Master F", "Master G"];
    with(myDialog){
      with(dialogColumns.add()){
      staticTexts.add({staticLabel:"Select a Master you want to copy to"});
      with(dialogRows.add()){
      var mySelection = dropdowns.add({stringList:mStringList, selectedIndex:0});
    main();
    function main(){
      if (!app.documents.length || !app.selection.length)
      alert( "Nothing selected!" );
      exit();
      if (myDialog.show() == true)
      copy_to_next_master();
    function copy_to_next_master() {
    var
      mChoice = mySelection.selectedIndex,
      mMsg = "Done.\rWhat you select is pasted in place to next documents - " + mStringList[mChoice],
      nSel = app.selection.length,
      mDone = false,
      i,n,nextDoc,curSel;  
    for ( i = 1; i < app.documents.length; i++) {  
      nextDoc = app.documents[i];  
      targetMaster = nextDoc.masterSpreads[mChoice];
      if (!targetMaster.isValid) {
      mMsg += "\rCan't detect " + mStringList[mChoice] + " in a doc: " + nextDoc.name;
      continue;
      mDone = true;
      for ( n = 0; n < nSel; n++ ) {
      curSel = app.selection[n];
      curSel.duplicate( nextDoc.masterSpreads[mChoice] );
    mDone ? alert(mMsg) : alert("Nothing copied");
    Jarek

  • Multiple Master Pages - how to apply to forms?

    Hello!
    I need to build a form with two pages, one with portrait orientation and the other one with landscape orientation.
    So I created two Master Pagers, one for each, with correspondent orientations.
    The first page is ok, following the portrait Master Page definitions. Now I want to apply the landscape Master Page definitions on the second page - I haven't found where to do it.
    Please, where do I change this?
    Thank you very much for any hints.
    Marcos

    HI Niall,
    I'm glad to have found this thread as I have some forms which need 3 Master pages and something is wrong but I can't figure it out.
    The 1st Master Page is portrait and will be used for the first two pages of content.
    The 2nd Master Page is landscaped and will be used for the third page (or more) content.
    The 3rd Master page has 'fixed' Revision History content and just is what it is, and is ALWAYs last on every form we do.
    So I was able to get the first two content pages on the first Master page (portrait) and it looks fine.
    So far, so good.
    Now for the problem:
    The next "content" page is landscaped, but I cannot put content on it. In fact, if I click on that page, the Master Page is highlighted.
    If I delete it, the 2nd Master Page is deleted as well.
    Moving on:
    The next page does use the appropriate landscaped Master Page and looks good.
    The final page is the Rev history page, as expected.
    NOTES: on the difficult page I have tried to use the information you have here but it doesn't work as it appears to be a Master Page.
    How does a master page show up in the Design View and not allow content to be placed on it? How can I remove it?
    Thanks an awful lot - hope your weather is better than ours!
    Slan!

  • Master page unnecessarily repeated in adobe forms.

    Hi ,
    The scenario i m trying to develop is to have data and an image field on the first page followed by only data on the next page.For this i have created two master pages and two body pages.The first master page has got an image field attached and 4 content areas.The second master page has got only 4 content areas.The pagination of the bodypages is done as described below :
    bodypage1--placed on master page 1,after : go to next content area ,if dataset must be paginated :goto next master page
    bodypage2--placed on master page 2,after : go to next content area
    The problem i am facing is result is displyed like :
    data on page like master page1 (required)
    empty page like masterpage1 (NOT REQD)
    rest data on pages like masterpage2(reqd)
    THIS EMPTY PAGE IS A PROBLEM.Can anyone tell where i m going wrong?
    Thanks,
    Ashwani Rohilla

    Hello,
    For this you need not create a master page, body page...complete design your whole layout in design view of default page...and dont change the settings of pagination tab... I think that should work.
    thanks,
    Rakesh.

Maybe you are looking for