Hello Anders. This is response to your kind offer of help on the oembed (http://our.umbraco.org/projects/oembed-macro---easy-embed-youtube,-flickr,-vimeo-etc/feature-requestbug-forum/8586-Yellow-screen-of-death) page. I did as you suggested and installed your project instead. Interestingly, I am still getting a yellow screen but this time the feedback may be more helpful. It looks like there is some security setting I need to change. Thanks for any help you may be able to provide.
umbraco version: umbraco v
4.0.2.1 (Assembly version: 1.0.3441.17657)
asp.net version: 2.0.50727
Windows and iis version: Windows Server 2003, IIS 6
Stack trace below
Detailed explanation below
I created a new page, inserted the macro, set the SourceUrl parameter to "http://www.youtube.com/watch?v=6_sWOd9WQGo", saved and published the page, then browsed to the page: http://forms.fcps.net/video-embed-test
The result was a yellow screen with the following:
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.
Exception Details: System.Security.SecurityException:
Requested registry access is not allowed.
Source Error:
[No relevant source lines]
Source File:
c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET
Files\root\3f9bce0d\3853655f\App_Web_default.aspx.cdcab7d2.t1rcpxms.0.cs
Line: 0
Well, this is strange. After I posted the above, I did sopme research on trust levels in ASP.net. As far as I can tell, umbraco is running in full trust mode on my server. I looked at the config file in the framework folder, and it sets the level at "full" and allows override. There is nothing in my umbraco folder's web.config to override this, so it should be running in full trust mode, as far as I can tell. So maybe this is not the real problem.
Please try and get the latest version of the project. Updated to support cache and refactored some code. I think it was because it was trying to write to the event log and not the umbraco log. But now its writing to the umbraco log
Security Exception
Hello Anders. This is response to your kind offer of help on the oembed (http://our.umbraco.org/projects/oembed-macro---easy-embed-youtube,-flickr,-vimeo-etc/feature-requestbug-forum/8586-Yellow-screen-of-death) page. I did as you suggested and installed your project instead. Interestingly, I am still getting a yellow screen but this time the feedback may be more helpful. It looks like there is some security setting I need to change. Thanks for any help you may be able to provide.
I created a new page, inserted the macro, set the SourceUrl parameter to "http://www.youtube.com/watch?v=6_sWOd9WQGo", saved and published the page, then browsed to the page: http://forms.fcps.net/video-embed-test
The result was a yellow screen with the following:
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.Exception Details: System.Security.SecurityException: Requested registry access is not allowed.
Source Error:
Source File: c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\root\3f9bce0d\3853655f\App_Web_default.aspx.cdcab7d2.t1rcpxms.0.cs Line: 0
Stack Trace:
Well, this is strange. After I posted the above, I did sopme research on trust levels in ASP.net. As far as I can tell, umbraco is running in full trust mode on my server. I looked at the config file in the framework folder, and it sets the level at "full" and allows override. There is nothing in my umbraco folder's web.config to override this, so it should be running in full trust mode, as far as I can tell. So maybe this is not the real problem.
Please try and get the latest version of the project. Updated to support cache and refactored some code. I think it was because it was trying to write to the event log and not the umbraco log. But now its writing to the umbraco log
is working on a reply...