Smarty

strikernl · Smarty n00b Joined: 07 Dec 2010 Posts: 2

In smarty 2 this was 'valid', at least it didn't spawn any notices, even on error_reporting(E_ALL), with the links key not existing:

U.Tews · Posted: Tue Dec 07, 2010 1:42 pm Post subject:

This is an intended change. Smarty2 and the early Smarty3 versions did always turn E_NOTICE off. This was against the coding standards in many organizations as other coding errors for example in plugins might not be detected.

With the error_reporting property you have now full control about Smarty's error reporting behaviour.

strikernl · Smarty n00b Joined: 07 Dec 2010 Posts: 2

Is it not possible to wrap such calls in isset() in the compiled template automatically?

The thing is, there are some notices I _do_ want to get, such as calls to non-existent Smarty functions (for instance, I am migrating this from Smarty 2, and I want to rewrite everything to Smarty 3 as I go, not in one effort. So calls to register_function for instance _should_ give a notice).

U.Tews · Posted: Tue Dec 07, 2010 3:43 pm Post subject:

That's why you can set up $smarty->error_reporting. It's setting is used just for the processing time of the template itself.

With $smarty->error_reporting = E_ALL & ~E_NOTICE you get exactly the old behaviour.