Bug #85692
closed
UriBuilder::buildBackendUri() ignores "pageType"
0%
Description
When I create links to actions in the backend using the Fluid view-helper Link\ActionViewHelper, the pageType is ignored.
CURRENT BEHAVIOR:
I want to create a custom CSV download, which does not match any views presented in the backend. To prevent TYPO3 from writing its BE HTML header and footer into the CSV file, I created a custom page type for CSV files according to this documentation: https://docs.typo3.org/typo3cms/ExtbaseFluidBook/8-Fluid/2-using-different-output-formats.html using disableAllHeaderCode = 1.
But when I create links to Extbase actions in the backend, the pageType parameter is ignored. This is even mentioned in a code comment at the method UriBuilder::buildBackendUri():
The settings pageUid, pageType, noCache, useCacheHash & linkAccessRestrictedPages will be ignored in the backend.
(see:
\TYPO3\CMS\Extbase\Mvc\Web\Routing\UriBuilder.php::buildBackendUri())
This is not further explained, there is no documentation on it and from my point of view, this does not make any sense.
EXPECTED BEHAVIOR:
A) The pageType should not be suppressed at any point.
OR
B) If ignoring pageType has some meaning, the documentation should clearly point out how to create other output-formats for the backend than HTML.
Updated by Wouter Wolters over 5 years ago
- Status changed from New to Rejected
The mentioned line is there for a reason, the backend does not use any of these settings.
Evaluation is not there as these settings are for frontend only.
I suggest you to ask your question on StackOverflow to get an example how to output different content.
Per action you can define other output formats than HTML
Thanks.
Updated by Feeela no-lastname-given over 5 years ago
- Category changed from Extbase to Documentation
- Complexity set to easy
@Wouter Wolters wrote:
The mentioned line is there for a reason, the backend does not use any of these settings.
Evaluation is not there as these settings are for frontend only.
In that case this issue is still valid, as mentioned above under “EXPECTED BEHAVIOR”:
“B) If ignoring pageType has some meaning, the documentation should clearly point out how to create other output-formats for the backend than HTML.”
There is no such hint in the official documentation – is not even a note on different behaviors of Extbase between FE an BE. But instead of fixing the docs you advice me to forget about the TYPO3 documentation and ask questions on SO. This seems weird to me.
I changed the topic of this issue from “Extbase” to “Documentation” to emphasize the above.