Bug #36231
closed
Search on page should be merged with main search
Added by Fabien Udriot over 12 years ago.
Updated about 7 years ago.
Category:
Backend User Interface
Description
The search on page that is available in module list along with module page is not ideal:
- redundant with the main search
- not very visible for End User
We should improve the situation.
Could we have it merged with the main search (the upper right search).
Files
The search I am talking about:
Are there already ideas in the air about this topic?
Could we add a new keyword in the main search. We currently have #page, #content for filtering the scope of search. Could we add a "#this" to define the current page. Or does the keyword make it to geeky? Obviously, we will add this new keyword into the local help (the blue box - if you see what I am mean) for the sake of clarity for the End Users.
At the moment, the situation is as follows:
foo -> will search all (configured) tables
#page: foo -> will search in table "pages"
#content: foo -> will search in table "tt_content"
Then we could add:
#this: foo -> will search all (configured) tables on the current pid
- Category set to Usability
- Status changed from New to Needs Feedback
- Priority changed from Should have to Could have
This was already changed. Or not?
This was the concept back than at the UXW I've suggested.
http://forge.typo3.org/projects/usability/wiki/T3UXW09-Team4-20091117
Since the release of 4.5 I think the search at the top-right includes
a so called local view, which provides the search results of the search
from the bottom in the past. Am I right? This was at least what I wished :)
Greez WrYBiT
This was already changed. Or not?
Don't think so. Tested on 4.7 with #page_id
In my opinion this is the correct way.
The search form in page and list modules should be removed completely.
To train the livesearch to obey the selected page there should be be two sections within the search results:
1. Local results (currently selected page)
2. Global results
- Status changed from Needs Feedback to Accepted
- Project changed from 78 to TYPO3 Core
- Category changed from Usability to Backend User Interface
- TYPO3 Version set to 8
- Is Regression set to No
- Status changed from Accepted to Closed
I close this issue in favor of #53666, please continue the discussion there.
Also available in: Atom
PDF