Beware of debug logger?? True or False??

[DivaVocals]

Not sure if this is the right place to post this, but I wanted to get opinions on this from the Zen Cart experts..

I ran across this blog post: Beware of zencart debug logger!

Which states:

In the recent versions of Zencart (I think starting from 1.3.9h) you will find that includes/extra_configures/enable_error_logging.php exists by default. This file will turn on the debug switch and will put the logs into your /cache folder. The problem is that it also puts lots of WARNINGS and such inside this, and ZC does generate lots of those. Within a short amount of time (depending on the number of visitors you have and number of warnings etc), this folder will be flooded with log files and will more than likely lead to many performance issues and such.
I recommend that you rename this to enable_error_logging.php.bak and only rename it backs when you want to check for an issue.

Any truth to this?? Has this been the experience of others??

[grneyes]

Yes! It's happening on everyone of my clients sites that use1.3.9h. On my own site it had over 10000 debug errors in the cache in just a few days.

[Ajeh]

You should not have any debug logs unless you have a problem to fix ...

If you have a problem they need to be addressed until there are no more debug logs generated ...

Should you get too many to open the /cache then rename it /cache_full and make a new /cache with proper write permissions and check the error messages and correct the issues ...

Once fixed, delete the debug logs and the /cache to be clear of all debug logs if all is working correctly ...

Trying to turn off the debug logs so they do not fill up the /cache is fool hardy as you are not fixing anything and you need to fix whatever is not working so that you do not get any debug logs ...

[DivaVocals]

You should not have any debug logs unless you have a problem to fix ...

If you have a problem they need to be addressed until there are no more debug logs generated ...

Should you get too many to open the /cache then rename it /cache_full and make a new /cache with proper write permissions and check the error messages and correct the issues ...

Once fixed, delete the debug logs and the /cache to be clear of all debug logs if all is working correctly ...

Trying to turn off the debug logs so they do not fill up the /cache is fool hardy as you are not fixing anything and you need to fix whatever is not working so that you do not get any debug logs ...

This was my thought as well when I read this.. Thanks for your insight..

[grneyes]

I would fix it if I could figure out the problem but just loading my index page should not cause a send mail error but yet it does every single time it's loaded.

[DivaVocals]

I would fix it if I could figure out the problem but just loading my index page should not cause a send mail error but yet it does every single time it's loaded.

Honestly you should start a new post about this to try and sort out the issues you are having (you might start with posting some DETAILS of the exact error messages you are getting)

The intent of this topic wasn't to troubleshoot errors in the error log.. I wanted to get an opinion about the advice given in this article.

[grneyes]

Honestly you should start a new post about this to try and sort out the issues you are having (you might start with posting some DETAILS of the exact error messages you are getting)

The intent of this topic wasn't to troubleshoot errors in the error log.. I wanted to get an opinion about the advice given in this article.

I wasn't asking anyone to troubleshoot anything. No reason to be rude about it.

[DivaVocals]

I wasn't asking anyone to troubleshoot anything. No reason to be rude about it.

Rude eh?? You read WAY MORE into my post and assigned sentiments to it I did NOT convey (or even mean).. Your accusation is rude... I merely suggested that IF you were seeking troubleshooting assistance (which your post seemed to feel like) that you should start a fresh post to get some help from the community.. 'tis all..

[DrByte]

I ran across this blog post: blog.rubikintegration.com/2012/02/04/beware-of-zencart-debug-logger

Which states:

In the recent versions of Zencart (I think starting from 1.3.9h) you will find that includes/extra_configures/enable_error_logging.php exists by default. This file will turn on the debug switch and will put the logs into your /cache folder. The problem is that it also puts lots of WARNINGS and such inside this, and ZC does generate lots of those. Within a short amount of time (depending on the number of visitors you have and number of warnings etc), this folder will be flooded with log files and will more than likely lead to many performance issues and such.
I recommend that you rename this to enable_error_logging.php.bak and only rename it backs when you want to check for an issue.

Any truth to this?? Has this been the experience of others??

There's only a small bit of truth in those statements: yes the site's performance will slow down if there is a huge number of debug logs.

BUT there will ONLY be debug logs if there are actual errors on the site. A default clean install of the current version of Zen Cart (ie: v1.5.0 as of today) does NOT trigger any debug logs.
So, any problems that are showing in the logs are a result of sloppy coding on the part of whoever has been customizing the site or its addons.

I suppose this merely exposes that the folks at rubikintegration have a lot of code problems :O

[DrByte]

I would fix it if I could figure out the problem but just loading my index page should not cause a send mail error but yet it does every single time it's loaded.

Honestly you should start a new post about this to try and sort out the issues you are having (you might start with posting some DETAILS of the exact error messages you are getting)

The intent of this topic wasn't to troubleshoot errors in the error log.. I wanted to get an opinion about the advice given in this article.

And I would agree with DivaVocals: if you are reading this thread and have a lot of debug logs, it is best for you to start a separate thread to discuss your specific problems, including details from the most recent log entries. Be sure to review the FAQs for possible answers to your error messages before posting, as it may save you some time.