Objects below master page menu

I have a master page with menu and bar black on the top. What I do is that the contents of other pages go under the master page content. And do not get done.
As you can do?
thanks

Are you editing the master template page or a page that has the master applied to it?
Right click the element>arrange>bring to front

Similar Messages

Click event on sub page menu makes my master page menu go away..???

I've populated a menu using xml retrieved from a stored procedure and all is working great, except when I select an item from the sub menu and call a click event and it makes my main menu on my site.master go away and shifts the current aspx page up.
<asp:Menu ID="mnu_catproj" runat="server" BackColor="#B5C7DE" DynamicEnableDefaultPopOutImage="False" DynamicHorizontalOffset="2"
DynamicPopOutImageTextFormatString="" Style="position: relative;" Font-Bold="True" Font-Italic="False" Font-Names="Verdana" Font-Size="X-Small"
ForeColor="White" Orientation="Horizontal" StaticEnableDefaultPopOutImage="False" StaticSubMenuIndent="10px" >
<DataBindings>
<asp:MenuItemBinding DataMember="Category" TextField="#InnerText" ValueField="#Value" />
<asp:MenuItemBinding DataMember="Project" TextField="#InnerText" />
</DataBindings>
<DynamicHoverStyle BackColor="#CC9900" ForeColor="#0000CC" />
<DynamicMenuItemStyle HorizontalPadding="5px" VerticalPadding="2px" />
<DynamicMenuStyle BackColor="#B5C7DE" />
<DynamicSelectedStyle BackColor="#507CD1" />
<StaticHoverStyle BackColor="#284E98" ForeColor="White" />
<StaticMenuItemStyle HorizontalPadding="5px" VerticalPadding="2px" />
<StaticSelectedStyle BackColor="#507CD1" />
</asp:Menu>
Protected Sub mnu_catproj_MenuItemClick(sender As Object, e As MenuEventArgs) Handles mnu_catproj.MenuItemClick
lblCategory.Text = mnu_catproj.SelectedItem.Parent.Text.ToString()
lblProject.Text = mnu_catproj.SelectedItem.Text()
btnMD_submit.Enabled = True
End Sub
I know the click event is calling the subroutine but the Master Page menu goes away
<asp:Menu ID="MainMenu" runat="server" DataSourceID="XmlDataSource1" Font-Names="Verdana" ForeColor="#333399" ScrollDownImageUrl="/Images/menuSeparator.gif" StaticPopOutImageUrl="/Images/menuSeparator.gif" Orientation="Horizontal" DynamicPopOutImageUrl="~/Images/triangle-16.gif" ItemWrap="True" CssClass="menuStyle" Height="27px">
<DataBindings>
<asp:MenuItemBinding DataMember="Menu" Depth="0" TextField="text" Selectable="False" />
<asp:MenuItemBinding DataMember="SubMenu" Depth="1" NavigateUrlField="url" TextField="text" ValueField="url" />
<asp:MenuItemBinding DataMember="SubMenu" Depth="2" NavigateUrlField="url" TextField="text" ValueField="url" SelectableField="url" />
<asp:MenuItemBinding DataMember="SubMenu1" NavigateUrlField="url" TextField="text" ValueField="text" ToolTipField="#Value" TargetField="target" />
</DataBindings>
<DynamicHoverStyle BackColor="#003399" Font-Size="X-Small" ForeColor="White" Font-Bold="False" />
<DynamicMenuItemStyle HorizontalPadding="10px" VerticalPadding="5px" BackColor="#E5E5E5" BorderColor="#999999" BorderStyle="Solid" BorderWidth="0.01em" Font-Size="X-Small" ForeColor="Black" />
<DynamicMenuStyle BackColor="#E5E5E5" />
<DynamicSelectedStyle BackColor="#507CD1" Font-Size="X-Small" />
<StaticHoverStyle BackColor="#FF9900" ForeColor="White" Font-Bold="False" />
<StaticMenuItemStyle HorizontalPadding="15px" VerticalPadding="4px" />
<StaticMenuStyle CssClass="menuStyle" />
<StaticSelectedStyle BackColor="#FFCC66" />
</asp:Menu>
finally: this works fine in Firefox browser but not in IE or Chrome

Hi DeanO78O,
This forum is to discuss problems of Windows Forms. Your question is not related to the topic of this forum.
You could post it in the dedicated ASP.Net Forum
http://forums.asp.net for more efficient responses, where you can contact ASP.NET experts.
Best regards,
Youjun Tang
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

InDesign encounters error when locking objects on master page

I have CS5 and love it. But, after moving objects on my master page between layers (don't ask me why, just thought it might be a good idea) I cannot lock (Ctrl-L) the objects without locking InDesign. It encounters a error and locks up. I have to use the Task Manager to close it and start over. Are you not allowed to move objects on the master page between layers? Do I need my mouse slapped?

Eugene means that master objects are difficult to select on a live page (you have to Ctrl + Shift Click them to override) so there is really little reason to lock them. You shouldn'ty be getting acrash when you try, though. First step might be Replace Your Preferences

Auto-number page objects from master pages

Hello all! I'm trying to set up a photo contact sheet template in InDesign so that we can get rid of the one we're using in Word that's rather...clunky. The only caption underneath each photo will be a simple, basic number that increases sequentially. There are six photos per page. I dove into numbered lists for the first time and figured out how to make the numbered captions work on the regular document pages, but I am trying to avoid creating the caption text box objects there because these contact sheets could be anywhere from 10-40 pages, and it's much easier to just create a slew of new pages from a master page.
When I transfer the number captions to the master page, the numbers are correctly sequenced when a single new document page is created from that master...but any additional document pages have the same sequential numbers (e.g. 1-6)! Is there a way to get around this?

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?

Change the font typeface of text object in form Master Page

Dear all,
        I am creating a Adobe Livecycle form with multi-language support. Simply, there is a header title that is a text object in master page. I want that it can be converted to simplified Chinese from English and change its font typeface to “SimSun” when printing begins. I try the following code on its “Initize” event to do this.
Simply, I configure a print flag(Y/N) in form so that it will convert into simplified Chinese and change the font typeface to ‘SimSun’ when the flag is reset to ‘Y’.
Int langInt = i ;
If (pFlag == “Y”) {
           PaymentRequisitionApp.pageSet.Page1.MasterSubform. Text1.value.text.value = l_XML.Record[i].TITLE.toString();
           PaymentRequisitionApp.pageSet.Page1.MasterSubform. Text1.font.typeface ="simsun";
I found that it doesn’t work. There is something else in the form to reset the title to English. So I try to paste the code above in “calculate” event of tex1 object. It’s work!
Question:
1.      Anyone can tell me that the implement order of the events in the form?
2.      Does it exist other better way to do this?
        3. Which event, function or any else let the master page’s object to be reset?

this link for downloading the sample is valid:
http://rapidshare.com/#!download|935|429748707|TEST2.pdf|84.309

How to reduce the weight of SharePoint master page.

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






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







firstbank








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








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

















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







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






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




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




<meta charset="utf-8" />

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

</head>
<body>



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

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

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









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

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

Master page issue

Has the problem of objects in the master pages falling out of the document after exporting to pdf been addressed in CS6?

Two very recent threads on this:
http://forums.adobe.com/thread/1018754?tstart=60
http://forums.adobe.com/thread/1016281?tstart=30
Both threads mention CS6, but I can personally vow this also happens with CS4 -- only last month, an intern ran afoul of it and all I needed was a single glance to spot the issue.
I have a habit of *never* straddling objects across master pages; it could be I learned not to as much as a decade ago. I'm pretty sure every now and then it was mentioned as a harmful bug in this forum.

Strange tags in master pages - any idea how they got there?

NOTE: This issue is related to my posting (1/2 way down) in http://forums.adobe.com/message/4539747#4539747
but I wanted to start a new thread to separate it as its own problem.
I just noticed that when I create a new topic, I see this unusual local formatting <p class="TABELBODY"> tag in HTML view (see below, 4rth line from bottom). This is where the mysterious "TABLEBODY" formatting is originating that I've been plagued throughout my current project.
If I delete the default text in this new topic (in Design mode), this <p class="TABELBODY"> still winds up in the topic when viewing in HTML view (see below, 3rd line from bottom).
When you start adding new text in the topic in Design mode, it attaches itself to your first line of text as local formatting (see below, 9th line from bottom):
When you view the topic in Design mode and place your cursor on the first line of text, you'll see this local formatting TABELBODY display in the syle dropdown (see below).
I decided to open up a new topic using my other master page, and also noticed strange tags in it (<?rh-region_start type="body" ?> ). See below, 3rd and 12th lines from bottom.
Consequently, I finally figured out that both my master pages had junk HTML tags in them, which carried over to all of my topics. I have now fixed the master pages by editing out the junk in the HTML mode.
I did some further investigation and found out that the originating project that was the basis for my current project also had master pages with the same tag issues. So now I'm wondering, how did this start? Maybe someone imported a RH html output file into a project by mistake a long time ago, and it corrupted the master pages right up until this time? Or, could it have been from upgrading from RH 7 to 9?

Boy, this is really getting stranger by the moment...every time I think I have solved a problem in RH, another layer of problems emerges...
I made the minor edits on my two master pages to get rid of the junk tags shown above and did a Save All. Here is the result (see screens below):
Master Page 1 After Edits
Master Page 2 After Edits
That's ALL I touched. However, now when I view any topic using these master pages with either the Preview mode (eyeglass icon) or as a final output file, the default text from those master pages displays on top of the topic. Interestingly enough, the master page text does NOT display in these topics in Design mode.
Preview Mode of Topic Using Master Page 1, Displaying Default Text from Master Page 1 on Top
Preview Mode of Topic Using Master Page 2, Displaying Default Text from Master Page 2 on Top
HTML View of Topic Using Master Page 1
HTML View of Topic Using Master Page 2
I'm crying "uncle" now - help!!

Digital Signature issue in Master pages

Hi,
I have added signature field object in the master page. I am not able to sign pdf through e-signature whenever i am defining signature object on master page.
I tried to add object on the normal page, then it is working fine.
Can anybody suggest cause of the same?
Thank you.
Sachin

Ritwika,
Are the User Name and Password correct? Is the User assigned to the SAP_XMII_User role in Netweaver? On the iCommand's Security screen, is the SAP_XMII_User assigned as a Reader role?
Have you checked the Netweaver log? There may be more detailed information there.
Kind Regards,
Diana
Edited by: Diana Hoppe on Mar 3, 2011 9:50 AM

Why Is The Menu On The Master Page BELOW The Objects In Other Pages?

I added a menu on the master page using the Composition widget called featured news and it stays behind the other objects on normal pages.
How do I fix this? Here are the pictures of the menu when it's closed and when it's open.

Make a new layer, which is by default placed above all other layers.
Go to your master page and drag the menu onto this layer.

About Me link is not visible in Welcome Menu if placed on custom location in Custom Master Page

Experts,
I am facing a problem in my -ongoing SP 2013 project's branding. The problem is with Welcome Menu. I need to put the welcome menu at a custom place rather than in ribbon area. for this I added welcome menu snippet inside my Master Page HTML but there is
a problem with it. On ribbon link "About Me" is visible while at the same time link "About me" is not visible on welcome menu which has been inserted on custom place. below images describe my problem more accurately.
I need help in this regard if some one can help me. For your information My User Profiles are properly configured and working.
HBkhan

Hi Haris,
I tested the same scenario in my environment, and the link will display My Settings link instead of About Me link when there is more than one welcome menu in the page.
If you want to put the welcome menu at a custom place rather than in ribbon area, I recommend you remove the welcome menu in the ribbon area(suitebar) after putting the other welcome menu at the custom place.
Thanks,
Victoria
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Victoria Xia
TechNet Community Support

How do I 'assign a higher layer to the object on the master' (page numbers on master) I understand the layer needs to be at the top to show above placed images on pages but how do I do this?

I've added the page numbers to my master pages. They are displaying on the pages but I have images on the individual pages that are covering the numbers. I understand I need to assign a higher layer to the object but I don't understand how to do that. Please help me? Please explain a simply clearly as possible, I've read other answers but still don't understand. Wish it was as simple as select object, right click, edit layer!
Many thanks!

Layers panel;
Create new layer
Switch to Master page
Make sure new layer is on top in the Layers panel, if not drag the layer on top in the Layers panel.
Select (click once on) that top layer (pen symbol appears behind that layer in the Layer panel)
Now draw your page numbers etc on the Mastet page
From now on, select (click once on) any Layer in the Layers panel that is below the layer you used on your Master page items and create new objects in your document pages.
If you accidently created objects on a 'wrong' layer:
Select those objects
You will see a square behind the layers name in the Layers panel
Click and hold the mouse on that square and drag it behind the name of the layer you want to move the objects to.
Buy a book about InDesign and start learning these basic principles!

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

Cannot download master page using managed client object model SharePoint 2010

string siteUrl = "http://server:port/sites/demo";
string fileServerRelativeUrl = @"/sites/demo/_catalogs/masterpage/v4.master";
using (ClientContext context = new ClientContext(siteUrl)){ FileInformation fileInfo = Microsoft.SharePoint.Client.File.OpenBinaryDirect(context, fileServerRelativeUrl);}
File.OpenBinaryDirect() throws "The remote server returned an error: (404) Not Found" error. while Microsoft.SharePoint.Client.File f1 = web.GetFileByServerRelativeUrl(fileUrl);
context.Load(f1);
context.ExecuteQuery();this gives the file object.File.OpenBinaryDirect() works if I pass "/sites/demo/_catalogs/masterpage/TabViewPageLayout.aspx" as fileServerRelativeUrl.Both the files are present in Master Page Gallery.File.OpenBinaryDirect() doesn't work if I pass any of ".master" file in the master page galleryPlease let me know whether downloading the master pages is supported using managed Client object model.

Hi,
If don't change the default config, We are unble to download master page.
It's better to create your own (perhaps based on the default.master) and use that master page.
also,make sure there's no a permission issue on the website.
Thanks
Guangchao chen
TechNet Community Support

Master page objects with drop shadows crossing over spreads

Mac 10.5.4 - INDesign CS3
I have a book file that is giving me a pretty hard time. There are several master page spreads that do not show as spreads in the book file. The left page from one set of masters with the right page from another set. There is a grouped row of circles that has drop shadow applied that appears on several master spreads. This is built as two groups that meet in the gutter to give the appearance of a row all the way across the spread. When the group is on the gutter between the two pages of the master spread, The object will show up on the both pages of the book spread, on top of the data from the left page master. If we shut off the drop shadow, no problem. If we move the group 0p5 away from the gutter no problem. The problem is that in the end we want this element to have a drop shadow and to run into the gutter.
Does InDesign count the spread of the object effect as part of the object itself? That seems like what is happening. Is there a fix (work around) for this?

The easiest workaround I know of is to paste the object with the drop shadow inside another box such that you can clip it at the gutter. We've cursed this "feature" for years.

Objects below master page menu

Similar Messages

Maybe you are looking for