Hello all,
After some digging, I found two possible workarounds to solve this issue
- Follow this blog article, that suggests to update the crawler user agent string to remove the error. I don't like this option because it
will tells asp.net to render controls in uplevel mode
- Use a control adapter. Here are the steps to implement it :
Code of the adapter :
namespace YouNamespace.GanttSearchFix
{
[Guid("B9D71139-8AC2-4320-BC00-E7B375231D5C")]
public class GanttSearchAdapterFix : ControlAdapter
{
private static string g_CrawlerUserAgent = GetCrawlerUserAgent();
private static string GetCrawlerUserAgent()
{
using (var regKEy = Registry.LocalMachine.OpenSubKey(@"SOFTWARE\Microsoft\Office Server\14.0\Search\Global\Gathering Manager"))
{
var userAgentValue = (string)regKEy.GetValue("UserAgent");
return userAgentValue;
}
}
protected override void OnLoad(EventArgs e)
{
var context = HttpContext.Current;
if (context != null)
{
if (string.Compare(context.Request.UserAgent, g_CrawlerUserAgent, true) != 0)
{
base.OnLoad(e);
}
}
}
}
}
Create a .browser file :
<?xml version="1.0" encoding="utf-8"?>
<browsers>
<browser refID="Default">
<controlAdapters>
<adapter controlType="Microsoft.SharePoint.WebControls.Gantt, Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"
adapterType="$SharePoint.Type.b9d71139-8ac2-4320-bc00-e7b375231d5c.AssemblyQualifiedName$" />
</controlAdapters>
</browser>
</browsers>
(note that I have to add "browser" extension in the SharePoint token files replaceable parameters).
Deploy this files under the APP_Browsers folder of your web app. Recycle the application pool.
This will remove the OnLoad methods of the control when the user agent string is the one defined by the crawler. The check of the browser level is done within this method.
Hope that helps, two years later :)
Paying back the community for its help by writing articles :
Have a Nice Day.Net Blog
