Why so many errors in sugar code?

[lfkohn]

I am using SugarCRM Enterprise -- just updated to 4.5.1

Whenever I try to use the System Settings : Display stack trace of errors: -- my app gets flooded with all sorts of errors - mostly smarty errors but other things that aren't really errors that keep me from seeing anything that is really going wrong.

Here is an example of just a few of the errors that show with "Display stack trace of errors" on:

private/var/www/html/crm_svk/cache/smarty/templates_c/%%7F^7F5^7F52877A%%EditView.tpl.php[L:17](:StackTraceErrorHandler)
/private/var/www/html/crm_svk/include/Smarty/Smarty.class.php[L:1258](:include)
/private/var/www/html/crm_svk/include/Smarty/Smarty.class.php[L:1108](Smarty:fetch)
/private/var/www/html/crm_svk/modules/Configurator/EditView.php[L:96](Smarty:display)
/private/var/www/html/crm_svk/index.php[L:645](:include)

kinda makes this feature unusable.

OS : Any ( on linux and MacOS X same issue
Sugar Version : 4.5.1 and 4.5.0
Webserver: apache 2.2
php version : 5.2.5
mysql version 5.0.51a

[Jeff.Tichenor]

Depending on what is causing your issue, it might be more helpful to use the SugarCRM logging system. By default, the log system will only log 'fatal' type errors. You can increase the logging level by editing the log4php.properties file in the SugarCRM root directory.
Sugar's log file is called sugarcrm.log by default. This is located in your SugarCRM root directory.
More information on using the log system can be found here:
http://www.sugarcrm.com/wiki/index.php?title=Debugging

The 'Display Stack Trace Errors' function is really designed to be used by developers when customizing the app.
If the SugarCRM log system does not provide you with the information you are looking for, then you could turn on php errors. This is done by editing the php.ini file and setting the 'display_errors = on'. You must restart your webserver after modifying the php.ini.