Feature #24949: Order of module menu entries - TYPO3 Core - TYPO3 Forge

Custom queries

Accessibility
Easy tasks
Forge Triage
JavaScript issues
JavaScript Issues (w/o Epics/Stories)
My open issues
No feedback within 90 days
Open Bugs
Open issues of 10
Recently modified
Regressions
Stabilization Issues
Usability or UX

Watchers (2)

Georg Ringer
Jo Hasenau

Actions

Copy link

Feature #24949

closed

Order of module menu entries

Added by Ralle Büchnitz almost 14 years ago. Updated over 2 years ago.

Status:

Closed

Priority:

Should have

Assignee:

Category:

Backend User Interface

Target version:

Candidate for Major Version

Start date:

2011-02-04

Due date:

% Done:

Estimated time:

PHP Version:

5.3

Tags:

Complexity:

Sprint Focus:

Description

Order and position of menu-elements depend on the order of their installation. But this is quite confusing as you the web-menu-elements may appear in different order in different typo3's.

It would be a good solution to order (at least all system extensions) in a predefined way. Whether they are installed or not. Like it was int he good old typo3's ;-)

This is just a small usability improvement.

The menu elements of the web menu seem to appear in the way they are installed.

Maybe all non-system-extensions could be ordered by their extension key. So the order will be the same on every typo3.
(issue imported from #M17476)

Related issues 3 (0 open — 3 closed)

Related to TYPO3 Core - Bug #47936: Improve Module-Menu API and implement

Closed

Mathias Schreiber

2012-06-24

Actions

Related to TYPO3 Core - Bug #28502: t3lib_extMgm::addModule(): support sorting of main modules

Closed

2011-07-27

Actions

Related to TYPO3 Core - Bug #97105: Module Registry has wrong sorting in v12

Closed

Benni Mack

2022-03-04

Actions

Issue # Delay: days Cancel

History
Notes
Property changes

Actions

Copy link

Updated by Ernesto Baschny almost 14 years ago

The idea is good but the solution is quite complex.

Currently an extension (including the sysext's) have the possibility to add themselves "before" or "after" some other existing module or as "top" (start). Default is "at the end".

Trouble starts when one adds itself "after/before" some module which is not even installed anymore. E.g. uninstalling "Info" sysext will drop the "info" module, which is currently being used by Workspaces "before:info", so the result is Workspaces being placed at the end. Ugly, I confess, but a result of our "new flexibility".

Hardcoding the order of the sysext seems "brutal"; but might be the only solution. Maybe having some sort of "order" parameter (like the new context menu) would help.

Some more information:

Old hardcoded (4.4) modules were:

$TBE_MODULES = array(
'web' => 'list,info,perm,func',
'file' => 'list',
'user' => 'ws',
'tools' => 'em',
'help' => 'about,cshmanual'
);

- "layout" module was added with "top" (EXT:cms)
- "view" module was added with "after:layout" (EXT:viewpage)

Which then created the ordering we all know:

layout,view,list,info,perm,func,workspaces

Ideas how to acchieve that?

Actions

Copy link

Updated by Ralle Büchnitz almost 14 years ago

What about a second order param like a number? And if you want to have sysext's as the first extensions to appear prepend an integer 1 to any non-system-extension. So that you can be sure to have a predefined order.

Like
web -> 10
file -> 20
user -> 30
powermail -> 10 (but becomes 110 as "1" will be prepended and
order/position is like desired)
templavoila -> 10 (same as above - but also with alphabetical order and p is before t)

and so on...

This could be written to a cache or serialized andwritten to a config file till any new extensions will be installed. (For perfomance reasons.)

Maybe you need to drop the current sorting for 4.6? As two sorting algorithms will be confusing?! Then you should add a default sorting param to any new extension p.e. 50 or so.

What do you think about that? To difficult?

Actions

Copy link