Ok, so you have developed your funky new SharePoint master page and new personal site template. You have set up all the permissions in the SSP to allow users to edit their own profiles and take the headache away from you.

But...

When a user clicks on Edit on the user display page they only see their network account listed. How do you fix it?

First, its nothing you did wrong with permissions or settings. Its down to the way that WSS and MOSS co-exist on the machine.

The resolution is really simple:

• navigate to the 12\templates\layouts hive
• rename the useredit.aspx file to useredit.old.aspx
• copy the editprofile.aspx file and rename the copy to useredit.aspx
  

Your users will now have a fully functioning profile editing page.

What is the CRMSandpit?

   <div id="Container">
      <div id="LeftNav">...</div>
      <div id="Content">...</div>
      <div id="LeftFooter">...</div>
   </div>

#Container
{
   height: auto;
   width: 150em;
   margin: auto;
   clear: both;
   position: relative; /* you will see the importance of this shortly*/
}
#LeftNav
{
   width: 35em;
   float: left;
}
#Content
{
   width: 115em;
   float: right;
}
#LeftFooter
{
   position: absolute;
   left: 1em;
   bottom: 1em;
   width: 13em;
}

1. Check the page exists - if it doesn't server the error page.
2. Send the correct error code to the browser.

Check the page exists

   1:          protected void Application_BeginRequest(object sender, EventArgs e)

   2:          {

   3:              //get the url

   4:              string url = Request.RawUrl;

   5:              //check the document exists on the file system

   6:              if ((!System.IO.File.Exists(Server.MapPath(url))))

   7:              {

   8:                  //if the document does not exist serve the error page

   9:                  Server.Transfer("/Error/FileNotFound.aspx");

  10:              }

  11:          }

Send the correct error status

   1:          protected void Page_Load(object sender, EventArgs e)

   2:          {

   3:              Response.StatusCode = 404;

   4:              Response.Status = "404 Not Found";

   5:   

   6:          }