First Solution (extreme solution):
The first solution I have found in sharepoint forum. The solution is to comment out the section in master page which shows the message. As per the solution, find the following section in master page and comment it out.<div id="s4-statusbarcontainer"> <div id="pageStatusBar" class="s4-status-s1"> </div> </div>
So the solution in this case to hide div permanently from the master page. But the problem here might be that if the same div is used to show another useful message then user will not find the message.
Second Solution (soft solution):
Another solution might be not to remove the div from master page. Rather to hide/show the message on the client side on page load. Remember the default master page is V4.master, so in case of default master page, use V4.master instead of Default.master. The logic is:- set the div’s visibility to ‘none’ as shown below. So the div is not visible by default.
<div id="s4-statusbarcontainer" style="display:none"> <div id="pageStatusBar" class="s4-status-s1"> </div> </div>
- Run a script on page load which will check the message inside the div. And based on the message the div will be visible or not. I have put the following script in the master page’s head section. The script check if the display message is not ‘The current page has been customized..’ and if not so then display the message:
<head> ........................... <script type="text/javascript"> ExecuteOrDelayUntilScriptLoaded(hideWarning, "sp.js"); function hideWarning() { var statusbarContainer = document.getElementById('s4-statusbarcontainer'); if (statusbarContainer != null) { var messageSpan = document.getElementById('status_1_body'); if (messageSpan != null) { if (messageSpan.innerHTML.indexOf('The current page has been customized from its template.') == -1) statusbarContainer.style.display = 'inline'; } } } </script> </head>
In the above code snippet, the method ‘ExecuteOrDelayUntilScriptLoaded’ ensures that the method hideWarning is not invoked until the base SharePoint JavaScript file sp.js is loaded.
My final judgment is that SharePoint should provide a settings from site collection/web level to enable/disable the warning. sometimes admin wants to accept the warning but don’t want to show it to end users. Hope some SharePoint team will heed into this. Till that day we, sharepoint developer, need to find a way out. Hope someone out there will get a better idea.
Hmmm...very buggy. What is really odd is that if you make the change several times in Designer and then click on 'Revert to Template', it will eventually keep the new change yet the Revert to Template message will go away. Not exactly smooth - but my work saved and annoying message is gone! :)
ReplyDeleteIn your case the changes were kept intact but in some cases the changes are reverted. So you can't predict if the changes will be kept or not.
ReplyDeletePlease use brackets EVERYTIME after IF, otherwise it's bugs up ahead....
ReplyDeleteSecond Solution works great on our SharePoint Enterprise sandbox.
ReplyDeleteThanks Sohel!!!
Thank you veeery much!
ReplyDeleteAnother alternative is to use the SharePoint:SPSecurityTrimmedControl class and its Permissions attribute arround the pageStatusBar div tag.
ReplyDeleteNice.. I had to make some changes to make it work for me, though. I used "sp.ribbon.js" instead of "sp.js" and I changed the messageSpan.innerHTML.indexOf conditional around and added "display: none;" instead of inline.
ReplyDeleteFor some reason, it wouldn't work properly the original way.
ExecuteOrDelayUntilScriptLoaded(hideWarning, "sp.ribbon.js");
function hideWarning() {
var statusbarContainer = document.getElementById('s4-statusbarcontainer');
if (statusbarContainer != null) {
var messageSpan = document.getElementById('status_1_body');
if (messageSpan != null) {
if (messageSpan.innerHTML.indexOf('The current page has been customized from its template.') !== -1){
statusbarContainer.style.display = 'none';
}
}
}
}
Your solution solved my problem while the first solution didn't
Deletethank you
This worked for me without messing with the master page:
ReplyDeleteExecuteOrDelayUntilScriptLoaded(hideWarning, "sp.js");
function hideWarning() {
var statusbarContainer = document.getElementById('s4-statusbarcontainer');
if (statusbarContainer != null) {
var messageSpan = document.getElementById('status_1_body');
if (messageSpan != null) {
if (messageSpan.innerHTML.indexOf('The current page has been customized from its template.') != -1)
statusbarContainer.style.display = 'none';
}
}
}
Thankx Sohel & RamGen, I just pasted above script snippet in my custom .js & it started working :)
ReplyDeleteThank you so much! The first solution worked for me!
ReplyDeleteI see that some things haven't changed (namely SharePoint 2013)
ReplyDeleteI didn't like the idea of hiding the Status Alert either. Specially if the pages need check in and check out you wouldn't be able to see this.
This doesn't resolve the template thing or nor does it hide it but pushes it to the bottom of the page.
This is not complete and may not be 100% compatible but I've spent enough time on this today...
I've left the colors in the divs so you can see the wizardry I was trying out.
I added a Script Editor web part then added this;
[style type="text/css"]
#contentBox { display: flex; flex-direction: column; background-color:grey; border:black solid 1px;}
#contentBox > #DeltaPageStatusBar { order: 2; background-color:silver;}
#contentBox > #DeltaPlaceHolderMain { order: 1; background-color:yellow;}
#DeltaFormDigest {background-color:red;}
[/style]
I haven't tested the compatibility and support of FLEX as a CSS but https://css-tricks.com/using-flexbox/ seems to cover the other browsers.
Some notable links;
http://jsfiddle.net/hqya7q6o/
http://jsfiddle.net/2fcj8s9e/
http://tanalin.com/en/articles/css-block-order/
replace [] with <>
Delete