Laravel 4中的糟糕错误
[英]Whoops error in laravel 4
问题描述
Most of the time i am getting 
大多数时候我都在
"htmlspecialchars() [<a href='function.htmlspecialchars'>function.htmlspecialchars</a>]: Invalid multibyte sequence in argument"
in laravel even for syntax error. 在laravel中甚至出现语法错误。 I didnt understand and I am unable to track the actual error. 我不理解，无法跟踪实际错误。
How can i track the actual error in laravel 4 我如何在Laravel 4中跟踪实际错误
1 个解决方案
解决方案1
0 2013-07-24 14:22:59
It seems to be a encoding issue. 这似乎是一个编码问题。 Be sure to specify the encoding UTF-8 : 确保指定编码UTF-8：
声明:本站的技术帖子网页，遵循CC BY-SA 4.0协议，如果您需要转载，请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.
相关问题
哎呀Laravel升级错误 - Laravel Upgrade Error With Whoops
查看：清除路径：清除后出现Laravel'Whoops'错误 - Laravel 'Whoops' error after view:clear route:clear
哎呀，看起来像出事了。 LARAVEL错误 - Whoops, looks like something went wrong. LARAVEL ERROR
Laravel 5.2 +哎呀 - Laravel 5.2 + Whoops
Laravel whoops 和 class str 未找到 - Laravel whoops and class str not found
使用laravel 5.4项目在浏览器上进行多次刷新时会出现错误“糟糕，好像出了点问题。” - multiple refresh on browser with laravel 5.4 project get error “Whoops, looks like something went wrong.”
哎呀，看起来出事了。 尝试在内置服务器上运行时 Laravel 5 中的错误 - Whoops, looks like something went wrong. error in Laravel 5 when trying to run on built in server
上传 Laravel 项目后，AWS Elastic Beanstalks 在其 url 上显示“哎呀！有错误” - AWS Elastic Beanstalks shows "whoops! there was an error" on its url after uploading Laravel Project
Laravel v5.2.38的错误报告比“糟糕，好像出了点问题”更好。 - Laravel v5.2.38 better error reporting than “Whoops, looks like something went wrong.”
从 xlxs 文件插入 10000 行时，浏览器抛出错误“糟糕，出了点问题” - laravel - Browser throws error “Whoops, something went wrong” when insertin 10000 rows from xlxs file - laravel
相关标签