All worked just fine in 2.5.1 but when I upgrade to 2.6.3 I receive Internal Server Error (500) when opening Resources Browser with an initial statement 'The server didn't send back a proper XML response'.
On updating I modified config.js and changed browser support from php default to asp and in conectors\asp\config.js changed the image initial path and check everything twice.
I found nothing on my gogle search that made any sense. Any idea where I went wrong?
On updating I modified config.js and changed browser support from php default to asp and in conectors\asp\config.js changed the image initial path and check everything twice.
I found nothing on my gogle search that made any sense. Any idea where I went wrong?
Re: Upgrade 2.5.1-2.6.3 - Internal Server Error(500) - ASP
Re: Upgrade 2.5.1-2.6.3 - Internal Server Error(500) - ASP
Mu understanding of codepage is not good but it seems I should be able to keep this commented. Any problems doing this?
Re: Upgrade 2.5.1-2.6.3 - Internal Server Error(500) - ASP
What's your webserver? I guess that you are using a pretty old one if it doesn't have the response.codepage property.
Re: Upgrade 2.5.1-2.6.3 - Internal Server Error(500) - ASP
Re: Upgrade 2.5.1-2.6.3 - Internal Server Error(500) - ASP
If there is a better workaround please let me know. thanks
Re: Upgrade 2.5.1-2.6.3 - Internal Server Error(500) - ASP
I am using IIS on a Windows 2000 server and I have ALL the updates.
What are we to expect for commenting out that line?
' Response.CodePage = 65001
Re: Upgrade 2.5.1-2.6.3 - Internal Server Error(500) - ASP
Hey,
I think the issue is with windows 2000 server and the version of IIS.
Windows 2000 - IIS 5
Windows XP Pro - IIS 5.1
Windows 2003 Server - IIS 6.0
The issue is that Response.CodePage was introduced in 5.1+ and is not supported in IIS 5.0 and below.
http://msdn.microsoft.com/en-us/library/ms525789.aspx
So, I'm not sure what commenting it out will affect in FCKEditor, but for those using IIS 5.0 (windows 2000 pro or server) will not be able to use the upload module for FCKEditor.
It won't be an issue for me much longer as we're replacing our development server in January, but others might be affected.
NOTE :: there's a bug tracker on this and this info might be helpful to configure a remedy to eliminate the bug from the tracker:
http://dev.fckeditor.net/ticket/2604
Joe