Closed thomaslow closed 1 month ago
Hm, some parent classes method's signature for some of the classes in Classes/Validation
have changed from TYPO3 v11 to v12. So the tests for v12 fail, because our classes don't explicitly declare the same parameter and return types as the TYPO3's parent classes. But if I add the type declarations, the tests for v11 fail, because now their signatures don't match with the parent classes in v11.
Any idea how we could avoid that? Maybe don't use declare(strict_types=1);
in those classes?
Also pinging @markusweigelt, because he is the author of the validator feature.
@sebastian-meyer Thanks for trying to merge. I'll have to look at this in more detail. It may be related to Breaking Change 96998.
Thank you for your implementations. I will test the 'Embedded 3D Viewer' later this week with your update.
Regarding the validation: Should we support both versions? It seems that security releases for TYPO3 11.5 are ending this month.
https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/12.0/Breaking-96998-ExtbaseValidatorInterfaceChanged.html#migration has some hint how to handle both versions.
Yes, if it is possible we should support both versions. There are some users who will use the ELTS version of TYPO3 v11 before migrating to v12.
I reverted my changes in master
. All validation classes are now again working for v10 and v11, but not for v12.
@sebastian-meyer Unit and integration tests work again with both Typo3 v11 and v12. Please let me know in case I can help some more.
Thank you very much! I'll review this tomorrow!
@sebastian-meyer I'm glad my changes work for you. Please let me know in case any issues pop up that I missed. Of course, I'll occasionally check the issue list myself in the following weeks.
Changes
The following changes have been implemented:
typo3/cms-scheduler
typo3/testing-framework
to v7, which is compatible with Typo3 v11 and v12TYPO3_MODE
references (see Typo3 Deprecation #92947)TYPO3_MODE not found
, which is not required any moreSolrSearch
implementation by extending fromQuery
class (see Typo3 Breaking #96044)AbstractController
(see Typo3 Deprecation #99615)forward
calls toredirect
in controller classes (see Typo3 Deprecation #92815)ObjectManager
(see Typo3 Deprecation #94619)$GLOBALS["TSFE"]
(see Typo3 Manual)cruser_id
,t3ver_oid
,t3ver_wsid
,t3ver_state
,t3ver_stage
from test fixtures, which are not available in Typo3 v12 any more (see Typo3 Breaking #98024)session_id
length intx_dlf_basket
table, which has more then 32 characters since Typo3 v10.4, see ext_tables.sql for Typo3 frontend module.Todo
The following tasks still need to be done before merging:
solr:9.6
as soon as pull request #1335 is mergedTests
The following tests have been done for a fresh installation of both Typo3 v11 and Typo3 v12:
General
Create default namespaces
,Create structures
,Create metadata
,Create solr rore
onNew Tenant
admin pagekitodo:index
kitodo:reindex --all
kitodo:harvest
kitodo-demo
theme, see belowKitodo Plugins
Kitodo: Collection
Kitodo: Search
Kitodo: List View
, shows facets, facets can be selectedKitodo: List View
Kitodo: PageView
Kitodo: PageView
Kitodo: Navigation
Kitodo: Feeds
Kitodo: OAI-PMH Interface
Kitodo: Table of Contents
Kitodo: Basket
Kitodo: Metadata
Kitodo: Page Grid
Kitodo: Calendar
Unable to test
Kitodo: Statistics
Kitodo: Embedded 3d Viewer
Kitodo: AudioPlayer
Kitodo: Toolbox
Kitodo: Basket
(pdf generation)Unfortunately, I do not have access or experience with a production system of
kitodo-presentation
. Because of that, I'm not sure whether some of the issues are the result of a misconfiguration of my Typo3 installation. All problems listed above also occur with the current master and my Typo3 installation. I would appreciate any help in testing my changes or tips to correctly set up Typo3 pages and Kitodo-Presentation plugins for testing.Demo
Demonstration of
kitodo-presentation
updated for Typo3 v12 with demo theme (please ignore CSS problems)https://github.com/user-attachments/assets/03de016a-9ef4-444c-a52e-28ab6d7add3c