Bug #88100
closed
Page tree hooks removed in TYPO3 v9 without deprecation warning in TYPO3 v8
0%
Description
- Changing the sorting of parts of the page tree (like on date), using node post processing
- Adding suffix or prefix to the page title in the page tree (like a date), using node post processing
- Filtering pages
- Getting tree mounts
The hooks could be used with
$GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['t3lib/tree/pagetree/class.t3lib_tree_pagetree_dataprovider.php']['postProcessCollections']
According to the TYPO3 core team rules no hooks can be suddenly removed without a proper deprecation warning in the previous version, in this case TYPO3 version 8. There were no deprecation warnings in version 8
Updated by Georg Ringer over 5 years ago
- Status changed from New to Needs Feedback
the removal of the mentioned hook has been anounced as breaking change with issue #82426
see https://docs.typo3.org/typo3cms/extensions/core/Changelog/9.0/Breaking-82426-ExtJSAndExtDirectRemoval.html for the related documentation.
breaking changes sometimes need to happen and as you know it is tried to have those as less as possible. I would propose to create a new issue to propose additional hooks, is that ok?
Updated by Patrick Broens over 5 years ago
The removal of the hooks was done with no regard to the TYPO3 core development policy, which clearly states: TYPO3 core development policy states that public API will not be changed without a grace period where extension authors can adapt to the changes. In that grace period a deprecation warning will be thrown. If you want to remove or change functionality in the TYPO3 core, it has to be deprecated first.
See https://docs.typo3.org/typo3cms/ContributionWorkflowGuide/Appendix/HowToDeprecateThings.html
Since they are hooks, they are part of the public API of TYPO3.
The new classes for the page tree are declared @internal, which means they are not part of the public API. This means it makes no sense to add a hook or signal to it. @internal means no information should be displayed in public documentation.
Nevertheless, I will have a look if I can propose new signals or hooks
Updated by Georg Ringer over 5 years ago
- Status changed from Needs Feedback to Closed
besides breaking changes ...
as you created #88099 anyway, I will close this issue