Useful SharePoint toolkit to generate custom code

Came across this really nice online toolkit.

http://usermanagedsolutions.com/SharePoint-User-Toolkit/default.aspx

Nice tool that can generate code for a CEWP to bring back data from another site in the collection for display.

Filter on SharePoint list

Colleague of mine sent me this code that was on the Internet to filter lists.  Simply place it into a CEWP.

Very Handy but it won't work when you have Counts and Totals on the list.

<script src="http://www.google.com/jsapi"></script>

<script>


google.load("jquery", "1.2.6");

google.setOnLoadCallback(function() {

$(document).ready(function()
{
jQuery.extend(jQuery.expr[':'], {
  containsIgnoreCase: "(a.textContent||a.innerText||jQuery(a).text()||'').toLowerCase().indexOf((m[3]||'').toLowerCase())>=0"
});


$("table.ms-listviewtable tr.ms-viewheadertr").each(function()
{
if($("td.ms-vh-group", this).size() > 0)
{
return;
}

var tdset = "";

var colIndex = 0;

$(this).children("th,td").each(function()
{
if($(this).hasClass("ms-vh-icon"))
{
// attachment
tdset += "<td></td>";
}
else
{
// filterable
tdset += "<td><input type='text' class='vossers-filterfield' filtercolindex='" + colIndex + "' /></td>";
}

colIndex++;
});

var tr = "<tr class='vossers-filterrow'>" + tdset + "</tr>";

$(tr).insertAfter(this);
});


$("input.vossers-filterfield")
.css("border", "1px solid #7f9db9")
.css("width", "100%")
.css("margin", "2px")
.css("padding", "2px")
.keyup(function()
{
var inputClosure = this;

if(window.VossersFilterTimeoutHandle)
{
clearTimeout(window.VossersFilterTimeoutHandle);
}

window.VossersFilterTimeoutHandle = setTimeout(function()
{
var filterValues = new Array();

$("input.vossers-filterfield", $(inputClosure).parents("tr:first")).each(function()
{
if($(this).val() != "")
{
filterValues[$(this).attr("filtercolindex")] = $(this).val();
}
});


$(inputClosure).parents("tr.vossers-filterrow").nextAll("tr").each(function()
{
var mismatch = false;

$(this).children("td").each(function(colIndex)
{
if(mismatch) return;

if(filterValues[colIndex])
{
var val = filterValues[colIndex];

// replace double quote character with 2 instances of itself
val = val.replace(/"/g, String.fromCharCode(34) + String.fromCharCode(34));

if($(this).is(":not(:containsIgnoreCase('" + val + "'))"))
{
mismatch = true;
}
}
});

if(mismatch)
{
$(this).hide();
}
else
{
$(this).show();
}
});

}, 250);
});
});

});

</script>

Serious gotcha for SharePoint 2007 large site deletion

While trying to delete a large SharePoint site as part of an internal migration of data.  Ran into severe problems.

SharePoint 2007 seemed unable to handle deletion of sites where there is greater than 25 Gig of data with lists that had thousands of items say 30,000 +

Perhaps this is the real reason why they warn people of having lists greater than 10,000 items.  Even though the site's performance its OK, you have problems removing them.

You will find even an stsadm statement like the following won't work. Yes, even if you code in the WebID

stsadm -o deleteweb  -force -webid ea949749-8f81-40b0-8c76-0cfc37c62d7d -databasename WSS_Content_XYZ -databaseserver XYZ_UAT\SQLSERVER2008 

Then even if you delete the libraries first.  You will find it cannot be emptied easily from the second layer recycle bin.  Everytime you try to empty a large list the whole site collection gets locked out and effectively knocking the whole site out of action.  This is a bad flaw with the product from an admin perspective.  MS recommends getting a powerful server to do the business but that's simply not possible in some business scenarios. Especially if one goes by the rule that you want to test first on a Test Server before running it on a live server.  Most Test Servers are not spec particularly hot.  

Therefore, you can never test properly whether a deletion would work.

What we found eventually worked was if we went into the recycle bin and emptied each of the libraries individually one at the time.  Each time locking out 

the site for a long period of time.  Eventually all the big libraries got cleared and the site was able to be deleted.

Basically with this feature, you must schedule in long downtimes for large site deletion.  Not good for any Live site.

Well and surely Konged by it.

Having to Restart WebClient Service from CMD Line for WebDav location in SharePoint to work

This continues to baffle us.  A section of our users require the WebDav protocol to work when browsing to a SharePoint location.

For example on Run \\xyz.com\it\shared documents\

They expect it to open a the location and not prompt for user name and password and when it opens in Window Explorer they should see \\xyz.com\it\shared 

documents\ in the address bar rather than http://xyz.com/it/shared documents/ 

It turns out, users must first have the hostname of xyz.com set into IE's Intranet zone as the browser settings has influence over Windows Explorer when opening WebDav locations.

Then one must have the WebClient Service running in order for it to work properly else it tends to open in http: protocol.

Now here is what got us.  Sometimes even if WebDave service reports running.  It is necessary for some strange reason to restart it.

It is mainly either because the service has :

-Cached something based on the local admin's credentials therefore causing a prompt to appear.
-It has actually somehow not started properly because the service has a dependency on the MRXDAV services.

Therefore, what we must do is simply in the command line and run these 4 commands in the order below.  Has to be done on command line.

NET STOP WEBCLIENT 
NET STOP MRXDAV 
NET START WEBCLIENT 
NET START MRXDAV


Then try opening a location in the Run again and it should start to work.

This KONGED us for a while.

On a Win 7, Vista machine it seemed like the order for restarting the webclient has changed.

NET STOP MRXDAV  - This will then prompt WebClient to be stopped.  Click Y
NET START MRXDAV
NET START WEBCLIENT

Also, when we try to locate a WebDAV location that is in SharePoint, the prompt will continue to appear even if it is inserted into Intranet zone.  We found that we must have this registry key set and then restart WebClient for the authentication pass through to work.

See here

http://support.microsoft.com/kb/941050/en-us

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameters\AuthForwardServerList

Rather neat tool to move large discussion boards etc between SharePoint sites

Was confronted with a problem with moving large discussion boards and email enabled library with thousands of .emls inside between site from a Site Admin perspective when:

-It was not possible to do with Content Structure Manager.
-Dicussion board was too big to save as a list template.
-SharePoint Designer won't play ball and won't let you copt the items.
-Windows Explorer view won't work.

Then it seemed like one must use stsadm functions.  stsadm -o export -url "http://mysites.com/list/etc" -filename list.exp

However, was brought to attention of a really cool tool that someone has developed,

http://spdeploymentwizard.codeplex.com/ 
http://www.sharepointnutsandbolts.com/2007/12/introducing-sharepoint-content.html

Tool must be installed on WFE Server though.  But it generates export files that can then be imported into target site.  Really nice interface and saves tinkering with stsadm.  Works well.

Simple Style sheet css for IE to highlight an image button on mouseover

Looked up and found a simple css style to give a Mouse Over effect on all image button links.  Can be used with CEWP in SharePoint quite a lot.


<STYLE type=text/css>.highlightit IMG {
 FILTER: progid:DXImageTransform.Microsoft.Alpha(opacity=100); opacity: 1; -moz-opacity: 1
}
.highlightit:hover IMG {
 FILTER: progid:DXImageTransform.Microsoft.Alpha(opacity=40); opacity: 0.3; -moz-opacity: 0.3
}
</STYLE>


<td align=left valign=middle><a href="Pipeline.aspx" class="highlightit" title="Our Pipeline"><img src="Resources/CurrentYearPipeline.png" style="border:none;width:130px" alt="Our Pipeline" /></a></td>

Use of App Offline Page for SharePoint Web Application

To make this feature work, you have to place the app_offline.htm file in the rootof the application. When ASP.NET sees it, it will shut-down the app-domain for the application (and not restart it for requests) and instead send back the contents of the app_offline.htm file in response to all new dynamic requests for the application. 

example :

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" >
<head>
    <title>Application Offline</title>
</head>
<style>

div {
    background-color:#ffffcc;
    padding-top:10px;
    padding-bottom:10px;
    padding-left:10px;
    padding-right:10px;
    border-style:solid;
    border-color:Black;
    border-width:1px;
    text-align:center;
}

</style>
<body>
    <div>
    Information from IT.  This SharePoint application is currently offline due to Maintenance activities.  It will be available soon around 1pm HKT.  Thank you for your patience.
    </div>
</body>
</html>