Wednesday, April 02, 2008 2:48 PMProblem when updating Homepage (default.aspx) with FrontPage2003
Steps to produce the error:
- Load the site in FrontPage2003
- Edit the homepage default.aspx in FrontPage 2003
- Save the Page in FrontPage
- Navigate to the homepage url:
Errors being reported : Server Application Error, these errors seem to be generated because the wrong parser is handling the default.aspx page after it has become unghosted. It should be being handled by the asp.NET parser but because it is unghosted its being handled by the Sharepoint SafeMode Parser <ref: http://www.codeguru.com/cpp/misc/mis...cle.php/c9581/ >
To get the default page loading again the DOCs table within the content database was then updated. The one row refereeing to the URL for the default.aspx page was updated with similar values for an aspx page that was in the ghosted state. This was in the hope of making Sharepoint think the default.aspx homepage was ghosted.
This seemed to work as the default.aspx homepage loaded successfully, presumable now being parsed by the right aspx.NET parser. But then the following anomolies occur:
- · The customised template was replaced by a default Sharepoint template for the homepage.
- · The site hyperlinks for created sub- sites no longer work and produce an error : ‘Download unknown file type’
- · The ManageSites link no longer works and produced an error in the application log
‘Error in Path :/_layouts/admin/CreateNewSiteStep1.aspx’
Error Stack Trace : at System.Web.UI.TemplateParser.GetType(String typeName, Boolean ignoreCase)
at System.Web.UI.TemplateParser.ProcessMainDirective( IDictionary mainDirective)
at System.Web.UI.TemplateControlParser.ProcessMainDir ective(IDictionary mainDirective)
at System.Web.UI.PageParser.ProcessMainDirective(IDic tionary mainDirective)
at System.Web.UI.TemplateParser.ProcessDirective(Stri ng directiveName, IDictionary directive)
at System.Web.UI.TemplateControlParser.ProcessDirecti ve(String directiveName, IDictionary directive)
at System.Web.UI.TemplateParser.ParseStringInternal(S tring text)
at System.Web.UI.TemplateParser.ParseString(String text, String virtualPath, String basePhysicalDir)
Error TargetSite ystem.Type GetType(System.String, Boolean)
Please note the same errors were reported even after restoring the SharePoint content database to its previous state before the update to the DOCs table
Thursday, April 03, 2008 4:45 AM
It is recomended to use sharepoint designer instead of frontpage !
Frontpage is produced in 2003 and SP 3.0 produced in 2007.
Certainly frontpage can't recognize the sp 3.0 components.
Thursday, April 03, 2008 5:36 AMI would put it more strongly than the previous responder.
You CAN NOT use FP 2003 with WSS 3.0. If you do you will have both problems and corrupt sites.