Bug #20283: Extract BackendSearch from hardcoded Module to sysext - TYPO3 Core - TYPO3 Forge

Actions

Copy link

Bug #20283

closed

Extract BackendSearch from hardcoded Module to sysext

Added by Steffen Ritter over 15 years ago. Updated about 6 years ago.

Status:

Closed

Priority:

Should have

Assignee:

Christian Kuhn

Category:

Target version:

Start date:

2009-04-06

Due date:

% Done:

Estimated time:

TYPO3 Version:

4.3

PHP Version:

5.2

Tags:

Complexity:

Is Regression:

Sprint Focus:

Description

current backend search in toolbar uses "normal" API to register Toolbar-Items.
Including of this is currently hardcoded in backend.php

So tasks to request are:
- move classes/class.backendsearchmenu.php into sysext/beSeachMenu
- add registerToolbarItem.php and needed standard files to ext
- remove line 139 from backend.php (trunk 5289)

this is a prerequisite for implementing any other search, since there is no possibility to deactivate the hardcoded one...
(issue imported from #M10850)

Files

Download all files

10850_v1.diff (1.23 KB) 10850_v1.diff		Administrator Admin, 2009-04-06 11:29
backendSearch.t3x (4.84 KB) backendSearch.t3x		Administrator Admin, 2009-04-06 11:30

Actions

Copy link

Updated by Steffen Ritter over 15 years ago

addition to the patches:
Files
typo3/classes/class.backendsearchmenu.php
typo3/js/backendsearch.js

have to be removed

Actions

Copy link

Updated by Christian Kuhn over 15 years ago

Resolved, won't fix.

The RFC has been dropped in the core mailinglist.

Quote Ingo Renner:
"-1 you can just modify the existing one. Alternatively you could also
"overwrite" it by overwriting the key in the backend toolbar items array."

"The search is an important part of the backend and thus it's ok to be
(semi) hardcoded."

Actions

Copy link