TYPO3 Core

With real content, this is than way to much on one page >> modul_page_02.png

Possible Solution: A simple text line, which links to the list modul and explains
that there are more (different) records on this page, and that you could access
them via the list modul.

As Less, as Better :)

Ok - the screen modul_page_02.png is only if there are records on content-pages.

In this case a link or another option like the "Extended view" (maybe "Display records") could help to achieve the records.

1. Modul page

1.1 Content pages without records
- regular view (no changes)

1.1 Content pages with records
- regular view
- link to list
- alternative option "Display records" -> display the records under the content

1.2 Folders
- display all records automatically - no text "The current page is a folder..."

2. Modul list

no changes :-)

With the option 1.2 the editor can reach all content without changing the view... (i think this is a problem for a lot of people)

Hi,

I can understand your problem a bit.

• I guess it will not be easy to show all tables below the Page content (Page module itself is an (extended) instance of the List module - and it's a bastard..)
• Showing the tables will slow down the Page module. With your suggestion to create a checkbox for that it's a bit relaxed, but well, I'm still sceptic.
• You can already show tables below the Content Elements - tt_news and tt_calender do that. I think it's part of the problem that some extension tables are listed there, but not all.

Steffen

Hi,

the problem with tables below the page is more complex than i thought (I'm interesting, how tt_news solved this). To get a smooth solution we should care about two cases on the module Page:

1. Sysfolder (most used by editors for tables/records)
- display all records automatically - no text "The current page is a folder..."

2. Content pages (exceptionally for tables/records)
- display records by enabling a checkbox, etc...

Greetings
Gunther

There is also a use case for using a Folder like a normal Page in the Page module and just create content there as usual.

I've often seen configurations, where contents of such a special folder are used in other places of the web site (e.g. in a border column on every page). So IMHO we can't just redirect to the list module.

Steffen,

your case of using the Folder would work too - I don't want to redirect the user in any way. The Folder could display content elements (your case) and additionally records (my opinion) on the Page.

Greetings G.

Hi!

I have been thinking about this a lot as well. True is that in last 7 years I'd say 97% of my users don't need to change the view manually, it could be changed automatically for folder type pages.
On the other hand it's true, sometimes list view is needed for regular pages as well.

For TemplaVoila there is a page module that does automatic switching if opening a folder. Really useful for most of the sites. Now using TemplaVoila no more the problem is back.

One possible solution.

Remembering the last set module for the page? True, might become flow killer.
But what about setting defaults? Opening all folders in List module and regular pages in page module by default, but leaving possibility to change manually.
Adding a tiny feature but solving the problem for most common content editors.

Regards,

Tanel