I am using the following code to render inline razor c# macro. After upgrade to U4.10, every macro content follow with an asp.net trace. I am still using master page, no MVC template yet. Also, is it (&umbDebugShowTrace=true) still working on U4.10?
I experience the same on a website I just updated to v4.10.0.1 (production website). The result is in the footer, as shown below (the website URL is http://www.villatropezienne.com.
For the time being, I have added the some JQuery script code to hide the __asptrace div:
Been struggling with this as well. I even tried parsing the markup using the HtmlAgilityPack, but it seems the trace markup is not valid html, so that was a no-go...
Anyway, here's what seems to be a temporary fix:
Inspired by this post I tried setting trace="false" in /default.aspx - and yay, it seems to do the trick: No more rogue trace information!
Seems a bit more elegant than hiding the markup using css/js. Note that this overrides umbDebugShowTrace, so no more tracing even if you need it, but I'll take that drawback for now.
U4.10 ASP.NET Trace spam
I am using the following code to render inline razor c# macro. After upgrade to U4.10, every macro content follow with an asp.net trace. I am still using master page, no MVC template yet. Also, is it (&umbDebugShowTrace=true) still working on U4.10?
umbDebugShowTrace still works in 4.10 and tracing should be disabled by default.
If I understand correctly the main page does NOT have trace info, but anything that you render through library.RenderMacroContent has. Right?
Yes, you are right. One trace follow one macro. 'bodyText' is RTE data may has none or many macro inside it.
I experience the same on a website I just updated to v4.10.0.1 (production website). The result is in the footer, as shown below (the website URL is http://www.villatropezienne.com.
For the time being, I have added the some JQuery script code to hide the __asptrace div:
<script type="text/javascript">
$(document).ready(function(){
$('#__asptrace').css('display','none');
});
</script>
I just created a bug report for this one: http://issues.umbraco.org/issue/U4-1203. Please vote the bug if you experience the problem too. Thanks!
This is now discussed at http://issues.umbraco.org/issue/U4-1203
Been struggling with this as well. I even tried parsing the markup using the HtmlAgilityPack, but it seems the trace markup is not valid html, so that was a no-go...
Anyway, here's what seems to be a temporary fix:
Inspired by this post I tried setting trace="false" in /default.aspx - and yay, it seems to do the trick: No more rogue trace information!
Seems a bit more elegant than hiding the markup using css/js. Note that this overrides umbDebugShowTrace, so no more tracing even if you need it, but I'll take that drawback for now.
Fixed in 4.11
Big-ups for the swift action, Stephen.
I just thought I'd share my fix for others who, like me, need a temp solution here and now.
is working on a reply...