TYPO3 Core

What should this headline show anyway?
I found out the following until now:

- Shows title of the page if creating, editing records (e.g. tt_content)
- Shows title of the parent page if creating a new page
- Should show page title of the current page if editing a page.

Does this even make sense?
If yes, the problem you described should be easy to fix. See attached patch.
It may not be the best solution, but at least it fixes the problem.

The same error occurs when editing a BE user.

Can you have a look at that, too?

I can confirm that the attached bug fixes the issue with "Page Properties"

And I can confirm that the same issue is present when editing a be_user

It happens when editing a be_user, be_group, basically anything on the root page (PID:0).

When editing a record, the title of the parent page is shown as the headline. When editing a record on root level, there is no title, because a parent "page" doesn't exist. But which headline to display in that case?

In my opinion, it would be cool to display the title of the currently edited record. By title meaning the label field set in TCA. When creating a new record/page the headline could just say "New page/content/news/whatever". After saving, the entered title could be shown.

When creating a new record/page the headline could just say "New page/content/news/whatever". After saving, the entered title could be shown.

Sounds good! Go ahead!

Version 2 added.

When creating a new record, the label will be: Create new [tablename]
When editing a record it will be: Edit [recordtitle]

Please test yourself and see if it works. I am quite in a hurry right now, so I hope I didn't make any mistake in the code.

Anything else would be just confusing - I tested it with the current trunk and the title said "Root" while I was editing a page on the next level - so Reinhard's proposal seems to be only useful way to fix this misleading behaviour.

Thanks for the feedback. I will give it a try and post it on the core list.
As I see this as a bug, I hope this gets fixed for 4.4.

version 5 contained changes not belonging to this issue. Please ignore v5 and use v6 instead.

Committed to trunk rev 7911