Issue Task Closed

#104695[DOCS] Add missing html template view statement in BarChartWidget.rst

TYPO3 GmbH TYPO3com 08/22/24, 10:24 updated 08/22/24, 11:37

Description

Encountered the error:

Core: Exception handler (WEB): Uncaught TYPO3 Exception: #1257246929: Tried resolving a template file for controller action “Standard->widget/ChartWidget” in format “.html”, but none of the paths contained the expected template file (Standard/Widget/ChartWidget.html). No paths configured. | TYPO3Fluid\Fluid\View\Exception\InvalidTemplateResourceException thrown in file /var/www/html/vendor/typo3fluid/fluid/src/View/TemplatePaths.php in line 595. Requested URL: https://mysite.ddev.site:8443/typo3/ajax/dashboard/widget/content?token=—AnonymizedToken—&widget=sysLogErrorsMyWidget

To add the small view statement helped. Seems to be an error when comparing with file cms-dashboard/Configuration/Backend/DashboardWidgets.yaml.

This issue was automatically created from https://github.com/TYPO3/typo3/pull/518

Reviews 2

History 23

  1. Gerrit Code Review pushed patch set 1 for main to change 85722 status New Under Review 08/22/24, 10:24

  2. Garvin Hicking commented and changed category status Under Review Needs Feedback 08/22/24, 11:13

    I am a bit reluctant here to change this in the docs, because I don’t know why $view would be required here?

    The file EXT:dashboard/Configuration/Backend/DashboardWidgets.yaml was removed with
    https://review.typo3.org/c/Packages/TYPO3.CMS/+/84425 and also in the last version of it in v12 I don’t see a ‘$view’ argument in there.

    What exact widget did you create yourself, how can I reproduce the error?

  3. Garvin Hicking commented and changed status Needs Feedback Closed 08/22/24, 11:37

    The issue was:

    • v11 had $view as required argument
    • Docs of v11 did mention $view, but did not list examples
    • v12 and v13 dropped needing $view in the definitions
    • When looking at the v12/v13 examples and trying to use them in v11 context, this will fail

    Issue is fixed by using the matching v11 documentation of this, closing. :-)