Smarty

[dioobr]

I migrated from version 3.1.19 to 3.1.29 and found a great little problem. My code looked like this:

[dioobr]

This is probably the most stupid question, whose solution is obvious: use the constant as a variable in the template.

[AnrDaemon]

That notice would only make sense, if you are using tx when it is not assigned to template. I.e. some code path is going around your assignment, but still render the same template.

[U.Tews]

Since a while you can use constants directly in templates.

This could create some ambiguity when using the {$foo.bar} syntax for array access and bar but bar is also a constant.