[TYPO3-hci] [TYPO3] Mysql error...

[Jens Hoffmann]

I'm not so good in Coding PHP. So i need to ask stupid:
Isn't there a better way to produce more "uncryped" messages?

Own CD-Layout for the Errors.

Three Information Blocks:
1. Easy/Basic Error Description (Everybody could understand this.)
2. How has this Error happend ... last Action ... (Info for the Dev.)
    + Typo3 Ver. and Ext. Ver, Apache Ver, etc.
    + The "cryped" Error (The usual one)
3. Call to Action. What can i do now. (Dev. eMail addy, Dev. Forum 
Mailinglist, etc.)

Greez Jens

Martin Kutschker schrieb:
> Staffan Ericsson schrieb:
>> Jens Hoffmann skrev:
>>
>>> I don't get HCI point in this thread?
>>> What's it about? Better Error Messages?
>>
>>
>> Yes - this is a not too uncommon occurrence when working with typo3. The
>> error reports pointing to some part of the core and nothing giving any
>> hints about where the problem is.
>>
>> Useful error messages is a vital part of good HCI.
> 
> In theory yes. But for this particulary error the user will eventually 
> get only the same message in a better layout/format. All the DB class 
> knows is that some code tried to execute a wrong SQL.
> 
> Masi