Hey-- this CKfinder program is fantastic! I'm having a problem, though-- I'm able to get it working in a dedicated environment just fine-- IIS 6, ASP.net 2.0. However, when I move it over to a shared hosting environment I get this error:
Server Error in '/' Application.
Security Exception
Description: The application attempted to perform an operation not allowed by the security policy. To grant this application the required permission please contact your system administrator or change the application's trust level in the configuration file.
on this page:
/FCKeditor/ckfinder/core/connector/aspx/connector.aspx?command=Init
Any ideas on what needs to be done? Again, the setup works fine on my dedicated server until I move it over.
Server Error in '/' Application.
Security Exception
Description: The application attempted to perform an operation not allowed by the security policy. To grant this application the required permission please contact your system administrator or change the application's trust level in the configuration file.
on this page:
/FCKeditor/ckfinder/core/connector/aspx/connector.aspx?command=Init
Any ideas on what needs to be done? Again, the setup works fine on my dedicated server until I move it over.
Re: ASPX problem
Thanks in advance.
Frederico Knabben
CKEditor Project Lead and CKSource Owner
--
Follow us on: Twitter | Facebook | Google+ | LinkedIn
Re: ASPX problem
Here are 2 knowledge base articles at my host on this problem:
https://www.webcontrolcenter.com/Knowle ... x?KBID=913
https://www.webcontrolcenter.com/Knowle ... x?KBID=927
One option they give is to move to a special "low security" server... which is something, unfortunately, that I probably couldn't get a client to be OK with.
This is one of the other pages I found to be helpful about the issue:
http://blogs.msdn.com/shawnfa/archive/2 ... 67390.aspx
but it would require source access to use the proposed fix... and i'm not even sure if it'd work on the host.
Thanks!
Re: ASPX problem
Just a follow-up. In reading through some forums on the hosts' website, it does appear that if you use the fix spoken about in this link:
http://blogs.msdn.com/shawnfa/archive/2 ... 67390.aspx
it should take care of the problem. I can't verify it, but it appears that it will work. Of course, I will test it if you make the change.