blocks|key|4967695|text|我也遇到过同样的问题。Laravel只显示了“哇，看起来出了什么问题。”但是这一行并没有显示出实际的错误。然后，我检查了app/config/app.php文件，并将"debug"+=>+false更改为"debug"+=>+true，它工作得很好。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4967696|你说你也这样做了，但还是不工作。我建议您为您的项目运行一个composer+update命令，然后重试。|4967697|entityMap^0|2B|G|2U|F|0|T|F|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|R|8|@]|D|@]|E|$]]]|I|$]]

I have faced the same problem. Laravel was showing only "Whoops, looks like something went wrong." but this line and not showing the actual error. Then I have checked the app/config/app.php file and changed <code>"debug" =&gt; false</code> to <code>"debug" =&gt; true</code> and it worked perfectly.

You said that you have also done it and still not working. I suggest you to run a <code>composer update</code> command for your project and then try again.

blocks|key|4968050|text|要确保您的应用程序处于开发模式，请编辑bootstrap/start.php，在detectEnvironment函数中只需输入您的机器名称即可。在linux上，使用hostname+terminal命令确定您的机器名称。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4968051|$env+=+$app->detectEnvironment(array(
++'local'+=>+array('homestead',+'Jeanphi'),
));|code-block|syntax|javascript|4968052|entityMap^0|J|J|14|H|2B|8|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|T|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|U|8|@]|D|@]|E|$]]]|L|$]]

To be sure your app is in development mode, edit <code>bootstrap/start.php</code>, in the <code>detectEnvironment</code> function simply put your machine name. On linux use <code>hostname</code> terminal commande to determine your machine name.

<pre><code>$env = $app-&gt;detectEnvironment(array(
 'local' =&gt; array('homestead', 'Jeanphi'),
));
</code></pre>

blocks|key|2042775|text|实际上，当我在app/config/app.php中设置'debug'+=>+true时，调试对我来说工作得很好。当我在app/config/APP.php中设置了这个开关时，它会告诉Laravel打开呼呼并绕过'compiled.php‘文件。当它被禁用时，呼呼将不显示。取而代之的是提供正常的服务器错误页面。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2042776|你还在期待别的什么吗？|2042777|编辑:也许你指的是“调试”，就像L3+(Anbu)中的老分析器栏一样。在这种情况下，我建议您安装this+package|2042778|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/juy/profiler^0|S|F|0|0|1C|C|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|U|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|V|8|@]|D|@$9|W|A|X|1|Y]]|E|$]]|$1|J|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|K|$L|$5|M|N|O|E|$P|Q]]]]

Actually debugging is working fine for me with L4.0.7 when i set <code>'debug' =&gt; true</code> in app/config/app.php
That switch tells Laravel to turn on Whoops and to bypass the 'compiled.php' file. When it is disabled, Whoops will not show. A normal server error page is served instead.

Were you expecting something else?

EDIT: maybe you are referring to "debugging" as the old profiler bar that were in L3 (Anbu). In that case I suggest you install <a href="https://github.com/juy/profiler" rel="nofollow">this package</a>

blocks|key|2855045|text|检查你没有按照fideloper在评论中建议的那样重命名你的app/config文件夹。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2855046|例如，您可能已将其重命名，以防止在将站点复制到其他位置时覆盖默认配置设置。|2855047|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Check you haven't renamed your app/config folder as fideloper suggests in the comment. 

For example you might have renamed it to prevent overwriting the default config settings when copying your site somewhere else.

blocks|key|4967852|text|值得一提的是，我在部署之后收到了这个错误，因为我没有创建这些文件夹：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4967853|/app/storage/cache
/app/storage/logs
/app/storage/meta
/app/storage/sessions
/app/storage/views|code-block|syntax|javascript|4967854|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

For all it's worth, I was getting this error now after deployment because I didn't create these folders:

<pre><code>/app/storage/cache
/app/storage/logs
/app/storage/meta
/app/storage/sessions
/app/storage/views
</code></pre>

blocks|key|4967883|text|某些更改需要重新启动apache才能生效。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4967884|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Some changes need an apache restart to take effect.

blocks|key|4967914|text|在将debug和其他一些配置选项分离到一个单独的(dev.php)配置文件中后，我最近遇到了一个问题。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4967915|事后看来显而易见的，按逻辑模糊的解决方案：不要将+debug+移出配置/app.php|BOLD|4967916|entityMap^0|2|5|0|L|3|P|5|V|C|P|5|0^^$0|@$1|2|3|4|5|6|7|K|8|@$9|L|A|M|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|N|8|@$9|O|A|P|B|H]|$9|Q|A|R|B|H]|$9|S|A|T|B|H]|$9|U|A|V|B|C]]|D|@]|E|$]]|$1|I|3|-4|5|6|7|W|8|@]|D|@]|E|$]]]|J|$]]

I came across problem recently, after separating out <code>debug</code> and a few other config options into a separate (dev.php) config file.

The in-hindsight obvious, by-logic obscure solution: Don't move <code>debug</code> out of config/app.php

blocks|key|4967953|text|虽然我的应用程序处于调试模式，但也有同样的问题。在我的例子中，我是在服务器上部署的，要实现这一点，您必须处理detectEnvironment变量。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|4967954|它位于bootstrap/start.php|4967955|$env+=+$app->detectEnvironment(array(

+++++++'local'+=>+array('your_server_name'),

));|code-block|syntax|javascript|4967956|按照文档中的说明：|4967957|http://laravel.com/docs/4.2/configuration|4967958|entityMap|0|LINK|mutability|MUTABLE|url^0|1I|H|0|3|J|0|0|0|0|15|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|10|8|@$9|11|A|12|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|13|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|14|8|@]|D|@]|E|$]]|$1|O|3|P|5|6|7|15|8|@]|D|@$9|16|A|17|1|18]]|E|$]]|$1|Q|3|-4|5|6|7|19|8|@]|D|@]|E|$]]]|R|$S|$5|T|U|V|E|$W|P]]]]

Had that same problem altought my app was in debug mode.
In my case I was deploying on server,and to make that work 
you must take care of detectEnvironment variable.

It is located in bootstrap/start.php

<pre><code>$env = $app-&gt;detectEnvironment(array(

 'local' =&gt; array('your_server_name'),

));
</code></pre>

as it's instructed in the docs :

<a href="http://laravel.com/docs/4.2/configuration" rel="nofollow">http://laravel.com/docs/4.2/configuration</a>

blocks|key|2042922|text|我有几次同样的问题，我有两种可能性。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2042923|2042924|文件夹存储没有正确的权限，您应该使用chmod+755或chmod777|unordered-list-item|2042925|2042926|+public/index.php+has+none+permission+or+a+777|2042927|2042928|这两个选项我以前就想到过，也许还有更多。|2042929|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|O|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|P|8|@]|9|@]|A|$]]|$1|F|3|-4|5|E|7|Q|8|@]|9|@]|A|$]]|$1|G|3|H|5|E|7|R|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|S|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|T|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|M|$]]

I had the same problem several times and I have two possibilities.

<ul>
<li>the folder storage doesn't have the right permissions, you should use chmod 755 or chmod 777</li>
<li>the public/index.php has none permission or a 777</li>
</ul>

These two options has occurred to me before, maybe there are some more.

blocks|key|138340|text|我也有同样的问题...首先，laravel使用apache在windows上运行良好。然后，当我使用ubuntu和nginx时，它显示“哇，看起来出了什么问题。”|type|unstyled|depth|inlineStyleRanges|entityRanges|data|138341|在php日志中没有错误，在laravel日志中也没有找到任何东西..|138342|因此，我尝试将路径文件夹权限修改为0777|138343|138344|+sudo+chmod+-R+0777+{将您的文件夹应用程序文件夹放在此处}|blockquote|138345|138346|138347|它起作用了|138348|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]|$1|G|3|H|5|I|7|T|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|U|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|V|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|W|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|O|$]]

i got same problem with that...
first, laravel run well on windows using apache..
then while i'm using ubuntu and nginx, it shows "Whoops, looks like something went wrong."

no error in php log and nothing found on laravel log..

so i tried modify path folder permission to 0777

<blockquote>
 sudo chmod -R 0777 {put your folder application folder here}
</blockquote>

it works

blocks|key|4968086|text|您需要清除配置缓存，并在每次更改配置文件时重新生成配置缓存|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4968087|在控制台中运行'php+artisan+config:cache‘就可以了|4968088|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

well you need to clear configuration cache and regenerate it each time you change config files

run 'php artisan config:cache' in console and your good to go

It's extremely frustrating that I have 'debug' => true in the app config but all Laravel is showing is "Whoops, looks like something went wrong." For the love of coding, does somebody know how to get debugging to work?

Laravel 4 debugging not working

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

非常令人沮丧的是，我在应用程序配置中设置了'debug‘=>为真，但Laravel显示的只是“哇，看起来出了点问题。”出于对编码的热爱，有人知道如何让调试正常工作吗？

问Laravel 4调试不起作用
EN

回答 11

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Laravel 4调试不起作用EN

回答 11

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Laravel 4调试不起作用
EN