Feature #39051

Story #82206: list module enhancements/bugfixes

Add support for page module, to automatic redirect to list module

Added by Dominique Feyer over 8 years ago. Updated 8 months ago.

Status:
Closed
Priority:
Could have
Assignee:
-
Category:
Backend User Interface
Target version:
-
Start date:
2012-07-18
Due date:
% Done:

10%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:
Needs Decision

Description

When the user select a sysfolder in the page module, currently the BE just display a link to the list module.

With a new option flag, the backend can redirect to the list module automaticaly, with a proper flashmessage in the list module to explain the user, why they have been redirected.


Related issues

Related to TYPO3 Core - Feature #36705: Forward pages with defined doctype to list viewNew2012-04-29

Actions
Has duplicate TYPO3 Core - Feature #64406: Switch to suggested backend module if configured by PageTsconfigClosed2015-01-21

Actions
#1

Updated by Ernesto Baschny over 8 years ago

  • Status changed from New to Needs Feedback

I would expect the usability team to look over such a change. Do you mind posting it in their tracker for approval?

http://forge.typo3.org/projects/usability/issues

Thanks!

#2

Updated by Philipp Gampe over 8 years ago

I would also like to have a way back ... e.g if the user selects another page later.

#3

Updated by Gerrit Code Review over 8 years ago

  • Status changed from Needs Feedback to Under Review

Patch set 2 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/12868

#4

Updated by Gerrit Code Review over 8 years ago

Patch set 3 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/12868

#5

Updated by Dominique Feyer over 8 years ago

Philipp Gampe wrote:

I would also like to have a way back ... e.g if the user selects another page later.

But the way back is not a easy to do. When I'm in list on a sysfolder ... and I select a page, maybe it's for managing record on this page, maybe it's for managing content, so the system can't know that.

What do you think ?

#6

Updated by Dominique Feyer over 8 years ago

Ernesto Baschny wrote:

I would expect the usability team to look over such a change. Do you mind posting it in their tracker for approval?

http://forge.typo3.org/projects/usability/issues

Thanks!

The cross post http://forge.typo3.org/issues/39065

#7

Updated by Dominique Feyer over 8 years ago

Based on Jens Hoffman answer in the UX thread the UX team seems OK with this feature.

Currently the feature is an option. Can it be the default value in 6.0 ?

#8

Updated by Ernesto Baschny over 8 years ago

I personally don't like it, I must confess.

The user just "clicking" around in the page tree will suddenly change module and it won't change back automatically when clicking again on non-Folder page.

Of course it is confusing having two modules to edit "content", but on the other hand, it would be more helpful to integrate both modules in one instead of jumping back and forth. Doing it automatically doesn't help the user, as it makes the user think it is "one module" while there is still a difference which he must know and learn.

Just my 2ct.

#9

Updated by Ingo Renner over 8 years ago

Just a note, if it should be a default behavior, you need to check whether the user is allowed to access the list view...

#10

Updated by Felix Kopp over 8 years ago

Keep in mind, that there might be setups, where a sysfolder contains tt_content elements.
E.g. folder Teasers that are selected on different pages via typoscript.

I don't think that a redirect is the way to go.

#11

Updated by Dominique Feyer over 8 years ago

Felix Kopp wrote:

Keep in mind, that there might be setups, where a sysfolder contains tt_content elements.
E.g. folder Teasers that are selected on different pages via typoscript.

I don't think that a redirect is the way to go.

This is just an option, and not the default behavior. So where's is the problem ?

Some setup manage tt_content in the list module in this case.

#12

Updated by Wouter Wolters almost 6 years ago

  • Status changed from Under Review to New
  • Assignee deleted (Dominique Feyer)
  • Priority changed from Should have to Could have
#13

Updated by Daniel Wagner almost 6 years ago

As this is an option which has to set by the integrator for some folders
it could be stored for the beuser that the module switch has been forced.
The check showing these flashmessages is done for every page so it should
be possible to switch back if the switch from page to list module has been
forced before and the new selected page is not a folder.

one case is ambiguous: forced switch and folder selected which not enabled
for automatic switching. to keep it simple i would not switch back, but ...

yes, two modules will still confuse but automatic switching will make life
a bit easier. (I have seen that extension vidi is offering a new list module.)

#14

Updated by Susanne Moog over 5 years ago

  • Sprint Focus set to PRC
#15

Updated by Riccardo De Contardi over 4 years ago

  • Category set to Backend User Interface
#16

Updated by Riccardo De Contardi over 3 years ago

  • Parent task set to #82206
#17

Updated by Riccardo De Contardi almost 3 years ago

  • Related to Feature #36705: Forward pages with defined doctype to list view added
#18

Updated by Riccardo De Contardi almost 3 years ago

  • Status changed from New to Closed

I close this issue in favor of #36705 please continue the discussion there. I've added a reference to this issue to keep track of the discussion in it.

If you think that this is the wrong decision please reopen it or ping me. Thank you.

#19

Updated by Benni Mack 8 months ago

  • Sprint Focus changed from PRC to Needs Decision

Also available in: Atom PDF