Microsoft Tech Blogs : Sharepoint 2007

RSS viewer webpart Proxy setting and BYPASSLIST

ketaanhs — Mon, 21 Dec 2009 18:29:00 GMT

In SharePoint 2007 (MOSS) we have a RSS viewer webpart and by now most of us know that we need a proxy enabled in the web.config file to have the RSS web part pull those feeds, but adding the proxy setting might block few other things, like in case if you are using FAST search and have the connector and Search results are fetched thru the web service the Fast results will stop from appearing (as the Fast server might be blocked @ the proxy server).

We have 2 solutions to it, enable it @ the Proxy Server level so that Fast Search queries will work or add the Fast Server address to the byPassList element in the web.config file

http://msdn.microsoft.com/en-us/library/aa903323(VS.71).aspx

Sample:

<configuration>

   <system.net>

      <defaultProxy>

         <bypasslist>

            <add address="[a-z]+\.contoso\.com" />

            <add address="192\.168\..*" />

         </bypasslist>

      </defaultProxy>

   </system.net>

</configuration>

Shared SSP and Web-application creation in Sharepoint 2007 (Alternate URL Synchronizer)

ketaanhs — Sat, 12 Sep 2009 16:11:00 GMT

At one of my customers we have a situation where we are Sharing the SSP from one Farm (i.e. Parent Farm) to another Farm (Child Farm). We also need to create a web-application with the same host header name (e.g. http://secure.msft.com) in both the Farms.

Following is the main crux of the issue:

1. We have a Parent Farm (This farm provides the SSP to child Farms), lets call this Farm ASIAFARM.

2. We create a web-app with url “secure.msft.com“ in the ASIAFARM, and the web-app is created.

3. Now we create the AAM entries for this web-app in the Parent farm (3 entries).

4. We now go to the Child Farm (This farm consumes the SSP provided by the Parent Farm), lets call this Farm USFARM.

5. We try creating a web-app with the same url i.e. “secure.msft.com“ in the USFARM and the web-app creation fails with the error: http://secure.msft.com is already routed to the Default zone of another application. Remove that mapping or use a different URL.

6. This is because of the reason that “Alternate URL Synchronizer” timer job syncs all the entries from the Parent Farm to the Child Farm and hence can’t create the web-app.

7. Then we disabled this (“Alternate URL Synchronizer” ) timer job in the Child Farm and deleted all the AAM entries from the Child Farm.

8. Then we tried creating a web-app with the same url i.e. “secure.msft.com“ in the USFARM and it succeeded. And we were able to create the additional AAM entries.

So bottom line is the (“Alternate URL Synchronizer” ) timer job Synchs the information (AAM) from Parent Farm into the Child Farms. If you want to take a look at the EXECUTE method of this timer job (using Reflector), just open the Assembly name: Microsoft.Office.Sharepoint.Administration

Class Name: AlternateUrlSynchronizerJob [This is basically a SEALED class).

After looking @ the source code of this TIMER JOB we found that it only writes the AAM (Alternate Access Mapping) from the Parent Farm to Child Farm, so now if you try to create a web-application with a host header that is already created in Parent Farm it will not be successful and it will not allow you to create a web-application in Child Farm with that host header. [PLEASE NOTE: This scenario only happens when you are sharing the SSP (Shared Service Provider) with two farms i.e. Child Farm uses SSP of Parent Farm, and that creates this Alternate URL Synchronizer Timer Job).

So be cautious (while architecting) when you propose this approach, as you will not be able to create a web-app with same host headers. I am still to find the answer for where all these AAMs are use (my *guess* is Search might be using it, dont what else would be using it).

As disabling this Timer Job (thru Central Admin-->Operations-->Timer Job Definition-->Disable) you will be able to create the web-apps requied in both the farms but not sure if you would be in a supported state, as we are still not aware of where all the AAMs are used.

"This week in Pictures" web part in Sharepoint 2007 and Time Interval

ketaanhs — Thu, 13 Aug 2009 03:34:00 GMT

In case if you are looking for how to set the time interval between image slideshow, you will find this blog helpful.

The “This week in Pictures” [TWIP] web part uses a java script for the slideshow (STARTSlideShow() method).

Basically in the OnPreRender() method (TWIP) web part from Microsoft.SharePoint.Portal.WebControls.ThisWeekInPicturesWebPart registers the client script

This refers to the JAVA script file (IMGLIB.js) in the layouts/1033 (or lang specific folder), that has a StartSlideShow()method that uses the timerId=setTimeout("AutoRun()", slideshowInterval); and slideshowInterval is set to 5000 (milli seconds), I changed this value to 2000 and it works for me (But I am sure we don’t want to do it this way J).

But we can override the StartSlideShow() method then we can change it the way we want J.

<UPDATE 13th Aug 2009>

Mak Rowshan (my buddy) just updated me that he was able to add the following script to SlideShow.aspx, and it modified the time interval for slideshow.

</script>

Exploring the Microsoft.Office.Server.Administration.Licensing information

ketaanhs — Wed, 12 Aug 2009 19:32:00 GMT

Have you ever had a need to explore whats the expiration date of the trial version of MOSS you are using, if yes then the solution for that is the INTERNAL STATIC CLASS: Microsoft.Office.Server.Administration.Licensing This will help you in finding out what is the expiration date and other details about licensing, check the Fiddler screen shot below for some details.

http://www.flickr.com/photos/43203883@N00/3815256542/sizes/o/

How to determine (find) who created a site on a MOSS 2007

ketaanhs — Wed, 08 Jul 2009 21:44:00 GMT

One of my colleague had asked query regarding how to find out the user who created the site in sharepoint 2007, obviously nothing in the UI to find out that. So we will have to do it programmatically and the way to get it is to use the SPWeb.Authors property. More details here: http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spweb.author.aspx

In case if someone wants to find out who created the site and not the owner of the site then a small console application can be written that uses the SPWeb.Authors property and running this console applicaiton on one of the sharepoint WFEs in the farm.

Modifying SPThemes.xml Programmatically to deploy new Themes MOSS 2007 (WSS 3.0)

ketaanhs — Wed, 01 Jul 2009 17:37:00 GMT

Modifying SPThemes.xml Programmatically to deploy new Themes MOSS 2007 (WSS 3.0)

One of my colleague was looking for modifying the SPThemes.xml file programmatically instead of editing it manually on each and every server. So that the deployment of new themes could be very easy thru the Solution Deployment/Packaging way. All we need is a Feature Receiver for that. In case if you have not already seen the VSEwss 1.3 here check it out, there is a ready made codebehind available that be reused to deploy your custom Themes in sharepoint 2007 (wss 3.0) using the feature / Solution deployment packaging approach. Following is the source code from the Feature receiver from the VSeWSS project (http://www.microsoft.com/downloads/details.aspx?FamilyID=0A87658F-20B8-4DCC-AD7A-09AD22641F3A&displaylang=en)

NOTE: These 10 Theme Features are FARM LEVEL Features and you can find these Features in the Central Admin box under the Operation tab under Farm level Features:

//--------------------------------------------------------------------------------
// This file is a "Sample" as part of the MICROSOFT SDK SAMPLES FOR SHAREPOINT
// PRODUCTS AND TECHNOLOGIES
//
// (c) 2008 Microsoft Corporation. All rights reserved.
//
// This source code is intended only as a supplement to Microsoft
// Development Tools and/or on-line documentation. See these other
// materials for detailed information regarding Microsoft code samples.
//
// THIS CODE AND INFORMATION ARE PROVIDED AS IS WITHOUT WARRANTY OF ANY
// KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
// IMPLIED WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A
// PARTICULAR PURPOSE.
//--------------------------------------------------------------------------------

using System;
using System.Collections.Generic;
using System.Text;

using Microsoft.SharePoint;
using Microsoft.SharePoint.Utilities;
using System.IO;
using System.Linq;
using System.Xml.Linq;

namespace TeamSiteTheme
{
    public class TeamSiteThemeFeatureReceiver : SPFeatureReceiver
    {
        private const string _themeName = "TEAM";
        private const string _themeNiceName = "Team";

        private enum ModificationType
        {
            Add,
            Remove
        }

        public override void FeatureActivated(SPFeatureReceiverProperties properties)
        {
            ModifySPTheme(ModificationType.Add);

            using (SPWeb web = (SPWeb)properties.Feature.Parent)
            {
                web.ApplyTheme(_themeName);
            }
        }

        public override void FeatureDeactivating(SPFeatureReceiverProperties properties)
        {
            ModifySPTheme(ModificationType.Remove);

            using (SPWeb web = (SPWeb)properties.Feature.Parent)
            {
                web.ApplyTheme("none");
            }

}

        public override void FeatureInstalled(SPFeatureReceiverProperties properties)
        {
            ModifySPTheme(ModificationType.Add);
        }

        public override void FeatureUninstalling(SPFeatureReceiverProperties properties)
        {
            ModifySPTheme(ModificationType.Remove);
        }

        private void ModifySPTheme(ModificationType type)
        {
            XDocument doc = null;
            XNamespace ns = "http://tempuri.org/SPThemes.xsd";

            // path to the SPTHEMES.XML file
            string spthemePath = Path.Combine(SPUtility.GetGenericSetupPath(@"TEMPLATE\LAYOUTS\1033"), "SPTHEMES.XML");
            string contents = string.Empty;

            // read the contents of the SPTHEMES.XML file
            using (StreamReader streamReader = new StreamReader(spthemePath))
            {
                contents = streamReader.ReadToEnd();
                streamReader.Close();
            }

            using (StringReader stringReader = new StringReader(contents.Trim()))
            {
                // create a new XDocument from the contents of the file
                doc = XDocument.Load(stringReader);

                // retrieve all elements with a TemplateID of our theme. At most, there should only be one
                var element = from b in doc.Element(ns + "SPThemes").Elements(ns + "Templates")
                              where b.Element(ns + "TemplateID").Value == _themeName
                              select b;

bool exists = (element != null && element.Count() > 0);

                if (type == ModificationType.Add)
                {
                    if (!exists)
                    {
                        // create an XElement that defines our custom theme
                        XElement xml =
                            new XElement(ns + "Templates",
                                new XElement(ns + "TemplateID", _themeName),
                                new XElement(ns + "DisplayName", string.Format("{0} Site Theme", _themeNiceName)),
                                new XElement(ns + "Description", string.Format("A {0}-like Site Theme", _themeNiceName)),
                                new XElement(ns + "Thumbnail", string.Format("1033/IMAGES/{0}/preview.jpg", _themeName)),
                                new XElement(ns + "Preview", string.Format("1033/IMAGES/{0}/preview.jpg", _themeName)));

                        // add the element to the file and save
                        doc.Element(ns + "SPThemes").Add(xml);
                        doc.Save(spthemePath);
                    }
                }
                else
                {
                    if (exists)
                    {
                        // if the element exists, remove it and save
                        element.Remove();
                        doc.Save(spthemePath);
                    }
                }

                stringReader.Close();
            }
        }

}
}

Audiences in Inter Farm SSP (Sharepoint 2007 / MOSS)

ketaanhs — Wed, 24 Jun 2009 18:19:00 GMT

We were doing some brain storming on Sharing the SSP (Shared Service Provider) between multiple farms i.e. the Parent Farm will be the provider/source of the SSP and the Child farm will consume the SSP. (Needless to say this is MOSS or sharepoint 2007).

It is very easy to set up the sharing of the SSP between farms basically going to the Central Administration àApplication ManagementàUnder office Shared Service provider (Grant or configure shared services between farms ) and here you can configure whether the current farm on which CA is hosted for that farm will be a consumer or provider of the SSP.

Ok so now we wanted to keep the Audiences in one place i.e. in the Parent farm and share these Audiences between the Parent and the Child farm. The question came in what would happen if the Parent farm is down for maintenance i.e. Service Pack upgrades, etc. What would happen to Audience targeting that is done on some of the content pages on the Child farm sites? Will it work or will it not? Will the Audiences resolve or not. So we did a quick small POC and following were our findings on that:

Case 1: All WFE’s and CA box from the Parent farm is down but not the SQL box from the parent farm: Audience still works (as Parent SQL box is still up and running).

Case 2: The entire farm is down (all WFEs, CA box) along with the Parent farm SQL Box: The audiences don’t work as expected.

So bottom line is the Child farm talks directly to the SQL box of the parent farm (i.e. the SSP db of the parent farm) and it is independent of any services on the WFE/CA box of the Parent farm.

Thank you to Ben Risher our in-house MOSS Infra Guru for guiding and helping me thru this. We worked together on this and got this to a conclusion.

Programmatically provision hostheader site collection (MOSS/Sharepoint 2007)

ketaanhs — Wed, 06 May 2009 06:09:00 GMT

I was looking for a sample on creating a Host header based site collection (programmatically) i.e. using WSS/Sharepoint 2007 API and came across the msdn article, but there is no sample: http://msdn.microsoft.com/en-us/library/ms479602.aspx

We can easily do it thru STSADM:

stsadm -o createsite -url http://THE-HOST-HEADER-FOR-THE-SITE-COLLECTION -ownerlogin DOMAIN\username -owneremail username@domain.com -hhurl http://THE-URL-OF-THE-WEBAPPLICATION-THE-SITE-COLLECTION-IS-GOING-INTO

But then I got the sample, thanks again to TROY STARR he is a great help, thought of sharing this with a larger community in case if someone wants to do it:

SPWebApplication webApp = SPWebApplication.Lookup(new Uri("http://the-url-of-the-webapplication-the-site-collection-is-going-into"));

webApp.Sites.Add(

"http://the-host-header-for-the-site-collection", // site URL

"The Site Title", // site title

"The Site Description", // site description

1033, // site LCID that represents the language, e.g. 1033 = en-US

"STS#0", // site template, e.g. STS#0 = Team Site

@"DOMAIN\username", // site owner login

"Firstname Lastname", // site owner name

"username@domain.com", // site owner e-mail address

NULL, // secondary owner login

NULL, // secondary owner name

NULL, // secondary owner e-mail address

true); // is this a host-named site collection

Programmatically loop thru Publishing site collection or rather WARMP UP Script for FBA site

ketaanhs — Tue, 31 Mar 2009 20:26:00 GMT

I wanted to write a WARMP UP SCRIPT For FBA enabled Publishing site for Sharepoint 2007/ MOSS.

REQUIREMENT:

We have a web-application set up with FBA and we have some of the sites accessible anonymously and other for only authenticated users.

We would like to programmatically loop thru the entire site-collection, I am somehow not able to loop thru the site collection for the authenticated sites and I get access denied.

I am sure I am missing some simple step on creating a generic principal with Forms based authentication but not sure where and how I make sure that I can loop thru the site collection.

using System;

using System.Collections.Generic;

using System.Text;

using Microsoft.SharePoint;

using Microsoft.SharePoint.Publishing;

using System.Net;

using System.Web.Security;

namespace ConsoleApplication2

{

class Program

{

static void Main(string[] args)

{

//args[0]: This is the Site Collection url, e.g.: http://pub-staging.ABCD.com

//args[1]: This is web service URL for Authentication, e.g: http://pub-staging.ABCD.com/_vti_bin/Authentication.asmx

//args[2]: This is the username

//args[3]: This is the password

//string strSiteURL = "http://pub-staging.ABCD.com";

string strSiteURL = args[0];

System.Net.CookieContainer cookie;

bool blnStatus = FBAAuthenticate(out cookie,args[1],args[2],args[3]);

using (SPSite site = new SPSite(strSiteURL))

{

foreach (SPWeb web in site.AllWebs)

{

Console.WriteLine("***********************************************************");

Console.WriteLine(web.Url.ToString());

Console.WriteLine("***********************************************************");

//FormsAuthenticationTicket fbaTkt = new FormsAuthenticationTicket("fsegment10", true, 10);

if (PublishingWeb.IsPublishingWeb(web))

{

PublishingWeb publishingWeb = PublishingWeb.GetPublishingWeb(web);

PublishingPageCollection pageColl = publishingWeb.GetPublishingPages();

//Call the web service Authentication

foreach (SPListItem listItem in publishingWeb.PagesList.Items)

{

if (PublishingPage.IsPublishingPage(listItem))

{

PublishingPage page = PublishingPage.GetPublishingPage(listItem);

try

{

System.Net.HttpWebRequest req = (System.Net.HttpWebRequest)System.Net.HttpWebRequest.Create(page.Uri.ToString());

req.CookieContainer = cookie;

HttpWebResponse res = (HttpWebResponse)req.GetResponse();

using (System.IO.Stream str = res.GetResponseStream())

{

using (System.IO.StreamReader strReader = new System.IO.StreamReader(str))

{

Console.WriteLine(strReader.ReadToEnd());

strReader.Dispose();

}

catch (Exception ex)

{

}

/// <summary>

/// Sharepoint forms based authentication (FBA) web method call.

/// </summary>

/// <param name="cookieContainer">CookieContainer</param>

/// <param name="strSiteId">String</param>

/// <returns>Boolean</returns>

private static bool FBAAuthenticate(out System.Net.CookieContainer cookieContainer, string webServiceURL, string userName, string pwd)

{

bool blnStatus;

FBAPORTAL.Authentication auth = new FBAPORTAL.Authentication();

//auth.Url = "http://pub-staging.ABCD.com/_vti_bin/Authentication.asmx";

auth.Url = webServiceURL;

auth.CookieContainer = new System.Net.CookieContainer();

auth.AllowAutoRedirect = true;

//FBAPORTAL.LoginResult loginResult = auth.Login("fbaadminstaging", "fba1234");

FBAPORTAL.LoginResult loginResult = auth.Login(userName,pwd );

if (loginResult.ErrorCode == FBAPORTAL.LoginErrorCode.NoError)

{

blnStatus = true;

cookieContainer = auth.CookieContainer;

}

else

{

blnStatus = false;

cookieContainer = null;

}

return blnStatus;

}

MOSS / Sharepoint 2007 Custom Error Page and Access denied Page

ketaanhs — Mon, 16 Mar 2009 23:10:00 GMT

In case if you are interested in creating your own custom error page and custom access denied page instead of the out of the box MOSS / Sharepoint error page (generally the requirements in Publishing internet site). You can use the following HTTPModule (this is just a sample, you can change it to suit your requirements):

Note to have following Web.config Entries:

Following entries in the <appsettings> section in the web.config file:

Following entry is for a custom error page to be displayed for anonymous users, the key should be in the format: “CustomAnonCustErrPG-SiteCollectionURL” as shown below:

Following entry is for a custom error page to be displayed for authenticated users, the key should be in the format: “CustomAuthCustErrPG-SiteCollectionURL” as shown below:

Following entry is for a custom error page to be displayed for access denied errors, the key should be in the format: “CustomCustAcsDndPG -SiteCollectionURL” as shown below:

Create an entry on all the WFEs web-application specific web.config in the HTTPModules section, as follows just below the <HTTPModule> tag This should be the first entry in the HTTPModules section:

NOTE: Add your own Public key for PublicKeyToken per your snk used, replace the PUBLICKEYGUID with your own snk value

///////////////////////////////////////////////////////////////////////////////////////////////

// This is a HTTPModule used for redirecting the user to Home or Home Anon site depending on whether

// s/he is authenticated or anonymous.

// The module checks if the url is accessdenied.aspx and redirects the user to proper url.

////////////////////////////////////////////////////////////////////////////////////////////////

using System;

using System.Web;

using Microsoft.Practices.EnterpriseLibrary.ExceptionHandling;

using System.Configuration;

using Microsoft.SharePoint;

namespace XYZ.Sharepoint.HTTPModule.CustomErrorPages

{

public class CustomErrors : IHttpModule

{

#region -- Private fields --

private static AppSettingsReader m_Reader = new AppSettingsReader();

private static string m_SiteCollAnonCustomErrPG = "CustomAnonCustErrPG";

private static string m_SiteCollAuthCustomErrPG = "CustomAuthCustErrPG";

private static string m_SiteCollCustAcsDndPG = "CustomCustAcsDndPG";

#endregion

public void Init(HttpApplication context)

{

//Attaching event handlers for access denied and error respectively

//context.BeginRequest += new EventHandler(context_AcessDenied);

context.EndRequest += new EventHandler(context_AcessDenied);

context.Error += new EventHandler(context_Error);

}

void context_AcessDenied(object sender, EventArgs e)

{

try

{

HttpApplication httpApp = sender as HttpApplication;

HttpContext context = httpApp.Context;

string httpUrl = context.Request.Url.ToString();

string strCustomAcssDndURL = string.Empty;

string strSiteURL = string.Empty;

if (httpUrl.ToLower().Contains("/_layouts/accessdenied.aspx"))

{

SPSecurity.RunWithElevatedPrivileges(delegate()

{

using (SPSite site = new SPSite(httpUrl))

{

strSiteURL = site.Url;

}

});

HttpContext.Current.Server.ClearError();

HttpContext.Current.Response.Clear();

strCustomAcssDndURL = getAppSettingsValue(m_SiteCollCustAcsDndPG + "-" + strSiteURL);

HttpContext.Current.Response.Redirect(strCustomAcssDndURL, false);

}

catch (Exception ex)

{

//Do your exception handling

}

void context_Error(object sender, EventArgs e)

{

try

{

string strURL = string.Empty;

string strSiteURL = SPContext.Current.Site.Url;

Exception[] unhandledExceptions = HttpContext.Current.AllErrors;

//logging all the exceptions thru the Exception policy file

foreach (Exception ex in unhandledExceptions)

{

//Do your exception handling

}

HttpContext.Current.Server.ClearError();

HttpContext.Current.Response.Clear();

if (HttpContext.Current.User.Identity.IsAuthenticated)

{

strURL = getAppSettingsValue(m_SiteCollAuthCustomErrPG + "-" + strSiteURL);

HttpContext.Current.Response.Redirect(strURL, false);

}

else

{

strURL = getAppSettingsValue(m_SiteCollAnonCustomErrPG + "-" + strSiteURL);

HttpContext.Current.Response.Redirect(strURL, false);

}

catch (Exception ex)

{

//Do your exception handling

}

public void Dispose()

{

}

//Method used to read Appsettings value from web.config for the webapplication

private static string getAppSettingsValue(string sKey)

{

string sValue = null;

try

{

sValue = m_Reader.GetValue(sKey, typeof(string)) as string;

}

catch (Exception ex)

{

//Do your exception handling

}

return sValue;

}

Disable Event handlers during Content Deployment (Sharepoint 2007/MOSS)

ketaanhs — Thu, 12 Mar 2009 18:50:00 GMT

When we are doing a content deployment in a publishing site and there are lot of event handlers attached to list/libraries then be aware that by default content deployment tells PRIME not to fire events during import. You can change this setting, but beware that you’ll see a performance hit (and a small additional one for the actual event handler code you run).

So how do you do it?

EnableEventReceivers

Possible Values: 0 = No, 1 = Yes, Default Value: No.

This property allows you to control whether event receivers are allowed to fire during the import or not. The default is that event receivers are disabled during import. This configures the SPImportSettings.SuppressAfterEvents setting for the remote import job.

To modify this option please use the following STSADM command:

STSADM -o editcontentdeploymentpath -pathname <pathname> -enableeventreceivers yes | no

Note: In case if you get an error while running the STSADM command that looks like: Failed to update the content deployment path with name................................... Just make sure that you are running the command with proper privileges (one hack just run this command with the same app-pool account as the Central admin, but yes if you run it with a proper privileged account that should not be a problem).

Another important thing that I have observed is we restart the OWSTIMER service then we need to run the STSAM -o editContentDeploymentPath command to enable or disable the eventhandlers again.

Javascript RichHTMLField control sharepoint Page Layouts

ketaanhs — Thu, 12 Mar 2009 07:29:00 GMT

We are working on a Publishing portal (MOSS / Sharepoint 2007) and we had a requirement to allow the authors to enter Rich HTML content and that can contain javascript to popup some images that appear as small images in the content or just as a link. Now out of the box the RichHTMLField control rips off all javascript that you enter, but we wanted to allow the users to enter "onclick popup the page" kind of javascript in the content so that in DISPLAY mode the Jscript function could execute.

So we came up with a simple approach to add a client side handler (i.e. Java script that will find and replace the required tags) to replace a specific TAG on our page with the actual javascript tag (as our tags were constant). Following Java Script that we have added to the Master Page in the Head tag just before the </Head> tag (Thank you Rajendra Rawat for creating this Javascript) should help understand how to overcome the limitation:

// Add an entry to the _spBodyOnLoadFunctionNames array
// so that our function will run on the pageLoad event.

_spBodyOnLoadFunctionNames.push("EnableLinks");

//onload=EnableLinks;

function IsInDesignMode()
{
   if(document.getElementById("MSOLayout_InDesignMode").value == '1') return true;
   if(document.getElementById("MSOTlPn_SelectedWpId").value != "") return true;
   return false;
}

</script>
------------------------------------------------------------------------------------------------------------

Ensure body tag in master page looks like:
<BODY scroll="yes" onload="javascript:if (typeof(_spBodyOnLoadWrapper) != 'undefined') _spBodyOnLoadWrapper();">

otherwise
_spBodyOnLoadFunctionNames will come as ‘Undefined’ and code won’t execute.

And Following is the sample HTML (that you might add to the RICHHTMLFIELD):

<a href="http://blogs.msdn.com/controlpanel/blogs/posteditor.aspx?SelectedNavItem=Posts§ionid=5160&postid=9471322#" id="ThisStringToReplace_onclick=javascript:alert('hi');" >click here</a>

<tr>

</tr>

</table>

</div>

</td>

</td>

</tr>

</table>

By the way if you want to check on the client side whether the PAGE is in EDIT mode or DISPLAY Mode you can use the following:

Running our MOSS sites in IE-7 compat with IE-8

ketaanhs — Tue, 10 Mar 2009 19:34:00 GMT

We had worked on some MOSS portal sites and wanted to make sure the rendering is fine in IE-8 also without making any changes to the CSS, so the best thing we did was we added the following tag to our Master Page just below the HEAD html tag and then it rendered all our pages in IE-7 mode even while browsing from IE-8:

<!—End of Use IE7 mode in IE8 browser -->

Following article cam in handy: http://support.microsoft.com/kb/956197

Presence indicator problem with Custom Master Page scrolling

ketaanhs — Tue, 10 Mar 2009 05:56:00 GMT

Problem:

I have got a unique problem that when you hover over any contact, the actual presence icon appears several pixels below the actual icon.

This only happens when the page is scrolled down and works perfectly when the page is not in scrolled position.

Also, it works fine when I apply the default master page to the site.

Solution 1:
The problem is identified sometimes back with the init.js function IMNGetOOUILocation() that returns a fixed location (coordinate) 0, and probably this is causing issue in your custom master page scenario also.

Add this function in the master page, to check if that resolves the issue you are having:

****************************************************************************************************************************************

function IMNGetOOUILocation(obj)

{

var objRet=new Object;

var objSpan=obj;

var objOOUI=obj;

var oouiX=0, oouiY=0, objDX=0;

// Changed Fixed scroll up coordination problem due to master page

var scrollTopY = (document.documentElement &&

document.documentElement.scrollTop) ? document.documentElement.scrollTop :

(document.body.scrollTop ? document.body.scrollTop : 0);

var fRtl=document.dir=="rtl";

while (objSpan && objSpan.tagName !="SPAN" && objSpan.tagName

!="TABLE")

{

objSpan=objSpan.parentNode;

}

if (objSpan)

{

var collNodes=objSpan.tagName=="TABLE" ?

objSpan.rows(0).cells(0).childNodes

objSpan.childNodes;

var i;

for (i=0; i < collNodes.length;++i)

{

(collNodes.item(i).tagName=="IMG" && collNodes.item(i).id)

{

objOOUI=collNodes.item(i);

break;

}

if (collNodes.item(i).tagName=="A"

collNodes.item(i).childNodes.length > 0 &&

collNodes.item(i).childNodes.item(0).tagName=="IMG" &&

collNodes.item(i).childNodes.item(0).id)

{

objOOUI=collNodes.item(i).childNodes.item(0);

break;

}

obj=objOOUI;

while (obj)

{

if (fRtl)

{

if (obj.scrollWidth

>=obj.clientWidth+obj.scrollLeft)

objDX=obj.scrollWidth - obj.clientWidth - obj.scrollLeft;

else

objDX=obj.clientWidth+obj.scrollLeft - obj.scrollWidth;

oouiX+=obj.offsetLeft+objDX;

}

else

oouiX+=obj.offsetLeft -

obj.scrollLeft;

// Changed Fixed scroll up coordination problem due to master page

//oouiY+=obj.offsetTop - obj.scrollTop;

oouiY+=obj.offsetTop;

obj=obj.offsetParent;

}

try

{

obj=window.frameElement;

while (obj)

{

if (fRtl)

{

if (obj.scrollWidth

>=obj.clientWidth+obj.scrollLeft)

objDX=obj.scrollWidth - obj.clientWidth - obj.scrollLeft;

else

objDX=obj.clientWidth+obj.scrollLeft - obj.scrollWidth;

oouiX+=obj.offsetLeft+objDX;

}

else

oouiX+=obj.offsetLeft - obj.scrollLeft;

// Changed Fixed scroll up coordination problem due to master page

// oouiY+=obj.offsetTop -

obj.scrollTop;

oouiY+=obj.offsetTop;

obj=obj.offsetParent;

}

} catch(e)

{

};

objRet.objSpan=objSpan;

objRet.objOOUI=objOOUI;

objRet.oouiX=oouiX;

//!!! This is the code change:

// Changed Fixed scroll up coordination problem due to

master page

//objRet.oouiY=oouiY

objRet.oouiY=oouiY - scrollTopY;

if (fRtl)

objRet.oouiX+=objOOUI.offsetWidth;

return objRet;

}

****************************************************************************************************************************************

Solution 2: (Suggested by Madhur Ahuja):

Also, there is another workaround , Add the following CSS:

body

{

position:static;

}

form

{

position:relative;

}

CONTENT DEPLOYMENT, CONTENT EDITOR WEB PART, NOT VISIBLE (MOSS 2007)

ketaanhs — Thu, 05 Mar 2009 06:48:00 GMT

I was working with Ben {Risher} today and we did a content deployment of our AUTHORING site to the target site i.e. PUBLISHING SITE. Our Authoring site had pages (web part pages) that were using Content Editor web parts (CEWP) with some static HTML contents.

Now these content editor web parts were not visible on the pages of our Target publishing site even after the content deployment and also our end users were given RESTRICTED READ permission and they were getting ACCESS DENIED errors on these pages (with content editor web parts), we tried to debug the issue and when we got rid of the CEWPs the users were able to browse to the site and were not getting ACCESS DENIED errors anymore, so what was so different about the CEWP, well it was nothing but AUDIENCE TARGET property of the web part in the Authoring site was set to AUDIENCES from an SSP that was now removed from the FARM and hence after content deployment the same AUDIENCE IDs were carried to PUBLISHING environment and somehow CEWP was not working out for RESTRICTED READ permission level.

So the bottom line is if you do Content Deployment and you have AUDIENCE TARGETED CEWPs then the webparts are not rendered on the PUBLISHING SITE, check the AUDIENCE TARGET property and the audiences (GUID) inside it. Check if these AUDIENCES exists in the SSP for that farm.

I dont think this is the problem with CEWP alone this could happen with any other web part also,