Bug #90121
closedEditor with syntax highlighting (t3editor) - Malformed UTF-8 characters ERROR
0%
Description
Hey i get this weird error when i click on "Edit page properties", immediately after that error is writen in error log:
Core: Exception handler (WEB): Uncaught TYPO3 Exception: #1504972434: Unable to encode data to JSON in TYPO3\CMS\Core\Http\JsonResponse: Malformed UTF-8 characters, possibly incorrectly encoded | InvalidArgumentException thrown in file /var/www/typo3/typo3_source/typo3_src-9.5.13/typo3/sysext/core/Classes/Http/JsonResponse.php in line 105. Requested URL: https://www.domain.si/typo3/index.php?route=%%2Fajax%%2Ft3editor%%2Fcodecompletion%%2Fload-templates&token=--AnonymizedToken--&pageId=58
Full error trace in attachment.
I get this on multiple TYPO3 sites
TYPO3 9.5.13
PHP 7.2
Files
Updated by Rene Tobias almost 5 years ago
When i disable t3editor extension everything works fine.
Updated by Peter Linzenkirchner almost 5 years ago
I can confirm this: TYPO3 9.5.13, every time when saving a typoscript window with active t3editor.
Updated by Bastian Bringenberg almost 5 years ago
- Project changed from 9 to TYPO3 Core
- TYPO3 Version set to 9
Moved to correct project.
Set correct TYPO3 Version.
Updated by Riccardo De Contardi over 4 years ago
I tried the following test with 9.5.14 (php 7.2.21)
- edit a page
- go to resource tab and write something in the TSConfig field (syntax highlighter is active)
- save, close
Results:
No error reported in System > Logs
Is a different test necessary?
Updated by Rene Tobias over 4 years ago
I can confirm that with TYPO3 9.5.14 problem disappeared. When i switch back to 9.5.13 it appears again.
Updated by Riccardo De Contardi over 4 years ago
@René Fritz Tobias Tobias thank you for your quick reply; may I close your issue or is there still something to do here?
Updated by Riccardo De Contardi over 4 years ago
- Status changed from New to Closed
I close this issue as requested by the reporter; if you think that this is the wrong decision or experience the issue again, please reopen it or open a new issue with a reference to this one.
Thank you.
Updated by Katharina Strasser about 4 years ago
The problem is still present in 9.5.20