Disabling Template Eval Permanently?

[Blinker]

Hi guys

Quick question:

A while ago I was getting some errors in my log related a mod and JimM (god bless him) helped me out by showing me how to disable and re-enable template eval to determine the true location of an error.

Code Select Expand

INSERT INTO smf_settings VALUES ('disableTemplateEval', 1);

Code Select Expand

DELETE FROM smf_settings WHERE variable = 'disableTemplateEval';

I've had to run the disable query several times since so my question is this - 

Is there any harm in leaving it turned off permanently?

I imagine like me that plenty of people have to run the query regularly so I leave it off. Is there a problem with that?

[Tanks]

I also have these stupid errors and i am thinking of turning template eval off for good.. any harm in doin so ?

[Aleksi "Lex" Kilpinen]

Now - I'm not exactly sure about this, but as I've understood - in some cases it might even be better to just leave it off. ( With certain accelerators I seem to remember )
The only real downside I can think of, would be that some errors you might get, wouldn't be as pretty anymore.

Anyone feel free to correct me if I'm wrong here

EDIT:
Related topics

http://www.simplemachines.org/community/index.php?topic=290186.0
http://www.simplemachines.org/community/index.php?topic=50227.0

[Blinker]

Thanks for the reply LexArma. After reading those two threads I've decided to leave eval() off (disabled).

I don't have an accelerator and I'd rather see the true nature and location of my errors.

Cheers!

[Tanks]

But does this (leaving it off) means that the users see the errors ??

I think right now they dont see the errors i have in my error log.. some thing about subtemplate above body eval

[Blinker]

No they don't see the errors but you will see the full error in the admin error log.

The only errors they'll see will be template parse errors and any other serious stuff that's broken.

[Tanks]

Thanks Blinker