Extending Extensions
summary
Shows how TYPO3 extension hooking actually works: signals and slots dispatch a single array parameter, validate only array shape and element count, and run in unspecified order so the last modifier wins; hooks are plain global arrays with no enforced signature; X-classes override one original class per project so the last registration wins and breaks easily. Concrete fixes: add DB field + TCA to extend Extbase models, implement an Abstract Finisher to add a Form finisher, and note PSR‑14 event dispatcher arriving in TYPO3 10/310.
AI-written summary · about
chapters (11)
- 0:00Introduction and speaker intro
- 1:04Speaker background and talk overview
- 2:32Signals and slots explained
- 10:14Under the hood of signals and slots
- 13:38Hooks in TYPO3
- 17:49Hook limitations and data changes
- 20:23Xclasses in TYPO3
- 24:22Extending models without hooks
- 29:39Adding form finishers
- 32:31Outlook to PSR-14 event dispatcher
- 34:01Q&A session
related talks
45m"Robust Testing Strategies for TYPO3 Projects"
42mBeyond OOP: Developing PHP Extensions ... in PHP!
27mDesign Considerations for a simple Extension Framework For MySQL
57mWhen there's not a module for that
21mHookup with WordPress
45mPHP Extensions
28mA field guide to writing PHP extensions
44m"TYPO3 NEW APIS"