TYPO3 Core

In TYPO3 CMS version 6.2.9 and 7.0.2 the error is the same but there is a link "More information regarding this error might be available online." which links to the page

http://wiki.typo3.org/Exception/CMS/1294587217

the page explains the origin of the error and the first steps that must be done.

i know, but from the Usability POV the page should clearly state that this TYPO3 is not configured, and that a tutorial can be found somewhere or that a distribution can be installed.

It´s not a technical but a usability problem to lower the barier for starters.
The more information link is often ignored as people know, that most articles are simply empty ...

I know! :)

Maybe the error could be changed into something more friendly like:

The page is not configured! [no PAGE object with typeNum=0 found!][Please verify your Typoscript Setup configuration!]

mhmm i would use:

Welcome

Congratulations, your TYPO3 Installation is running.

Sadly there is no configuration for a page object with typeNum=0.

You can now either install a distribution from the Extensionmanager to get a sample page running easily or you can setup a basic page like described in our TYPO3 for beginners tutorial. (linked).

Have fun

I would also link documentation etc.

Dear mr. Kay Strobach,
the message you propose is very nice and user-friendly...but, well..my only concern is that it seems to imply that you are running the CMS for the first time. In other words: are you sure that this error is always a "first run" error?
The source of the error could be that you added somewhere a

page >

i totally get you, but IMHO the professional user like you and me will understand the "Sadly there is no configuration for a page object with typeNum=0.", which is still there ;) But newbies will instantly get directed to the docs and we avoid frustrated users :D

I did quite a lot of tutorial sessions with TYPO3 and most first time users complained about the non friendly greeting after the installation.
So IMHO this should be the target audience for that kind of message.

In my case the message appeared more often due to the lack of config, instead of a deleted page object, perhaps we should hand this to Matthes as RM to make a decission or ask the UX team ;)

I agree this is a matter for UX team; thank you for your feedback