Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at

  • Simon steed 373 posts 685 karma points
    Dec 07, 2012 @ 14:59
    Simon steed

    Question on permanent usage?

    Just a quicke - love the profiler, helped to sort a big issue this week with some Razor scripts so very useful

    Question 1 around renaming the umbraco:macro to profiler:macro - why is this needed, could you not retain umbraco:macro and use the masterpage flag to enable profiling?

    Question 2 If we renamed all our macros to Profiler but did not enable profiling in config and master pages, is there any performance hit to doing this?

    Basically I think it would be really useful to have this available to turn on at the flick of a switch but renaming all the macros is a pia :-)

    Your thoughts?

  • Jorge Lusar 150 posts 489 karma points
    Dec 10, 2012 @ 10:26
    Jorge Lusar

    Hi Simon,

    I'm glad you liked it and found it to be useful.

    About question 1, this is needed because I did not want to override the default macro, so you could have is a page some macros you want to profile and others that you don't. But I agree it just might be easiers to only have umbraco:macro and I might add this new functionality in the next release.

    Regarding question 2, there should not be any performance penalty when the MiniProfiler is disabled as it falls back to the default behaviors on theumbraco.presentation.templateControls.Macro. You can see the source code on ;



  • Simon steed 373 posts 685 karma points
    Dec 10, 2012 @ 12:55
    Simon steed

    Hi Jorge

    Thx for reply - I'd deffo include the ability to use umbraco:macro instead as it's makes the tool so much easier to use.


Please Sign in or register to post replies

Write your reply to: