Delete Master Page?

Is there a way to delete Master Page designs in Aperture books? I want to narrow my choices of Master Pages. I know how to add new ones, but how do I delete some of them?
Kevin

Is there a way to export/share custom master pages that are created?
i have found that the default set is located at:
user/Library/Application Support/Aperture/Book Themes/MyPublisher Theme/Pages
Note, that 'MyPublisher Theme' is what i named my custom theme within Aperture.
Any help appreciated.

Similar Messages

InDesign CS5 keeps crashing when I try deleting master pages.

I am working on a CS4 template (converted to CS5) and each time I try deleting a master page, InDesign crashes. I have also tried the Adobe InDesign 7_0_3 Patch All update but it has not helped. Any tips?

That worked! Thanks for the tip

Script add/delete master page automatically

I've searched and haven't managed to find one so apologise if this has been asked before.
Adobe Indesign CS2
Does anyone have a script to automatically insert, or delete my master page with an automatic text link between the frames on my pages, as I am loosing too much time adding and deleting manually. The page is my 'A-Master'
I have never installed a script before, nor know how to but I must invest time in this as it will save me lots of time in the future with the programming behaving like a word processor (microsoft word) with the beauty of the design elements with indesign.
Regards

Are you looking for some sort of feature that adds pages and link the text automatically as you type and reach the end of a page? That isn't going to happen in CS2, even with a script, as far as I know. There might be a plugin available, but it won't be free.
You'd be better off upgading while you still can get upgrade pricing. Smart Text Reflow was introduced in CS4 and does exactly what I think you want.

Haw to restore deleted master page object

If I apply Master Page to some page an then override and delete some object which originates on master page - is there any way to bring it back again with scripting?
I'd like to avoid reapplying Master Page - becuse I don't wat to reset overridden attributes other master page objects.

Most properties can be stored and applied using the "properties" property.
Depending on the content type, you will need to handle it differently. FWIW, here's some code that will apply properties from one text frame to another. For content you would need to either move/copy the text or thread the frame.
function applyProperties(origin,target){
    target.appliedObjectStyle=origin.appliedObjectStyle;
    target.properties = GetTextFrameProperties(origin)
    target.textFramePreferences.properties=origin.textFramePreferences.properties;
    target.textWrapPreferences.properties = origin.textWrapPreferences.properties;
function GetTextFrameProperties(frame){
    var frameProps = frame.properties;
    var e;
    //frame = frame.properties;
    var properties = {}
    for( var x in frameProps){
        switch (x){
            //case
        //appliedObjectStyle:frame.appliedObjectStyle,
//~        contentType:frame.contentType,
            case "cornerRadius":properties.cornerRadius = frameProps.cornerRadius;break;
            case "fillColor": properties.fillColor = frameProps.fillColor;break;
            case "fillTint": properties.fillTint = frameProps.fillTint;break;
            case "gapColor": properties.gapColor = frameProps.gapColor;break;
            case "gapTint": properties.gapTint = frameProps.gapTint;break;
            case "horizontalScale": properties.horizontalScale = frameProps.horizontalScale;break;
            case "itemLayer": properties.itemLayer = frameProps.itemLayer;break;
            case "label": properties.label = frameProps.label;break;
            case "rotationAngle": properties.rotationAngle = frameProps.rotationAngle;break;
            case "shearAngle": properties.shearAngle = frameProps.shearAngle;break;
            case "strokeAlignment": properties.strokeAlignment = frameProps.strokeAlignment;break;
            case "strokeColor": properties.strokeColor = frameProps.strokeColor;break;
            case "strokeTint": properties.strokeTint = frameProps.strokeTint;break;
            case "strokeType": properties.strokeType = frameProps.strokeType;break;
            case "strokeWeight": properties.strokeWeight = frameProps.strokeWeight;break;
            //textWrapPreferences: properties.frameProps.
            case "verticalScale": properties.verticalScale = frameProps.verticalScalebreak;
            case "allowOverrides": properties.allowOverrides=frameProps.allowOverrides;break;
            case "absoluteHorizontalScale": properties.absoluteHorizontalScale=frameProps.absoluteHorizontalScale;break;
            case "absoluteRotationAngle": properties.absoluteRotationAngle=frameProps.absoluteRotationAngle;break;
            case "absoluteShearAngle": properties.absoluteShearAngle=frameProps.absoluteShearAngle;break;
            case "absoluteVerticalScale": properties.absoluteVerticalScale=frameProps.absoluteVerticalScale;break;
            case "dataStore": properties.dataStore=frameProps.dataStore;break;
            case "endCap": properties.endCap=frameProps.endCap;break;
            case "endJoin": properties.endJoin=frameProps.endJoin;break;
            case "gradientFillAngle": properties.gradientFillAngle=frameProps.gradientFillAngle;break;
            case "gradientFillLength": properties.gradientFillLength=frameProps.gradientFillLength;break;
            case "gradientFillStart": properties.gradientFillStart=frameProps.gradientFillStart;break;
            case "gradientStrokeAngle": properties.gradientStrokeAngle=frameProps.gradientStrokeAngle;break;
            case "gradientStrokeLength": properties.gradientStrokeLength=frameProps.gradientStrokeLength;break;
            case "gradientStrokeStart": properties.gradientStrokeStart=frameProps.gradientStrokeStart;break;
            case "javascript": properties.javascript=frameProps.javascript;break;
            case "leftLineEnd": properties.leftLineEnd=frameProps.leftLineEnd;break;
            case "localDisplaySetting": properties.localDisplaySetting=frameProps.localDisplaySetting;break;
            //properties.locked=frameProps.locked;
            case "miterLimit": properties.miterLimit=frameProps.miterLimit;break;
            case "nonprinting": properties.nonprinting=frameProps.nonprinting;break;
            case "overprintFill": properties.overprintFill=frameProps.overprintFill;break;
            case "overprintGap": properties.overprintGap=frameProps.overprintGap;break;
            case "overprintStroke": properties.overprintStroke=frameProps.overprintStroke;break;
            case "rightLineEnd": properties.rightLineEnd=frameProps.rightLineEnd;break;
            case "strokeCornerAdjustment": properties.strokeCornerAdjustment=frameProps.strokeCornerAdjustment;break;
            case "strokeDashAndGap": properties.strokeDashAndGap=frameProps.strokeDashAndGap;break;
            case "cornerEffect": properties.cornerEffect = frameProps.cornerEffect;break;
            case "featherCornerType": properties.featherCornerType = frameProps.featherCornerType;break;
            case "featherMode": properties.featherMode = frameProps.featherMode;break;
            case "featherNoise": properties.featherNoise = frameProps.featherNoise;break;
            case "featherWidth": properties.featherWidth = frameProps.featherWidth;break;
            case "isolateBlending": properties.isolateBlending = frameProps.isolateBlending;break;
            case "nonprinting": properties.nonprinting = frameProps.nonprinting;break;
            case "opacity": properties.opacity = frameProps.opacity;break;
            case "shadowOpacity": properties.shadowOpacity = frameProps.shadowOpacity;break;
            case "shadowSpread": properties.shadowSpread = frameProps.shadowSpread;break;
            case "shadowXOffset": properties.shadowXOffset = frameProps.shadowXOffset;break;
            case "shadowYOffset": properties.shadowYOffset = frameProps.shadowYOffset;break;
            case "cornerOption": properties.cornerOption = frameProps.cornerOption;break;
            case "flip": properties.flip = frameProps.flip;break;
            case "absoluteFlip": properties.absoluteFlip = frameProps.absoluteFlip;break;
    return properties;
Harbs

Can't delete master spread

Dear All,
I'm trying to delete a master page but the option DELETE MASTER SPREAD is greyed out. It is not in use on any page, but still won't let me delete -- any idea why?
InDesign CC seems to be very quirky!
Small Town Gal

If you only have two master pages, that is [none] and A-master, and you did not use the A-master for some reason, you only use the [none] then you have no option to delete any of those master pages.
However if you have too many master pages, try to double check if you really did not use a particular master page by going to flyout of Pages -> Master Pages -> Select Unused Masters
After that go back to Pages -> then Delete Master Pages.
Hope it helps.

How to delete a submenu menu item from a master page?

I am having trouble deleting a submenu item from a menu on a master page. I'm not sure where or how it was created, but simply selecting it and trying to delete it, is not working...

Sub-menus are generated by your site structure. Either delete the page or disable it from menus with the contextual menu. If it's not a page, make a temporary change to the site structure and then change it back to force Muse to refresh, it might be a glitch.

Page numbers from MS Word cannot be deleted in pages

A colleague sent me a MSWord (Mac) document that I opened in pages 09 and started working on it. I need to delete the page numbers that were put in on the MSWord document. I guess they were put in using the automatic page numbering feature in Word. However, In the Pages09 document they are not in the usual footer location. It almost looks like they are part of the page background. They are not selectable and cannot be removed. It I choose to add page numbers using Pages, they numbers appear in the usual footer location—in addition to and not supplanting– the unselectable page numbers brought over from MSWord. Does anybody know a solution to this?

Loren,
The persistent content usually is a Master Object. So, you were right to begin with: Format > Advanced > Make Master Objects Selectable. One would think that if this is always the solution, it would be a simple matter to now select the tenacious item and delete it. The problem is that sometimes the object while now selectable is still not accessible.
This Master Object can hide behind the Header box, as though the Header was a solid glass wall. Deselecting the Header function, in the Document Inspector, will give you access, but it will also irretrievably delete your Header Content. A better way, I have found, is to change the header Margin figure in the Document Margins Pane of the Document Inspector.
Once you have moved the Header, Footer, or whatever else might be sharing the space, off the persistent page number, you can click on the page number Object and hit Delete. Now you can put back whatever you had to move, and you should be good to go. Consider yourself lucky if your Pages header doesn't fall over the old Word Header.
Jerry

Adding new elements to a Master Page and sharing them to existing pages

I need to include new navigation elements on the master page
and I want it to show up on pages I've already created. I've added
the new elements on a layer of their own which is part of the
master page, but the Share Layer to Pages... option is dimmed.

jcbluesman wrote:
> I'm using CS4, Jim, and here's a link to the .png
> (
http://idisk.mac.com/jconstant-Public/deimos.png
>
> The 3 tabs in the upper right on the master page are the
ones I'm trying to
> share across the existing pages. I created them in PS
(also CS4), then imported
> the .psd into this FW document, if that makes any
difference.
>
> Thanks,
> Jim
>
OK there are two related as I see it.
Each of your pages consists of a solid, opaque bitmap for a
main image.
Master Pages, by default, are at the bottom of the layer
stack. Your
tabs ARE present, you just can't see them because they are
covered up by
the bitmap.
Assuming you don't have those page images as multi-object
elements,
where you can edit the blue backgrounds, there are still two
things you
can do, both of which are pretty easy.
Go into each page and temporarily reduce the opacity of Layer
1.
Use the marquee tool to draw a selection around the area of
the tabs.
Delete the selection.
Return the lay back to full opacity.
OR
Try dragging the Master page to the top of the layer stack in
each page.
Hide or delete the Master page background.
This option is a little trickier, but I was able to do it.
Wait for the
black bar to appear before you release the mouse. You may
need to try
this a few times before it works.
HTH
Jim Babbage - .:Community MX:. & .:Adobe Community
Expert:.
http://www.communityMX.com/
CommunityMX - Free Resources:
http://www.communitymx.com/free.cfm
.:Adobe Community Expert for Fireworks:.
Adobe Community Expert
http://tinyurl.com/2a7dyp
.:Author:.
Lynda.com -
http://movielibrary.lynda.com/authors/author/?aid=188
Peachpit Press -
http://www.peachpit.com/authors/bio.aspx?a=d98ed798-5ef0-45a8-a70d-4b35fa14c9a4
Layers Magazine -
http://www.layersmagazine.com/author/jim-babbage

I am having major issues with links in keynote! Even though the links (a navigation system) are on the master page, they are only working on some of my slides. Anyone have ideas on how to fix this or similar issues? Help!

I am having major issues with links in keynote! Even though the links (a navigation system) are on the master page, they are only working on some of my slides. Anyone have ideas on how to fix this or similar issues? Help!
I have created a navigation system on the master pages and set the presentation to links only mode. I also have other links scattered throughout the program, like a linkable table of contents, etc. Some of them work, some of them don't. Not sure why. Anyone out there having similar issues? Or have any idea on how I can solve this issue? Any help would be appreciated!
Thanks!

Links should not create any problems in Keynote. If they are set up correctly on text, the text will be underlined. Objects that have links will have a curved arrow bottom right, if you click the arrow a popup will display the link information.
Try this repair for Keynote, ensure you complete all the tasks and in the order shown:
1
delete all the iWork applications if you have them, not just Keynote, using Appcleaner from Mac Update, its a freeware application
2
empty the trash: Finder > Empty Trash
3
Shut down your Mac, wait 30 seconds, then power on the Mac, immediately after the start chime, hold down the Shift key
When you see the grey Apple symbol and progress indicator (a spinning gear), release the Shift key.
If you are prompted to log in, type your password, then hold down the Shift key again as you click Log in.
4
Let the Mac fully boot up, it will take longer as the OS is repairing the drive
5
when fully booted, go to Applications > Utilities > Disc Utility; click on the boot drive then First Aid tab and click repair disc permissions
6
when complete, restart the Mac normally, Apple menu > Restart
7
install Keynote from the Mac App Store
let us know if this helped

How to remove all pages from layout? (except Master Page)

Geetings Experts:
I'm implementing additional security measures into my 'initialze' event, where I'll check some global variables and render the file unreadable if needed.
Which object and properties do I access to remove all my pages from the form?
I would like to createa a function that removes all the sub pages, leavning only the Matster Page, enable a label in the MasterPage and save itself.
I searched for xfa.layout and Page[n].remove() methods but cannot find any reference to these.
.presence = "hidden", fulfills my purpose but the pages remian visible and I need for a clean solution no pages are visible.
I'm advanced in C# but a novice in LC JavaScript, so any comment, reference or code snipet will be greatly appreciated
Thank you for your time,
Ivan A. Loreto – Computer Education Technician
LOMA LINDA UNIVERSITY | School of Allied Health Professions - Department of Physical Therapy
[PDF Development Platform]
Windows XP SP3
Acrobat Pro 9
LifeCycle Designer ES 8.2

Hi Ivan,
The particular syntax of Javascript in LC Designer is different from that used in Acrobat and different (as I understand it) from core javascript and other applications. There are several free guides on the Adobe web site which cover Acrobat and LC:
http://www.adobe.com/go/learn_lc_scriptingBasics
http://www.adobe.com/go/learn_lc_scriptingReference
http://www.adobe.com/go/learn_lc_formCalc
http://www.adobe.com/devnet/livecycle/articles/Adobe_XML_Form_Object_Model_Refer ence.pdf
http://www.adobe.com/devnet/acrobat/pdfs/lc_migrating_acrobat_xmlform.pdf
And a very handy resource (it goes back to version 6, but is still applicable):http://partners.adobe.com/public/developer/en/tips/CalcScripts.pdf
JP Terry's book on LC Forms is very good and we use www.pdfscripting (which is a subscription service). If you are going to be doing a lot of LC Designer work, these may be of help.
I am not a coder, so I going to try and work through your script. Bear with me if you already have this sorted...
The script looks ok and you are using the resolveNode method correctly. Seeing topmostSubform in the resolveNode indicates that you imported an existing document into LC. This is fine, but sometimes it restricts some of the functionality.
For starters I think that mPg is returning null. You can use the following in your script to see what is happening (debugging) and then comment it out:
console.println("mpg: " + mPg);
Then when previewing hit control+J to bring up the javascript console, then will show the value of mPg when that script executes.
Try deleting the SOM up to #pageSet:
var mPg = xfa.resolveNode("#pageSet.MasterPage1");
The javascript console will show you when the script is working.
In relation to the loop, I would advise a few changes:
for (var i=1; i <= xfa.layout.pageCount(); i++)
     var vPage = ("xfa.form.topmostSubform.Page" + i).toString();
     //console.println("vPage: " + vPage);
     var curPage = xfa.resolveNode(vPage);
     curPage.presence = "hidden";
}//next page
There are a few things here:
I would declare i as a variable, not an integer (not sure if it makes a difference);
I would use pageCount rather than numPages and then <=;
There was an extra ; at the end of the loop declaration;
I would break the script into steps and get the full SOM of the page as a variable first and then resolveNode that variable;
You don't need to go to the current page;
I tend to name master pages with a capital "P" and pages with a small "p". Personal preference, but it can make tracking script easier.
Have a crack off that and hopefully you can get it to work,
Niall
ps another tip, if you want to reference an object in script. First click on the object you want to script for and then scroll (or click on the master page) for the object you want to reference. Click inside the script editor and then when you move the mouse back into the form, press and hold Control, this will turn the mouse into a "V". When you click on the object you want to reference it will insert the SOM into the script. If it needs the resolveNode it will automatically put that in for you. Holding Shift and Control will insert a fully resolved node.

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&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

Moved page no longer displays Master Page elements.

After moving a page in my document the master page elements no longer display on screen or in print. If I move the page to a different location in the document the master displays but if it is in the specific position that it needs to be it will not display. The document has multiple Masters and others do work on the page but the one that I need will not. I've tried deleting the page and adding a new one and that does not fix the problem. I've checked and "Hide Master Items" is not checked. The page in question is in position 48 with F-Master applied. If I move it to position 49 it works, 50, it works, 51, or any other it works. If I apply a different master to the page, it works. If I delete the page, add a new page and apply F-Master it still does not work. The only page that this problem is happening on is page 48.

try exporting to .idml. See Remove minor corruption by exporting

Master page: header changes are not reflected in existing topics

A few months ago this forum helped me to troubleshoot and fix problems with the Show More | Show Less command that I inherited from a previous writer. I chose to use the Single Button approach and used this code, on the Master Page, for "onclick":
<body>
<?rh-script_start ?><script src="ehlpdhtm.js" type="text/javascript" language="JavaScript1.2"></script><?rh-script_end ?>
<?rh-region_start type="header" style="width: 100%; position: relative;" ?>
<table style="height: 10px;" cellspacing="0" width="100%">
<col width="186" />
<col width="481" />
<col width="97" />
<tr>
   <td><h2><img src="NGP_Logo_small.png" alt="" style="border: none;"
       border="0" /></h2></td>
   <td><h2 style="text-align: right; margin-right: 20px;">Help</h2></td>
   <td><h2><img src="btnshowall.gif" onclick="ShowAll(this)" alt=""
       style="border: none;" border="0" /></h2></td>
This worked fine until recently when I changed the logo in the left cell of the header table. Today I discovered that the img src = line had gone away. And so I re-entered it, and it works fine on new topics, and on some, but NOT all topics.
Here's what happens on an older topic:
Preview the topic.
Click Show All button. A Script Error message appears: "The value fo the property 'ShowAll' is null or undefined, not a Function object. Code = 0. file = ...../Help/Administration/rlt1F1.htm.
Here's the HTML code for this topic, which is missing the code btnshowall code.
<body>
<?rh-script_start ?><script src="../ehlpdhtm.js" type="text/javascript"
        language="JavaScript1.2"></script><?rh-script_end ?>
<?rh-placeholder type="header" ?>
<table cellspacing="0" width="100%">
<col style="width: 80.663%;" />
<col style="width: 19.337%;" />
<tr>
<td><h1><?rh-variable_start name="title" format="default" showcode="showcode"
          value="Setting Global Defaults" ?>Setting Global Defaults<?rh-variable_end ?></h1></td>
<td style="vertical-align: bottom;"><p style="text-align: right;
             margin-bottom: 6pt; line-height: Normal;"> </p></td>
</tr>
</table>
I tried setting the Master Page to None and then re-setting it to Main. That does not help.
The only workaround I've found so far is to create a new topic, copy the content from the old topic, delete the old topic, and rename the new topic using the old topic's name. But that is very tedious.
Any thoughts on how to fix the problem without recreating every topic?
Thank you.
Carol

A few months ago this forum helped me to troubleshoot and fix problems with the Show More | Show Less command that I inherited from a previous writer. I chose to use the Single Button approach and used this code, on the Master Page, for "onclick":
<body>
<?rh-script_start ?><script src="ehlpdhtm.js" type="text/javascript" language="JavaScript1.2"></script><?rh-script_end ?>
<?rh-region_start type="header" style="width: 100%; position: relative;" ?>
<table style="height: 10px;" cellspacing="0" width="100%">
<col width="186" />
<col width="481" />
<col width="97" />
<tr>
   <td><h2><img src="NGP_Logo_small.png" alt="" style="border: none;"
       border="0" /></h2></td>
   <td><h2 style="text-align: right; margin-right: 20px;">Help</h2></td>
   <td><h2><img src="btnshowall.gif" onclick="ShowAll(this)" alt=""
       style="border: none;" border="0" /></h2></td>
This worked fine until recently when I changed the logo in the left cell of the header table. Today I discovered that the img src = line had gone away. And so I re-entered it, and it works fine on new topics, and on some, but NOT all topics.
Here's what happens on an older topic:
Preview the topic.
Click Show All button. A Script Error message appears: "The value fo the property 'ShowAll' is null or undefined, not a Function object. Code = 0. file = ...../Help/Administration/rlt1F1.htm.
Here's the HTML code for this topic, which is missing the code btnshowall code.
<body>
<?rh-script_start ?><script src="../ehlpdhtm.js" type="text/javascript"
        language="JavaScript1.2"></script><?rh-script_end ?>
<?rh-placeholder type="header" ?>
<table cellspacing="0" width="100%">
<col style="width: 80.663%;" />
<col style="width: 19.337%;" />
<tr>
<td><h1><?rh-variable_start name="title" format="default" showcode="showcode"
          value="Setting Global Defaults" ?>Setting Global Defaults<?rh-variable_end ?></h1></td>
<td style="vertical-align: bottom;"><p style="text-align: right;
             margin-bottom: 6pt; line-height: Normal;"> </p></td>
</tr>
</table>
I tried setting the Master Page to None and then re-setting it to Main. That does not help.
The only workaround I've found so far is to create a new topic, copy the content from the old topic, delete the old topic, and rename the new topic using the old topic's name. But that is very tedious.
Any thoughts on how to fix the problem without recreating every topic?
Thank you.
Carol

Having issues with custom master pages and device channels

I'm working in Sharepoint 2013 and am attempting to create a custom master page that is to be used by mobile devices. I have created an html file and a custom css file that includes snippets from the design manager. The file appears to preview fine in a
browser from Microsoft Web Expression. I have loaded the html file into sharepoint via design manager, so the master file is there as well. The css files are in the style library for the site collection and I have created a device channel including user agent
strings for iphones going back to the iPhone 4 and operating systems going back to iOS 6. I have obviously assigned my custom "mobile" master for that device channel and I have turned off mobile browsing. However when I open the site on my phone
it shows the normal full desktop view and not my custom master. I will include my html code, my css and a screenshot of my device channel below. Please help!
<?xml version="1.0" encoding="utf-8"?>


<!DOCTYPE html[]>
<html xmlns:mso="urn:schemas-microsoft-com:office:office" xmlns:msdt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882">
<head>
<link href="https://otterbein.sharepoint.com/sites/Committees/Style Library/mobile_corev15.css" rel="stylesheet" type="text/css" />
<meta http-equiv="X-UA-Compatible" content="IE=10" />




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









<link href="https://otterbein.sharepoint.com/sites/Committees/Style Library/mobile_corev15.css" rel="stylesheet" type="text/css" />










<link href="https://otterbein.sharepoint.com/_vti_bin/spsdisco.aspx" rel="alternate" type="text/xml" />















<link href="https://otterbein.sharepoint.com/sites/Committees/Style Library/mobile_corev15.css" rel="stylesheet" type="text/css" />
</head>
<body style="width: 330; margin-right: 0px">
<div id="ms-designer-ribbon" style="width:312px">

<div id="TurnOnAccessibility" style="display:none" class="s4-notdlg noindex">
<a id="linkTurnOnAcc" href="#" class="ms-accessible ms-acc-button" onclick="SetIsAccessibilityFeatureEnabled(true);UpdateAccessibilityUI();document.getElementById('linkTurnOffAcc').focus();return false;">


</a>
</div>
<div id="TurnOffAccessibility" style="display:none" class="s4-notdlg noindex">
<a id="linkTurnOffAcc" href="#" class="ms-accessible ms-acc-button" onclick="SetIsAccessibilityFeatureEnabled(false);UpdateAccessibilityUI();document.getElementById('linkTurnOnAcc').focus();return false;">


</a>
</div>


</div>



<div id="s4-workspace" style="left: 0px; top: 0px; width: 329">
<div id="s4-bodyContainer" style="width: 328">
<table style="width: 312px">
<tr>
<td style="width: 312px; background: #666666; text-align:center">
<div class="js-callout-menuAction" style="background:rgb(102, 102, 102); color:white; width:295px; padding:8px; height:64px; overflow:hidden;">In true previews of your site, the SharePoint ribbon will be here.</div></td>
</tr>
<tr>
<td style="width: 312px; background: #CB1920; text-align:center">
<img alt="Otterbein Logo" src="https://otterbein.sharepoint.com/sites/Committees/Style%20Library/otterbein-logo_towers_white_mobile.png" style="padding:5px"><br>
<div data-name="SiteTitle" style="width: 295px; color:white; padding-bottom:5px; text-indent:5px" class="ms-chkmark-container-centerer">
<span style="font-size:xx-large">Committees</span>
</div>
<div WebPartID="00000000-0000-0000-0000-000000000000" HasPers="true" id="WebPart" width="250px" class="ms-WPBody noindex " OnlyForMePart="true" allowDelete="false" style="padding-top:15px; padding-bottom:15px"><div componentid="ctl00_ctl03_csr" id="ctl00_ctl03_csr"><div id="SearchBox" name="Control"><div class="ms-srch-sb ms-srch-sb-border" id="ctl00_ctl03_csr_sboxdiv">
<input type="text" value="Search..." maxlength="2048" accessKey="S" title="Search..." id="ctl00_ctl03_csr_sbox" autocomplete="off" autocorrect="off" onkeypress="EnsureScriptFunc('Search.ClientControls.js', 'Srch.U', function() {if (Srch.U.isEnterKey(String.fromCharCode(event.keyCode))) {$find('ctl00_ctl03_csr').search($get('ctl00_ctl03_csr_sbox').value);return Srch.U.cancelEvent(event);}})" onkeydown="EnsureScriptFunc('Search.ClientControls.js', 'Srch.U', function() {var ctl = $find('ctl00_ctl03_csr');ctl.activateDefaultQuerySuggestionBehavior();})" onfocus="EnsureScriptFunc('Search.ClientControls.js', 'Srch.U', function() {var ctl = $find('ctl00_ctl03_csr');ctl.hidePrompt();ctl.setBorder(true);})" onblur="EnsureScriptFunc('Search.ClientControls.js', 'Srch.U', function() {var ctl = $find('ctl00_ctl03_csr'); if (ctl){ ctl.showPrompt(); ctl.setBorder(false);}})" class="ms-textSmall ms-srch-sb-prompt ms-helperText" style="width: 250px; height: 18px" /><a title="Search" class="ms-srch-sb-searchLink" id="ctl00_ctl03_csr_SearchLink" onclick="EnsureScriptFunc('Search.ClientControls.js', 'Srch.U', function() {$find('ctl00_ctl03_csr').search($get('ctl00_ctl03_csr_sbox').value);})" href="javascript: {}"><img src="/sites/Committees/_catalogs/theme/Themed/EF0ED6F1/searchresultui-61174269.themedpng?ctag=55" class="ms-srch-sb-searchImg" id="searchImg" alt="Search" /></a></div></div></div><noscript><div id="ctl00_ctl03_noscript">It looks like your browser does not have JavaScript enabled. Please turn on JavaScript and try again.</div></noscript><div id="ctl00_ctl03" style="color:White;border-color:White;border-width:0px;border-style:Solid;text-align:center;"></div><div class="ms-clear"></div></div>
<div data-name="TopNavigationNoFlyoutWithStartNode"><span style="display:none">
<table cellpadding="4" cellspacing="0" style="font:messagebox;color:buttontext;background-color:buttonface;border: solid 1px;border-top-color:buttonhighlight;border-left-color:buttonhighlight;border-bottom-color:buttonshadow;border-right-color:buttonshadow">
<tr>
<td nowrap="nowrap">
<span style="font-weight:bold">PortalSiteMapDataSource</span> - topSiteMap</td>
</tr>
<tr>
<td></td>
</tr>
</table>
</span><a name="startNavigation"></a>
<div id="zz7_TopNavigationMenu" class=" noindex ms-core-listMenu-verticalBox">
<ul id="zz9_RootAspMenu" class="root ms-core-listMenu-root static">
<li class="static">
<a class="static menu-item ms-core-listMenu-item ms-displayInline ms-navedit-linkNode" href="/sites/Committees/SitePages/Home.aspx" accesskey="1">
<span class="additional-background ms-navedit-flyoutArrow">
<span class="menu-item-text">Committees</span></span></a></li>
<li class="static ms-verticalAlignTop ms-listMenu-editLink ms-navedit-editArea">
<span class="ms-navedit-editSpan" id="zz7_TopNavigationMenu_NavMenu_Edit">
<a id="zz7_TopNavigationMenu_NavMenu_EditLinks" class="ms-navedit-editLinksText" href="#" onclick="g_QuickLaunchMenu = null; EnsureScriptParams('quicklaunch.js', 'QuickLaunchInitEditMode', 'zz7_TopNavigationMenu', 1, 0, 1, '\u002fSITES\u002fCOMMITTEES'); cancelDefault(event); return false;" title="Edit Links">
<span class="ms-displayInlineBlock">
<span class="ms-navedit-editLinksIconWrapper ms-verticalAlignMiddle">
<img class="ms-navedit-editLinksIcon" src="/sites/Committees/_catalogs/theme/Themed/EF0ED6F1/spcommon-B35BB0A9.themedpng?ctag=55" alt="Edit Links" /></span><span class="ms-metadata ms-verticalAlignMiddle">Edit Links</span></span></a><span id="zz7_TopNavigationMenu_NavMenu_Loading" class="ms-navedit-menuLoading ms-hide"><a id="zz7_TopNavigationMenu_NavMenu_GearsLink" href="#" onclick="HideGears(); return false;" title="This animation indicates the operation is in progress. Click to remove this animated image."><img id="zz7_TopNavigationMenu_NavMenu_GearsImage" src="/_layouts/15/images/loadingcirclests16.gif?rev=38" alt="This animation indicates the operation is in progress. Click to remove this animated image." /></a></span><div id="zz7_TopNavigationMenu_NavMenu_ErrorMsg" class="ms-navedit-errorMsg">
</div>
</span></li>
</ul>
</div>

</div>
<br>
</td>
</tr>
<tr>
<td style="width: 312px">
<div class="DefaultContentBlock" style="border:medium black solid; background:yellow; color:black;">
This area will be filled in by content you create in your page layouts.
</div>
</td>
</tr>
<tr>
<td style="width: 312px; background:#CCCCCC"><div class="ms-webpart-chrome ms-webpart-chrome-fullWidth "><div WebPartID="00000000-0000-0000-0000-000000000000" HasPers="true" id="WebPart" width="312px" class="ms-WPBody noindex " OnlyForMePart="true" allowDelete="false" style=""><div class="ms-rtestate-field"></div></div></div></td>
</tr>
</table>
</div>
</div>
</body>
</html>
User agent strings for mobile Channel
Apple-iPhone3C1/1001.403
Apple-iPhone3C3/1001.403
Apple-iPhone4C1/1001.403
Apple-iPhone5C1/1001.405
Apple-iPhone5C2/1001.405
Apple-iPhone2C1/1001.523

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

Delete Master Page?

Similar Messages

Maybe you are looking for