![\"magelogs\"](\"http:\/\/dknzdesign.com\/wp-content\/uploads\/2015\/01\/magelogs1.jpg\")
<\/p>\n<\/p>\n
When developing your own module in Magento, it’s useful to pass variables and other messages out to a debug file so you can see how your module is working with its data. Magento comes with 2 built in log files, system.log & exception.log, both located in the var\/log<\/strong> folder. To activate them, you must go to the Magento admin panel and under: System->Configuration->Developer->Log Settings<\/strong>, you will see a setting for enabling the logs. \nsystem.log<\/strong> is used for general debugging and catches almost all log entries from Magento, including warning, debug and errors messages from both native and custom modules. Going through the system.log<\/strong> can be a nightmare, with dozens of other modules outputting to the log it can be like finding the proverbial, needle in a haystack. So why not create a custom log for your module!, With Magento its so easy:<\/p>\n And that’s all there is to it. You can pass variable, arrays, messages to yourself, whatever you want. Just be careful when outputting native Magento objects, as they can be really really big. (Don’t ever try to output and entire product object!) Default Log files When developing your own module in Magento, it’s useful to pass variables and other messages out to a debug file so you can see how your module is working with its data. Magento comes with 2 built in log files, system.log & exception.log, both located in the var\/log folder. To activate them,…<\/p>","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[40],"tags":[45,47,49,46,44,43,48],"_links":{"self":[{"href":"https:\/\/dknzdesign.com\/sl\/wp-json\/wp\/v2\/posts\/351"}],"collection":[{"href":"https:\/\/dknzdesign.com\/sl\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dknzdesign.com\/sl\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dknzdesign.com\/sl\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/dknzdesign.com\/sl\/wp-json\/wp\/v2\/comments?post=351"}],"version-history":[{"count":11,"href":"https:\/\/dknzdesign.com\/sl\/wp-json\/wp\/v2\/posts\/351\/revisions"}],"predecessor-version":[{"id":365,"href":"https:\/\/dknzdesign.com\/sl\/wp-json\/wp\/v2\/posts\/351\/revisions\/365"}],"wp:attachment":[{"href":"https:\/\/dknzdesign.com\/sl\/wp-json\/wp\/v2\/media?parent=351"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dknzdesign.com\/sl\/wp-json\/wp\/v2\/categories?post=351"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dknzdesign.com\/sl\/wp-json\/wp\/v2\/tags?post=351"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\n![\"enable-logs-magento\"](\"http:\/\/dknzdesign.com\/wp-content\/uploads\/2015\/01\/enable-logs-magento.png\")
<\/a><\/p>\n
\nexception.log<\/strong> is reserved for exceptions only, for example when you are using try-catch statement.
\nTo output to either the default system.log or the exception.log see the following code examples:<\/p>\nMage::log('My log entry');\r\nMage::log('My log message: '.$myVariable);\r\nMage::log($myArray);\r\nMage::log($myObject);\r\nMage::logException($e);\r\n<\/code><\/pre>\n<\/p>\nCustom Log Files<\/h3>\n
Mage::log('My log entry', null, 'mylogfile.log');\r\n\/\/pass a variable\r\nMage::log('My Variable: '.$myVar, null, 'mylogfile.log');\r\n<\/code><\/pre>\n
\nSo now you have the equivalent of console.log()<\/strong> in javascript for your new mage application. Please drop me a line if this has worked for you, and remember to comment out your debug log statements before you output for production.<\/p>","protected":false},"excerpt":{"rendered":"