Bug #43033
closed
Clicking page title leads to page settings
Added by Mario Rimann about 12 years ago.
Updated about 9 years ago.
Description
Tested on a 6.0.0rc1 installation, logged in as admin user:
Steps to reproduce¶
- Go to List module
- Click on the root of the tree (that contains two standard pages in my case)
- The list module is shown in the right pane and lists two pages
- Click on the title of one of those pages
Expected¶
The list module of that clicked page is shown (with it's contents)
Current behaviour¶
Instead of the list module, the form for editing the page settings are shown
- Category set to Backend API
- Target version set to 6.0.0
- Complexity set to easy
I can still reproduce this one on 6.1.5 - any pointer where in the "Backend API" something needs to be adjusted for this to be optimized?
Still present on 6.2.x, not only for the pages in root.
But..is this really a bug? clicking on the title of every record in the list module opens that record for editing...
- Status changed from New to Needs Feedback
This is actually not a bug, but streamlined with the other record types: On click in the list module, you can edit the record directly.
I just looked into this issue again. I see the point that its streamlined with the behaviour of $whatever record in the list module.
But still I think it's not what I expect upon clicking the name of a page. I also dont expect to get to the edit form of a non-page record, but there I could better agree with this functionality, as it won't contain sub-records (except IRRE records). But IMO this is something different with a page wich is by design a container for content elements. So I'd still prefer to get to the list of subpages/content-elements of a page when clicking the page's name in the list module.
But I agree to what our UI experts and the bigger part of the audience agrees to.
- Status changed from Needs Feedback to Closed
- Target version deleted (
6.0.0)
No feedback within the last 90 days => closing this issue.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by