A couple of years ago I started using custom provider extensions for a more convenient way of getting my Typo3 projects started. Html templates, Typoscript files and assets, such as images, css and js files, are contained in a project extension. In this article I want to share about my way of setting up Typo3 projects.
After updating a website containing custom extensions built by the extension_builder I encountered the problem of my text fields not showing the RTE anymore.
Fetching data via ajax from your typo3 website frontend can be done with an eid script or a custom typoscript page object targeted with it’s own pagetype. The latter is explained in this post.
Sometimes it’s necessary to get tt_content data in a custom extbase extension. Because Typo3 doesn’t provide a model for the tt_content table we have to find a workaround. Extbase table mapping is the solution here.
Extending an extbase model of a Typo3 extension for custom fields is a commonly needed feature and quite easy to implement, once you figured out the necessary steps. In this post I am going to explain how a custom field is added in the case of extending the popular extension news for the custom field subtitle.
Continue reading Extend a Typo3 Extbase model with custom field
Sometimes it’s useful to add attributes, such as css classes or id’s, to the body tag to apply custom css styling for different pages of your website. In most cases it’s enough to use the bodyTagCobject and conditional comments, but sometimes more flexibility is needed.
For many years the typoscript HMENU has done a really good job in building a site menu in Typo3 websites and it still does. Sometimes though it happened that I got into trouble, because of the lack of flexibility this traditional way of building menus has. A while ago I started using the fantastic Fluidtemplates Extension for Typo3 templating and found a new – much more flexible – way of building menus.