will there be an update for the TYPO3-CMS /func Extension to TYPO3 9.5.x? or is there a different way for using the Features now?
Sort pages and create pages have been moved the context menu in the page tree (under "More"). If you have a third party extension which extends the func extension, I'm afraid they will have to be rewritten to use their own backend module.
This changelog will tell you why there will be no updates
https://docs.typo3.org/typo3cms/extensions/core/Changelog/9.0/Breaking-81787-DropEXTfunc.html
It's available here https://extensions.typo3.org/extension/func/
and the introduction of the documentation explains why it will not be updated further
https://docs.typo3.org/typo3cms/extensions/func/
Related
We're currently struggling at creating Extension Provider with FluidPowered Typo3. This tutorial is outdated an we can't find any solution how to make Fluid Extension Provider from scratch. Also the 'builder' extension is not compatible with Typo3 versions higher than 8.5.
https://fluidtypo3.org/documentation/templating-manual/templating/provider-extension/generating-extensions.html
Is there any possibility to create Fluid Powered Extension Provider with Typo3 v. 9? Where are informations about custom extension provider files structure, controllers etc. ? The last post on Fluid website is from 2017.
You might want to look at this page instead: FluidTemplate documentation
And yes its short, but everything I could write is at that page. ;)
I have a sulu 1.6 installation with multiple webspaces. I have multiple page template definitions in app/Resources/templates/pages, like default.xml, homepage.xml, blog.xml, center.xml.
Is it possible to make for example the center.xml only available for the content of one webspace and not all the others?
UPDATDE:
Where can I change this behaviour in the code, that per webspace only the ones are showing up, that are defined in the webspace.xml? This is really blocking and a super bad user experience, since the template is directly linked together with the configured webspace, but the others do not fit.
Thx a lot!
Andreas
The template is only shown in the dropdown if its .html.twig file exists. So if you use the SuluThemeBundle and only a specific theme implements its .html.twig file the template will not be shown on the other theme aslong as the .html.twig does not exists there.
This feature has not yet been implemented, because not too many people have asked for it...
Since Sulu 2.0 you can limit the template on the webspace using the exclude-templates inside your webspace configuration:
<excluded-templates>
<excluded-template>overview</excluded-template>
</excluded-templates>
Before the only way to limit page templates was to work with themes.
I have to migrate TYPO3 6.2 websites to 8.7. Some websites use custom pibase extensions, do I need to redevelop them with Extbase ?
All previous answers have been correct but some words from a TYPO3 core team member: There are no plans to drop the support of "pibase" in the core. It is absolutely ok to use that API even though it does not provide much help to developers.
However I recommend to use at least fluid standalone to be able to create nice templates without all those ### stuff.
you don't need to redevelop these extensions, but you might need to change the call to core functions.
In 6.2 you still could use the old class names like t3lib.
These class names are available only with compatibility layer (together with a lot of delay).
For the future you need to use namespaces (and the correct new classes). You also should use namespaces for your own classes.
Depending on your used functions you might need to replace some calls with the newer functions as some functions got deprecated meanwhile.
You don't need to redevelop these extensions.
Just you need to change some TYPO3 core function like t3lib_div t3lib_BEfunc t3lib_parsehtml t3lib_extMgm and more..
Please see complete example here : See more details
I am new to TYPO3 and creating a TYPO3 extension. Extension can be added to a given place by the BE using the wizard. No problem.
My question is how can I add/call extension manually any place I want. For example among text.
What i mean is like Joomlas Mambots. Call the extension inside {myextentionName} among text for example.
Please any idea/help with an example is kindly appreciate.
You can find the TypoScript definition for each plugin below tt_content.list.20.<plugin-key>.
On top of that, most plugins provide a fully working version below plugin.<ext-key>.
If all fails, you can use the USER object to call the plugin directly. You will find an example in one of the above paths, because that is what the plugins to after all.
You can use typoscript tree and plugin keyword with the extension name for example plugin.xxxx.pi1.
I am a new TYPO3 user.
How to create an extension or plugin in Typo3 V 6.0, which will take an UID as an input and return the titles of the root page and its child pages if any. I am also using FLUID templates to display the returned data on the front end.
Thank You in advance.
Extension Builder in version 2.5.0+ is dedicated for creating extensions in TYPO3 ver 6.0+
FE plugin is just some action in your extension, play a little with builder, so you'll get familiar with the concept soon.