Feature #66331
closedIndexed Search Extbase Plugin per Typoscript einbinden
0%
Description
Derzeit ist es nicht möglich das Indexed Search Extbase Plugin via Typoscript einzubinden. Etwa mit dem vorgeschlagenen Standard und derzeitiger Konfiguration:
lib.searchbox = USER
lib.searchbox {
userFunc = tx_extbase_core_bootstrap->run
extensionName = IndexedSearch
pluginName = Pi2
switchableControllerActions {
Search {
1 = form
}
}
view =< plugin.tx_indexedsearch.view
settings =< plugin.tx_indexedsearch.settings
}
Updated by Andreas over 9 years ago
Guess the extbase version is still very beta. Only a view typoscript configurations are recogniced from the indexed_search Extbase version.
E.c. There is a template path issue: plugin.tx_indexedsearch.view.templateRootPath = xxx has no effect
As against a view settings are used in the Extbase version: plugin.tx_indexedsearch.settings.displayAdvancedSearchLink = 0 works.
Typo3 Version: 7.1.0
Updated by Wouter Wolters over 9 years ago
- Status changed from New to Needs Feedback
Can you try the 7.2 version? indedex_search extbase version got some patches by Tymoteusz Motylewski
Updated by Alexander Opitz about 9 years ago
- Status changed from Needs Feedback to Closed
No feedback within the last 90 days => closing this issue.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.
Updated by Patricia Bartel over 8 years ago
For me it worked like this:
lib.searchBox = USER_INT lib.searchBox { userFunc = TYPO3\CMS\Extbase\Core\Bootstrap->run extensionName = IndexedSearch #TYPO3.CMS. vendorName = TYPO3\CMS controller = Search pluginName = Pi2 action = form view =< plugin.tx_indexedsearch.view persistence < plugin.tx_indexedsearch.persistence settings =< plugin.tx_indexedsearch.settings }
Tested in Typo3 7.6.4
Updated by Andreas Krämer over 8 years ago
Also works for me this way in TYPO3 7.6.6, thanks!
But I would use a USER object instead of USER_INT so the page could still be cached.
Updated by Daniel Schultheis about 8 years ago
There is even a shorter approach which should work without problems:
lib.searchBox < tt_content.list.20.indexedsearch_pi2 lib.searchBox { controller = Search action = form view =< plugin.tx_indexedsearch.view persistence < plugin.tx_indexedsearch.persistence settings =< plugin.tx_indexedsearch.settings }
This works because Indexed Search is already initialized inside the CASE cObject "tt_content"