Bug #54562

Useful error messages for users

Added by Thomas Hempel over 1 year ago. Updated 10 months ago.

Status:Closed Start date:2013-12-22
Priority:Should have Due date:
Assigned To:- % Done:

0%

Category:-
Target version:Base Distribution - 1.1

Description

At the moment, as Neos is still very very young and has a lot of quirks and misses fundamental documentation, the error messages it throws every time you do something else then editing the Demo Sitepackage are not helpful at all.

The error messages consist of cryptic messages and backtraces. Here is an example

Exception while rendering
page<TYPO3.Neos:Page>/
body<TYPO3.TypoScript:Template>/
content/
main<TYPO3.Neos:ContentCollection>/
itemRenderer<TYPO3.Neos:ContentCase>/
default<TYPO3.TypoScript:Matcher>/
element<Scriptme:Article>:
The TypoScript object at path "page/body/content/main/itemRenderer/default/element" could not be rendered: Missing implementation class name for "Scriptme:Article". Add @class in your TypoScript configuration. (20131222080619db2270)

What does that even mean? The "@class" is barely mentioned in any of the documentation and this error doesn't make sense whatsoever. I just created a custom element with a handful of properties. Why would I need to define the class for it. There is no special logic involved. (I followed the documentation on creating your own content elements.)

Please try to give meaningful feedback. With this I neither know what is wrong (as it makes no sense and worked in 1.0.0) nor what I should do to solve it because the suggested solution doesn't make sense either.

This is just an example. In many other cases, the user only get's the backtrace with a general message that sounds a little like "something something very wrong. much error. something something".

Greets,
Thomas

History

#1 Updated by Thomas Hempel over 1 year ago

FYI: The solution for this problem is that I used a wrong prototype for my content element.

Instead of

prototype(TYPO3.Neos:Content)

I wrote

prototype(TYPO3.Neos.NodeTypes:Content)

I don't know if it is even possible to catch something like that. But "Can't render content "Scriptme:Article" because the prototype "TYPO3.Neos.NodeTypes:Content" does not exist." would have been a way better error message.

Greets,
Thomas

#2 Updated by Philipp Hanebrink 10 months ago

  • Status changed from New to Closed

Also available in: Atom PDF