How to enable verbose logging in Mango 1.4.3+
With Mango 1.4.2, logging was moved from the insecure (using the default location, anyway) file-based logging to database logging. This was a great security improvement, because then nobody could just pull up your error and warning logs and get a hold of semi-secret information that might give a hacker clues that help them gain access to your site.
However people complained that too much was being logged, causing the database to grow at a rate faster than they thought was reasonable. To combat this, a setting was added to control how much information gets logged in the event of a plugin error. By default, only summary information is logged. This tells you which plugin is throwing the error, but does not include any of the information you might need to debug the error. If you're a plugin developer -- or even just trying to troubleshoot a problem on your blog -- it would be really helpful to have that detail information. Here's how.
In the root of your blog's folder, find config.cfm and open it up. It's going to be a jumbled mess of xml (without line breaks) but don't worry, the stuff we want to change is all the way at the end. Just jump to the end and start scanning backwards.
Find this section:
<node name="logging">
<map>
<entry key="level" value="warning"/>
</map>
</node>
...And change "warning" to "debug". To make the change take effect, go into the Cache section of admin and click the Reload Configuration button. Until you do this, errors will still only have summary information logged.
Do note that this will cause a lot of information to be logged for errors, which could cause the database to grow significantly if your blog is throwing lots of errors. I would encourage you to use something like LogViewer to inspect and clear the error logs regularly.
in Mango Posted 2010-07-09 02:20
3 responses:
Leave a comment: