[BUG] Several new regressions (some of them only with DFG Viewer)

[stweil]

Description

The viewer no longer works with newspapers in an installation of latest Kitodo.Presentation with latest dfgviewer and slub-digitalcollections.

TYPO3 shows runtime exceptions. In addition, essential functionality is missing in the document viewer.

• Runtime exception because of missing PHP dependency (fix: [BUGFIX] Add required typo3/cms-reports #1767)
• Runtime exception because of missing type cast (possible fix: [BUGFIX] Add missing type cast #1765)
• Fulltext button and fulltext missing in viewer. Works again in test with code from 2025-12-08.
• Missing dc:calc in dfgviewer, see slub_digitalcollections. Fixed in [BUGFIX] Remove usage of CalcViewHelper slub/dfg-viewer#383.
• Runtime exception because of typed static property, see slub_digitalcollections. Fixed in [BUGFIX] Fix static call to $documentRepository slub/slub_digitalcollections#195.

Reproduction

Install it and try to display a newspaper (years, months, individual issue).

Expected Behavior

No regression.

Environment

• OS version: Debian GNU Linux stable
• TYPO3 version: 12

Additional Context

See my comments for the pull requests slub/slub_digitalcollections#179 and slub/slub_digitalcollections#186 which are responsible for two regressions.

One more regressions remains after reverting these two commits:

Tue, 25 Nov 2025 14:23:47 +0100 [ALERT] request="806b92604d22b" component="TYPO3.CMS.Frontend.ContentObject.Exception.ProductionExceptionHandler":
Oops, an error occurred! Code: 202511251423476245d421- Exception:
Kitodo\Dlf\ViewHelpers\LinkViewHelper::doubleEncode(): Argument #1 ($url) must be of type string, int given,
called in /viewer/vendor/kitodo/presentation/Classes/ViewHelpers/LinkViewHelper.php on line 75
[...]

[stweil]

@markusweigelt, one regression is related to pull request #1749. I could fix it with PR #1765, but maybe you have a better fix.

[stweil]

@markusweigelt, @michaelkubina, there is another regression which seems to exist since end of November according to the CI tests:

Error: Interface "TYPO3\CMS\Reports\StatusProviderInterface" not found

It not only breaks the CI tests: TYPO3 with Kitodo.Presentation no longer worked for me. I could fix it in my installation with composer require typo3/cms-reports typo3/cms-lowlevel which resulted in this patch:

diff --git a/composer.json b/composer.json
index db2b98a..4b9da92 100644
--- a/composer.json
+++ b/composer.json
@@ -33,7 +33,9 @@
                "typo3/cms-impexp": "^12.4",
                "typo3/cms-info": "^12.4",
                "typo3/cms-install": "^12.4",
+               "typo3/cms-lowlevel": "^12.4",
                "typo3/cms-reactions": "^12.4",
+               "typo3/cms-reports": "^12.4",
                "typo3/cms-rte-ckeditor": "^12.4",
                "typo3/cms-seo": "^12.4",
                "typo3/cms-setup": "^12.4",

[stweil]

Error: Interface "TYPO3\CMS\Reports\StatusProviderInterface" not found

Pull request #1767 fixes this CI error for me.

[stweil]

@sebastian-meyer, @markusweigelt, with latest code from kitodo-presentation and dfgviewer, I no longer see the fulltext button and the related fulltext. Instead of it, I now see a new multiview button. This. looks like another regression, either in dfgviewer or in kitodo-presentation.

[sebastian-meyer]

The multiview button should be an additional button, but not a replacement for fulltext. @markusweigelt: Could you please have a look at this?

[stweil]

The multiview button should be an additional button, but not a replacement for fulltext.

Currently it looks like this: https://digital.ladenburg.world/viewer?tx_dlf[id]=5675.

[sebastian-meyer]

The multiview button should be an additional button, but not a replacement for fulltext.

Currently it looks like this: https://digital.ladenburg.world/viewer?tx_dlf[id]=5675.

Yes, that seems to be a bug. Assigning @markusweigelt to review the type cast PR (#1765) and have a look at the missing fulltext button.