Task #104695
closed[DOCS] Add missing html template view statement in BarChartWidget.rst
0%
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
Updated by Gerrit Code Review 3 months ago
- Status changed from New to Under Review
Patch set 1 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/85722
Updated by Garvin Hicking 3 months ago
- Category set to Backend API
- Status changed from Under Review to Needs Feedback
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?
Updated by Garvin Hicking 3 months ago
- Status changed from Needs Feedback to Closed
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. :-)