View Single Post
Old 06-13-2011, 02:44 PM   #2
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 12,449
Karma: 8012886
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
No, no syntax changes, but yes, better error reporting.

There is a long-term bug that permits templates to be (sometimes) executed inside templates. You have been tripping over this bug, where {null} appears to be a template accessing the field named "null". There is no such field. I haven't fixed this bug because it could be considered a feature.

Another bug permitted use of bogus field names. That bug has been fixed, now reporting the error instead of doing something else. In your case, the 'something else' was probably returning the word "null". If that is what you want to happen, remove the {} around the word "null". If you want something else to happen, then change the template appropriately.
chaley is offline   Reply With Quote