BugNET

Open source issue tracking & project management

Forums

HomeHomeSupportSupportInstalling BugN...Installing BugN...Page Not Found for FCKEditor after installing BN 0.8.167.0Page Not Found for FCKEditor after installing BN 0.8.167.0
Previous
 
Next
New Post
1/29/2010 4:23 AM
 

The relevant source code for this (at FckHtmlEditorProvider.cs):

string basePath = HttpContext.Current.Request.ApplicationPath + "/FCKEditor/";

if(config["BasePath"] != null)
basePath = HttpContext.Current.Request.ApplicationPath + config["BasePath"];

The problem is that instead of using relative address only for virtual paths it is trying to ask the root address from the system. However Request.ApplicationPath is failing in a lot of scenarios. For instance we have to use very complex DNS re-routing, therefore the HttpContext.Current.Request.ApplicationPath property results in a simple "\" every time (so basically useless). I have modified the code to use a simple relative path instead:

string basePath = config["BasePath"];

if(basePath == null)
basePath =
"/FCKEditor/"; // or "FCKEditor/", it is irrelevant from now on, both are site relative

This way it will be independent from the enviroment. There are also a similar reference in Attachments.ascx, line 64. Is it possible to fix these in the next releases?

Thank you very much beforehand.

 
New Post
3/4/2010 8:12 PM
 

This fix didn't work for me. I still got page not found (404).

However, if I changed my code to be as follows, it seems to work just fine:

string basePath = HttpContext.Current.Request.ApplicationPath + "/FCKEditor/";

//if(config["BasePath"] != null)
//basePath = HttpContext.Current.Request.ApplicationPath + config["BasePath"];

Basically, just commenting out the second and third lines from the original code was all it took. Now the FCKEditor works just fine in my Issues as well as in my Welcome Message configuration.

Best regards,
Matt

 
New Post
3/21/2010 6:38 PM
 
I have found a muuuuch easier more configurable way to get the 404 error to disappear when trying to use the FCKEditor... No need to recompile!
In the web.config at the top-level of the BugNET application directory, go down to the line with the tag
  <HtmlEditorProvider defaultProvider="FckHtmlEditorProvider">
Then change the BasePath attribute in the subtag to ensure that there is a slash at the beginning of the path. This is counter-intuitive since in my web-structure, BugNET is not in the Root directory, but by making the path look like its the root directory seems to repair the problem.
So, change the following:
<add name="FckHtmlEditorProvider" type="BugNET.Providers.HtmlEditorProviders.FckHtmlEditorProvider, BugNET.Providers.FckHtmlEditorProvider" ... BasePath="FCKEditor/" />
To:
<add name="FckHtmlEditorProvider" type="BugNET.Providers.HtmlEditorProviders.FckHtmlEditorProvider, BugNET.Providers.FckHtmlEditorProvider" ...  BasePath="/FCKEditor/"  />
Please note the forward-slash at the beginning of the FCKEditor string in the second tag. That fixed it for me. Good luck.
 
New Post
3/29/2010 11:06 AM
 

I just modified <add name="FckHtmlEditorProvider" type="BugNET.Providers.HtmlEditorProviders.FckHtmlEditorProvider, BugNET.Providers.FckHtmlEditorProvider" Height="250" Width="100%" ToolbarSet="Default" Skin="Silver" BasePath="FCKEditor/">

to

<add name="FckHtmlEditorProvider" type="BugNET.Providers.HtmlEditorProviders.FckHtmlEditorProvider, BugNET.Providers.FckHtmlEditorProvider" Height="250" Width="100%" ToolbarSet="Default" Skin="Silver" BasePath="FCKEditor">

I thing something with how the path is used in the code is messing up with the /

 
New Post
4/11/2010 4:17 AM
 

I get the error on Racspace (Windows Server something or other, clustered), but not on IIS7/Win 7. I just removed it.

 
Previous
 
Next
HomeHomeSupportSupportInstalling BugN...Installing BugN...Page Not Found for FCKEditor after installing BN 0.8.167.0Page Not Found for FCKEditor after installing BN 0.8.167.0


Forum Policy

These Discussion Forums are dedicated to the discussion of the BugNET issue tracker.

For the benefit of the community and to protect the integrity of the project, please observe the following posting guidelines:
1. No Advertising.
2. No Flaming or Trolling.
3. No Profanity, Racism, or Prejudice.
4. Site Moderators have the final word on approving/removing a thread or post or comment.
5. English language posting only, please.