The extension ke_search has a search field plugin that I want to insert into my fluidtemplate and show on every page. I am very new in this and don't know how to start. Any help is appreciated.
相关问题
- Access fluidpage configuration in template
- How to install an extension to TYPO3 using compose
- TYPO3 Ajax Page Configuration
- Extbase query to compare two fields in same table
- TYPO3: Set more than one storage pid for one exten
相关文章
- How to get TYPO3 settings in the utility files?
- “Controller does not exist. Reflection failed.” TY
- How can i have different translations for action c
- Typo3 LTS9 Routing: ReUse config.YAML
- TYPO3 Extbase: How to sort child objects
- How to add custom wizards in typo3 7 TCA?
- Typo3 eID, how to access config
- How to access properties of a FileReference Object
You can assign the Plugin to an typoscript lib:
(Please search the location of the plugin in the typoscript browser)
In your fluid you can use
f:cObject
to include it:In general you have three possibilities to include special content in all your pages:
Solution 1 has the drawback of being very static and you might miss the opportunity to configure dynamically (e.g. links, spamprotection, ...)
Solution 2 could be complicated if you want a plugin and the plugin can not be configured by pure typoscript (or the configuration collided with the configuration of the plugin in the main content)
Solution 3 needs a special (unvisible) page where the CE is stored and can be edited. In your TS you render it with the CONTENT object and use a hard coded uid. You need to remember that special place and special CE. (an editor might 'replace' the CE and wonder why it goes missing)
Solution 4 enables you to use 'normal' editor functionality (configure the plugin as a CE), but might cost some more rendering time because of the sliding and you need to define a special column with additional handling.
In addition to Bernd's answer, this is the simplest solution using 1) with TypoScript and some constants for the simplest
ke_search
input field, but this could be even hardcoded in your html template and it would still work. It's just a GET query that's being sent to the result page – where you set the searchbox again by page plugin.