Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Bug clicking on browse server in fckeditorBug clicking on browse server in fckeditor
Previous
 
Next
New Post
8/6/2010 10:08 AM
 

Hi

An error has crept into a site deployed to a customer based on DNN.

Its when you go to link to a file or page within an article using the fckeditor.

When you click on browse server, the page pops up but is broken now (this was working away fine for the last year or so). No changes have been made to the code.

Providers/HtmlEditorProviders/Fck/fcklinkgallery.aspx?FCKTheme=Default&tabid=237

Parser Error
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

Parser Error Message: Unexpected end of file looking for </asp:LinkButton> tag.

Source Error:

Line 45:     </TR>
Line 46:     <TR>
Line 47:      <TD><asp:LinkButton id="cmdSelect" resourcekey="cmelect" cssclass="CommandButton" runat="server">
      Select created link</aspLinkButton></TD>
Line 48:     </TR>
Line 49:    </TABLE>
 

Source File: /Providers/HtmlEditorProviders/Fck/fcklinkgallery.aspx    Line: 47

I've checked the source aspx file and its fine. Not sure why its complaining about an unterminated linkbutton control

The only thing I can think of is that perhaps a file has been uploaded that had an unusual character in the file name that is disrupting the generated code.

Any ideas?

 
New Post
8/6/2010 10:36 AM
 
Is it a DNN Version previously 5.4.4 I suggest a upgrade.  Also a look to the Event viewer would be helpfull with detailed error log.
 
New Post
8/6/2010 11:32 AM
 
The version is quite old at this stage, 4.8

What is the risk of upgrading from 4.8 to 5.4. Bear in mind we have a number of add on modules running...

This was something I was kind of afraid to do. Its a production site and I can not risk it going wrong...
 
New Post
8/6/2010 11:34 AM
 
AssemblyVersion: 04.08.02
PortalID: 0
PortalName: deleted
UserID: 1
UserName: deleted
ActiveTabID: 237
ActiveTabName: FormTest
RawURL: /Providers/HtmlEditorProviders/Fck/fcklinkgallery.aspx?FCKTheme=Default&tabid=237
AbsoluteURL: /Providers/HtmlEditorProviders/Fck/fcklinkgallery.aspx
AbsoluteURLReferrer:
UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; Trident/4.0; Hewlett-Packard; GTB6.5; .NET CLR 1.0.3705; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022; Hewlett-Packard; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; InfoPath.2; MS-RTC LM 8; .NET4.0C; .NET4.0E)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 7dba9103-49af-4d07-be9c-d20fad88151e
InnerException: Unhandled Error:
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Web.UI.TemplateParser.ProcessException
StackTrace:
Message: System.Exception: Unhandled Error: ---> System.Web.HttpParseException: Unexpected end of file looking for </asp:LinkButton> tag. at System.Web.UI.TemplateParser.ProcessException(Exception ex) at System.Web.UI.TemplateParser.HandlePostParse() at System.Web.UI.TemplateControlParser.HandlePostParse() at System.Web.UI.PageParser.HandlePostParse() at System.Web.UI.TemplateParser.Parse() at System.Web.UI.TemplateParser.Parse(ICollection referencedAssemblies, VirtualPath virtualPath) at System.Web.Compilation.BaseTemplateBuildProvider.get_CodeCompilerType() at System.Web.Compilation.BuildProvider.GetCompilerTypeFromBuildProvider(BuildProvider buildProvider) at System.Web.Compilation.BuildProvidersCompiler.ProcessBuildProviders() at System.Web.Compilation.BuildProvidersCompiler.PerformBuild() at System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVirtualPathObjectFactory(VirtualPath virtualPath, HttpContext context, Boolean allowCrossApp, Boolean noAssert) at System.Web.Compilation.BuildManager.CreateInstanceFromVirtualPath(VirtualPath virtualPath, Type requiredBaseType, HttpContext context, Boolean allowCrossApp, Boolean noAssert) at System.Web.UI.PageHandlerFactory.GetHandlerHelper(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath) at System.Web.UI.PageHandlerFactory.System.Web.IHttpHandlerFactory2.GetHandler(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath) at System.Web.HttpApplication.MapHttpHandler(HttpContext context, String requestType, VirtualPath path, String pathTranslated, Boolean useAppConfig) at System.Web.HttpApplication.MapHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) --- End of inner exception stack trace ---
Source:
Server Name: deleted
 
New Post
8/6/2010 11:38 AM
 
The FCK issue is me known from DNN 5 not on DNN 4, so I suggest to upgrade to 4.9.5 ! 

I have never see your issue before on DNN 4.x, except it caused by a 3rd parity module.
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Bug clicking on browse server in fckeditorBug clicking on browse server in fckeditor


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out