In my case the error that’s going on here is that the page layout is not referenced as a relative url and is actually referencing the old server. To fix this issue we just need to loop through each SPWeb and update the page layouts to be relative. A little over a year ago I found a blog post online that had the solution by a very smart man who wrote a command line program to solve the issue. I am unable to find his post online today, so I decided to post my version of the code that I’ve updated to be used in a web part. I’ve compiled this code into a web part and whenever I run into the “Value does not fall within the expected range” error, I drop the web part on the home page, let it run and then delete the part off the page. 99% of time it works every time

Use this code at your own risk and I take no responsibility for anything bad that happens.

using System;
using System.Text;
using System.ComponentModel;
using System.Collections.Generic;
using System.Security.Permissions;

using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.Design.WebControls;

using Microsoft.SharePoint;
using Microsoft.SharePoint.Utilities;
using Microsoft.SharePoint.Security;
using Microsoft.SharePoint.Publishing;

namespace ScaredPanda
{
public class FixLayoutUrls : System.Web.UI.WebControls.WebParts.WebPart
{

protected override void CreateChildControls()
{
SPSecurity.CodeToRunElevated ElevatedCode = new SPSecurity.CodeToRunElevated(CodeToRunElevated);
SPSecurity.RunWithElevatedPrivileges(ElevatedCode);

base.CreateChildControls();
}

protected void CodeToRunElevated()
{
try
{
using (SPSite oSite = new SPSite(SPContext.Current.Web.Url))
{
Context.Response.Write(oSite.RootWeb.Url);
FixPages(oSite.RootWeb);
}
}
catch (Exception ex)
{}
}

private void FixPages(SPWeb oWeb)
{
try
{
if (!PublishingWeb.IsPublishingWeb(oWeb)) return;

PublishingWeb pw = PublishingWeb.GetPublishingWeb(oWeb);
SPListItemCollection oList = pw.PagesList.Items;

string sSiteUrl = oWeb.Site.Url;
oWeb.AllowUnsafeUpdates = true;
this.Context.Response.Write(“Processing ” + oWeb.Title + “(” + oList.Count.ToString() + ” pages)…<br>”);

foreach (SPListItem oPageItem in oList)
{
string s = (string)oPageItem[FieldId.PageLayout];
if (s != null && !s.StartsWith(sSiteUrl))
{
this.Context.Response.Write(“Fixing ” + oPageItem.Title + ” (” + oPageItem.Url + “)<br>”);
oPageItem[FieldId.PageLayout] = sSiteUrl + s.Substring(s.IndexOf(“/”, 9));
oPageItem.SystemUpdate();
}
}

foreach (SPWeb oSubWeb in oWeb.Webs)
{
FixPages(oSubWeb);
oSubWeb.Dispose();
}
}

catch (Exception ex)
{
this.Context.Response.Write(“Layout fix failed at site: ” + oWeb.Title + “<br>”);
this.Context.Response.Write(ex);
}
}
}
}

Share

Save

In order to use this widget you must have Yahoo! Widgets installed on your system. Which you can download here. Once you have Yahoo! Widgets installed just download the CHIRP Radio Realtime Playlist Yahoo! Widget – version .1 and open it using Yahoo! Widgets. Simple as that.

Now please keep in mind that this is the first version and I will be updating the look/feel/functionality as the days go on. I just wanted to get this up and out there as soon as possible. Drop me a line if you find any bugs or have any comments.

UPDATE: I removed the big CHRIP icon with a smaller icon so that there is no longer a “L” shape to the widget. Being that I wanted to have some type of identifier as to what the widget was, I put the little CHIRP bird icon on the right end of the now playing box.

Download: CHIRP Radio Realtime Playlist Yahoo! Widget – version .1.1

Here is some background about CHIRP Radio:

CHIRP Radio is a non-profit, volunteer-run, music-, arts-, and culture-focused radio station transmitting live from our studios in Chicago’s North Center neighborhood from 6AM-3AM seven days a week, 365 days a year.

CHIRP Radio hosts curate their own shows within certain guidelines, playing an eclectic mix of independent and under-heard music from an array of genres and eras. Listeners are encouraged to make requests and generally interact with CHIRP Radio hosts via comment, IM, or phone.

For now, CHIRP Radio is a web-only outlet, but the Chicago Independent Radio Project is working to change the law at the federal level to open up new licenses in urban areas, and hopes one day to be able to apply for a low-power FM broadcast license as well. To find out more about this work, visit chicagoindieradio.org.

CHIRP Radio does not air commercials, and receives no funding from corporations or the federal government. It is supported by special event revenues, small grants, and listeners like you. If you like what you hear, please consider making a donation to support this service.

Share

Save

Looking around the internet I’ve seen that many people have been trying to implement URL rewriting in a MOSS environment. Ive implemented url redirecting with MOSS using the HTTP module route for a while now and I’ve documented the code I used and what parameters worked the best for me here;

Take a look and let me know if this helps you and if you have any questions.

After messing around for a little bit it, I came up with a good way to do it. When I was looking for examples on the web there were a lot of people saying that it couldn’t be done. But in the end it actually didn’t take much to implement it. Here’s an HttpModule that I wrote to do the work.

The key pieces are the this.app.BeginRequest += new EventHandler(app_BeginRequest) which steps in front of the request and allows the module to get its redirect on. And HttpContext.Current.RewritePath(redirect, false); will push the necessary headers n such forward so that the receiving .aspx page will understand how to correctly post back.

using System;
using System.Data;
using System.Data.SqlClient;
using System.Reflection;
using System.Collections;
using System.Text;
using System.Web;
using System.Web.Caching;
using System.Web.SessionState;
using System.Security.Cryptography;
using System.Configuration;
using System.Threading;
using System.IO;
using System.Security;
using System.Security.Principal;

//if you do a HttpContext.Current.RewritePath without the 'false' parameter,
//the receiving sharepoint page will not handle post backs correctly
//this is extremely useful in situations where users/admins will be doing a
//'site actions' event
HttpContext.Current.RewritePath(redirect, false);
}
}
catch (Exception ex)
{
//rubbish
}
}
}
}

Share

Save