Usability Team

OK, if I'm called a conservative spoilsport, be it:

While I understand that the HCI Team has the right to decide certain things and probably overrule things for a good reason. I also highly appreciate all the cool things happend so far with the dedication of the team.

But I do not see a good reason in this case.

Because Google and Twitter do so?
Because it's funky?
Because it looks good?

I disagree and I was not the only one having such feelings about it.

Hi,

I don't think that the flipped logo is the problem within this discussion (related to the screen above). I think the wording is...

The "Oops, an error occured" was just a sentence I threw in my design one year ago. I think it should say something like "We apologize, an error occured. This shouldn't have happened..." (or something similar - maybe not "We apologize" ;)).

But the most important part is still missing: The explanation what caused the error and what would be a possible solution (instead of cryptic error-messages), or a link to a help-wiki, FAQ, forums etc.

The idea behind it was to help the user find a solution quicker, rather than keep going with technical error messages...

What I really like about the error message is that it now fits to the rest of the backend. It was still a missing piece in the puzzle for a streamlined TYPO3.

But the most important part is still missing: The explanation what caused the error and what would be a possible solution (instead of cryptic error-messages), or a link to a help-wiki, FAQ, forums etc.@

• Create an exception class, which accepts an error message and a title together with an error code. Currently only message + code are supported by PHP natively. We wanted to check first, how the FLOW3 guys built their Exception hierarchy
• Add a unique error code to every/some/most-frequent Exceptions, which are thrown in TYPO3. We have to discuss, if we limit us to create error codes only for Errors, which got a wiki page first (other way around would be to create the error codes, link them to empty wiki pages and hope for user contributions).

After that the ErrorHandler can automatically link to the wiki, when an error code is given.
We didn't forget your idea, it just needs some work around ;-)

As said in my duplicated suggestion entry (#10549 sorry for that), the guidelines regarding the use of the logo (http://typo3.org/teams/design/style-guide/the-typo3-logo/) explicitly prohibit change of orientation of it.

I really don't like this flipped logo and don't find it cool anymore.

Besides that, thanks for the work on the error message design in general (except the logo), it really looks better now.

Cheers

Anything new to this issue, or can we close it or what about the exception-classes for detailed error-messages? should we leave this issue in the list as a reminder?