SphereServer BugTracker - SphereServer |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0001749 | SphereServer | executable - generic | public | 12-05-10 17:01 | 17-09-12 20:49 |
|
| Reporter | Mirravin | |
| Assigned To | Terrikate | |
| Priority | normal | Severity | text | Reproducibility | always |
| Status | resolved | Resolution | fixed | |
| Platform | | OS | | OS Version | |
| Product Version | 0.56c Nightly | |
| Target Version | | Fixed in Version | 0.56c Nightly | |
| Nightly Version | Not Available |
| Experimental Flags | None |
| Option Flags | None |
| Internal Build Number | |
|
| Summary | 0001749: ERROR: Bad Login... |
| Description | Why bad login(for example incorrect password) is an error? It is not the error, but normal situation. This addes problems searching real errors in logs. I suggest to remove this word "ERROR" complitely or replace it with "WARNING". |
| Steps To Reproduce | |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | | has duplicate | 0001957 | closed | | Change ERROR: messages to WARNING: in bad login (wrong password, no account etc). |
|
| Attached Files | |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 12-05-10 17:01 | Mirravin | New Issue | |
| 12-05-10 17:01 | Mirravin | Nightly Version | => Not Available |
| 12-05-10 17:01 | Mirravin | Experimental Flags | => None |
| 12-05-10 17:01 | Mirravin | Option Flags | => None |
| 17-11-10 14:54 | Mirravin | Issue Monitored: Mirravin | |
| 13-05-11 21:22 | MrSugarCube | Relationship added | has duplicate 0001957 |
| 17-09-12 20:44 | Terrikate | Assigned To | => Terrikate |
| 17-09-12 20:44 | Terrikate | Status | new => assigned |
| 17-09-12 20:49 | Terrikate | Status | assigned => resolved |
| 17-09-12 20:49 | Terrikate | Fixed in Version | => 0.56c Nightly |
| 17-09-12 20:49 | Terrikate | Resolution | open => fixed |