In the past you were able to use ?umbDebugShowTrace=true to see the true error of an Umbraco Macro. I know this is no longer supported in Umbraco 7, therefore what is now the best method to see the true error message being produced by a Razor macro in Umbraco 7??
Thanks for the heads up. I have managed to get the mini-profiler working but this doesn't seem to expose the actual error that a macro is throwing unlike the umbDebugShowTrace method which used to display the exact C# error in RED. How do you go about getting the C# error that a macro is actually throwing in Umbraco 7??
Yes - as Graham mentioned the mini profiler works but doesn't expose the macro error like the umbDebugShowTrace did. (or the contents of UmbracoTraceLog)
Debugging macros
In the past you were able to use ?umbDebugShowTrace=true to see the true error of an Umbraco Macro. I know this is no longer supported in Umbraco 7, therefore what is now the best method to see the true error message being produced by a Razor macro in Umbraco 7??
Hi Graham
This changed with the release of Umbraco 6.1.0.
Now you can write ?umbdebug=true and see a miniprofiler as described in this post http://umbraco.com/follow-us/blog-archive/2013/5/30/indulge-in-all-this-umbraco-goodness-three-releases-in-one-day.aspx - I have not tested with v7 yet but I suppose this would be the same steps to take.
Please note it does not work using XSLT based macroes. Then one will have to open up the logfile found in /app_data/logs
Hope this helps.
/Jan
Hi Jan,
Thanks for the heads up. I have managed to get the mini-profiler working but this doesn't seem to expose the actual error that a macro is throwing unlike the umbDebugShowTrace method which used to display the exact C# error in RED. How do you go about getting the C# error that a macro is actually throwing in Umbraco 7??
Graham
Graham - did you find any solution/alternative to this?
Hi Guys
Sorry for the late answer - Must have missed the e-mail notification on this one.
Have you set "umbracoDebugMode" to true in the web.config file?
/Jan
Hi Jan,
Yes - as Graham mentioned the mini profiler works but doesn't expose the macro error like the umbDebugShowTrace did. (or the contents of UmbracoTraceLog)
Hi Matt
Hmm, yeah that is a bugger. Think you can find those in the /app_data/logs file with the "ERROR" tag...
/Jan
Out of interest what's the best practice for debugging macros? Develop in visual studio/get the errors on build?
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.