-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JsonView seems not to work #6
Comments
Same here - i think its because JsonView adds header to TypoScriptFrontendController in JsonView::L222 instead adding it to response directly. Maybe because TSFE is initiated in eID script of EXT:routing but headers not parsed there? I worked around like this (because i didnt understand the reason): |
Is problem now fixed for you? |
@xperseguers: I'm currently experiencing the same problem. PR from @SomeBdyElse basically fixed the issue. Could you please release a new version of EXT:routing? |
Either I am doing something wrong or the export via JsonView seems not to work. Each time I call my route the request returned a response with the content-type defined as text/html; charset=UTF-8 instead of application/json.
URLs to browse
or
Configuration/Routes.yaml
or
Both configurations and URLs are not working.
Classes/Controller/BlockController.php
Classes/View/Block/ListJson.php
Output
The text was updated successfully, but these errors were encountered: