Yii部署仅显示空白屏幕

Yii部署仅显示空白屏幕

问题描述:

I'm trying to deploy my Yii website to a Ubuntu 14.10 server, but all I get is a blank screen...

The server is properly setup with the lamp configuration

Steps taken so far:

  • I've uploaded the framework folder to a location that is referenced by the config file

  • I've uploaded my files with index.php to the proper folder

  • I've changed the permissions of the assets and protected/runtime folders to read-write (chmod 777)

  • I've even checked the requirements folder index.php that yii provides. It indicates that everything is all set to go...

I know that the index.php is being properly accessed because I can turn on yii debugging and see the debug messages.

What's really weird is that the log doesn't show an error and the last entry refers the line that does "render" of my index view in the SiteController.

Do you think the permissions of the view folder is wrong? I also checked if it was the htaccess file, but I've tried accessing the site with the htaccess file enabled and disabled with no result.

I have no idea what is going on...I'd greatly appreciate any help you guys can throw my way

我正在尝试将我的Yii网站部署到Ubuntu 14.10服务器,但我得到的只是一个空白屏幕。 .. p>

使用灯泡配置正确设置服务器 p>

目前采取的步骤: p>

    \ n
  • 我已将框架文件夹上传到配置文件引用的位置 p> li>

  • 我用index.php上传了我的文件 到正确的文件夹 p> li>

  • 我已将资产和受保护/运行时文件夹的权限更改为读写(chmod 777) code> li>

  • 我甚至检查了yii提供的requirements文件夹index.php。 它表示一切都已设置为... p> li> ul>

    我知道正在正确访问index.php因为我可以打开yii 调试并查看调试消息。 p>

    真正奇怪的是日志没有显示错误,最后一个条目引用了 SiteController code>中我的索引视图“渲染”的行 。 p>

    您认为视图文件夹的权限是错误的吗? 我还检查了它是否是htaccess文件,但我尝试在启用htaccess文件的情况下访问该站点并禁用该结果。 em> p>

    我没有 想法发生了什么......我非常感谢你们可以帮助我们的任何帮助 p> div>

Just wrapping this up. Alejandro's term of (PHP White Screen of Death) yielded many other topics on stackoverflow.

For those curious, I used the settings from this answer and found out that I was missing dirname(FILE) from all my require_once statements.

Funny thing is that, everything worked on my local dev xampp environment, but needed that dirname for the unix server.

Now I can continue finishing deployment.