Link to log file

[GoogleCodeExporter]

Add a link to the log file to ZP config page.
The file should be available to the admin only, not for anyone to download.
Give a user friendly msg if the file is not there.

Original issue reported on code.google.com by zetapri...@gmail.com on 8 Dec 2009 at 11:20

[GoogleCodeExporter]

Given the size of the log file on a busy server it's not a good idea to use 
HTTP for
this.

Let's just write everything into the standard Magento log.

We need a setting on the config page to let users choose to log or nor to log 
and
probably what to log as well. I'll leave it up to you to decide what we need to 
log.
The purpose is to help users troubleshoot using the logs without involving us. 
This
is just the first step, so the expectations are low. 

Write a wiki to explain:
  * how to turn logging on/off
  * where to find logs
  * how to access them
  * what is being logged (in general terms, but QC needs to know more for testing)

Original comment by zetapri...@gmail.com on 5 Jan 2010 at 10:17

[GoogleCodeExporter]

Turn logging on/off at System/Configuration/Developer page on magento admin 
interface.

File with logs are placed at ftp://www.zetaprints.com/magento/var/log/system.log

At this moment all debug information (successed and failed requests to zp) is 
being
logged.

Original comment by Anatoly....@gmail.com on 5 Jan 2010 at 11:57

[GoogleCodeExporter]

New code is available at magedev

Original comment by Anatoly....@gmail.com on 5 Jan 2010 at 12:02

[GoogleCodeExporter]

Original comment by Anatoly....@gmail.com on 5 Jan 2010 at 2:32

• Changed state: Finished

[GoogleCodeExporter]

How to test:
1) Find the instructions on logging in wiki, if you can. Are they in the right 
place?
2) Turn the logging on.
3) Import a couple of templates, run a few previews, place an order or two.
4) Change the API key and try to import again. 
5) Locate the logs. Copy locally, zip-up and store for analysis.
6) Turn the logging off. Try to import again with a failure and with success. 
Check
the logs. They may have changed, but there should be no new stuff from us in 
them.

Original comment by zetapri...@gmail.com on 7 Jan 2010 at 1:10

[GoogleCodeExporter]

I did find the instructions in the first place I looked (Troubleshooting). But 
the
wiki page does need a better explanation on how to reach the log files.

Attached zip holds the logs of the testing process in separate folders:

1. No err 
- initial log file after I enabled logging and ran a profile
2. Successful data import and order 
- logging turned on, no profile running err
3. Wrong API 
- run profile with an invalid API
4. No_logging_ZetaPrints_sync 
- Turned OFF logging in the main configuration tab of M admin page (ZetaPrints 
Sync
tab) but left it ON in the Developer tab. Ran a profile and the log file got a 
lot
bigger.
5. No_loging-success_and_err
- Turned logging OFF in the Developer tab and left it on in the ZetaPrints Sync 
tab.
Ran a profile with a valid and an invalid API. Log file did not change.

Note. Steps are numbered continuously as I did the testing.

Original comment by agur...@gmail.com on 8 Jan 2010 at 2:08

• Changed state: MoreWork

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I'm not sure what the problem is.
That wiki page needs a separate section for logging.

Original comment by zetapri...@gmail.com on 8 Jan 2010 at 10:23

[GoogleCodeExporter]

Original comment by zetapri...@gmail.com on 18 Jan 2010 at 12:14

• Changed state: Done