We have moved to GitHub Issues
Created by Sebastiaan Janssen 19 Aug 2012, 14:53:44 Updated by Sebastiaan Janssen 08 Sep 2013, 19:38:23
Now that the behaviour has changed a bit for Macro parameters, bugs can be real tricky to find. In earlier releases you didn't need to define a parameter in the macro settings, but now you do.
If you try to use an undefined parameter you will not get any kind of error or message, the value will simply be empty when you try to access it in the macro.
I would either like the macro to fail to render, outputting a message that an undefined parameter XYZ is being used. Or at least give a diagnostic output telling the same when using umbdebugshowtrace=true.
Silently just failing gives me a headache when there's a typo or I have forgotten to define the parameter.
''Originally created on CodePlex by [eatfrog|http://www.codeplex.com/site/users/view/eatfrog]'' on 1/10/2012 12:05:16 PM [Codeplex ID: 30668 - Codeplex Votes: 2]
Since v4.11.6 and v6.0.3 this should be fixed with the macroerrors configuration option. http://umbraco.com/follow-us/blog-archive/2013/3/27/umbraco-603-and-4116-released.aspx
Backwards Compatible: True
Due in version: