View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000397 | SOGo | SOPE | public | 2010-01-27 17:32 | 2017-01-06 19:57 |
| Reporter | majovel | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | open | ||
| Product Version | 1.2.0 | ||||
| Summary | 0000397: SOGo does not honours the user default for log level | ||||
| Description | I tried NGLogDefaultLogLevel = OFF; Regardless of the value put in NGLogDefaultLogLevel, has no effect on the information that is written in sogo.log that remains the same level as with NGLogDefaultLogLevel = INFO; (the default fallback) I think the cause is in the NGLogger.m function provided that _level takes the value from NGLogDefaultLogLevel, !(true) is false and then always return NGLogLevelInfo A solution can be Greetings, MartÃn | ||||
| Tags | No tags attached. | ||||
|
Can you provide us with a sample usage? SOGo makes use of SOPE's logging methods which do not use NSLog... Have a look at the NGLogger class for similar parameters. |
|
|
2010-01-28 23:52
|
|
|
SOGo makes use of SOPE's logging methods. From NGLogger.h: NGLogger honours the following user default keys: User Default key FunctionNGLogDefaultLogLevel The log level to use as a fallback, if no Attached 2 sample logs, for NGLogDefaultLogLevel = "OFF" and "ERROR" From NGLogger.m |
|
|
Should be fixed: https://github.com/inverse-inc/sope/commit/d30c986f9d2cefc764ae420cc3f2509adc0fea33 |
|
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2010-01-27 17:32 | majovel | New Issue | |
| 2010-01-28 21:43 |
|
Note Added: 0000520 | |
| 2010-01-28 23:52 | majovel | File Added: samples.zip | |
| 2010-01-29 00:15 | majovel | Note Added: 0000522 | |
| 2013-06-20 18:27 |
|
Note Added: 0005681 | |
| 2013-06-20 18:27 |
|
Assigned To | => jraby |
| 2013-06-20 18:27 |
|
Status | new => resolved |
| 2017-01-06 19:57 | francis | Status | resolved => closed |