Magento 一页空白
我们明天有黑色星期五促销活动,我们的网站托管在 bluehost 上,并基于 Magento CMS 构建,我们的结帐系统完全是空白的。
当您在购物车中单击“继续结帐”时,ourwebsitedomain.tld/index.php/checkout/onepage/ 为空白。
我们最近对网站进行了一些速度更改,但我们已经撤消了所有这些更改,包括编辑 htaccess 文件,但均无济于事。
我们已经尝试了 Magento 论坛中的所有方法,但没有任何效果。
我们认为这可能是服务器问题,但不幸的是 bluehost 今天没有开放,因为它是 thxgiving,并且我们无法备份或恢复到旧版本的站点,因为我们的服务器“正在维护”。
我们不确定这是否是我们所做的事情,或者是否是服务器问题。
我们将其发送到bluehost:
// 这是我们的想法:
- 也许这是一个SSL问题,因为URL是https:(oursitedomain.tld/index.php/checkout/onepage/是不会拉起的页面,甚至不会重定向)。 ssl 证书没有过期,但是是否还有其他问题?
- 也许我们需要重置另一个服务器配置?你能看看服务器是否还有其他问题吗?
- 我们无法恢复到站点的旧备份,因为 cpanel 中的备份和恢复版本控制台无法工作,说该站点正在维护。至少,我们需要备份网站的旧版本,并使购物车正常工作。 //
任何人的任何想法都将是巨大的。
即使有解决方法,那也没关系。我们正在尝试使用 paypal 或 google 绕过 onepage,但还没有成功。最糟糕的情况是,我们会弹出一个页面,说明结帐已停止,销售推迟到下周等,或者供客户致电。
We have a black friday sale tomorrow and our site is hosted on bluehost, and is built on Magento CMS and our checkout system is totally blank.
When you click "proceed to checkout" when in the shopping cart, ourwebsitedomain.tld/index.php/checkout/onepage/ is blank.
We recently made some speed changes to our site, and we have undone all of those, to no avail, including editing the htaccess file.
We have tried everything in the Magento forums, nothing's working.
We think it might be a server issue, but unfortunately bluehost is not open today because it's thxgiving, and we cannot backup or restore to an old version of the site because our server is "under maintenance".
We are not sure if it is something we have done, or if it is a server issue.
We send this to bluehost:
// Here are our thoughts:
- Maybe it's an SSL issue since the URL is https: (oursitedomain.tld/index.php/checkout/onepage/ is the page that will not pull up, won't even redirect). The ssl certificate has not expired, but coudl there be something else wrong with it?
- Maybe it is another server configuration that we need reset? can you see if there is anything else wrong with the server?
- We cannot restore to an old backup of the site because the backup and restore version console in cpanel is not working, says the site is under maintenance. At the very least , we need to backup an old version of the site, and get the shopping cart working.. //
Any ideas anyone has would be huge.
Even if there is a workaround, that will be fine. We are trying to bypass onepage with paypal or google, but no luck yet. worse case scenario we will throw a page up saying the checkout is down, the sale is postponed until next week, etc, or for customers to call in.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
造成空白页的一个非常常见(但可惜不是唯一)的原因是 PHP 的内存限制。您的 .htaccess 文件应包含如下行:
尝试将此值增加到
512M
。您可以通过在 Magento 文件夹中创建以下 PHP 文件来确认之前和之后的实际设置。然后只需在浏览器中输入这个新页面的地址(例如“ourwebsitedomain/phpinfo.php”)并查找“memory_limit”。
如果你想正确诊断问题,那么就努力消除可能性。转到不带“checkout/onepage”位的“https://ourwebsitedomain/”,如果有显示,那么您就知道这不是 SSL 的问题。
如果管理部分(不是 cpanel)正在运行,那么您可以选择暂时禁用安全“https”地址。使用 Paypal 时,它虽然不那么安全,但不是必需的,如果替代方案错过了一年中最大的购物日,也是可以理解的。
A very common (but, alas, not the only) cause of blank pages is PHP's memory limit. Your .htaccess file should have a line like:
Try increasing this value to
512M
. You can confirm what the actual setting is both before and after by creating the following PHP file in your Magento folder.Then simply type the address of this new page (eg. "ourwebsitedomain/phpinfo.php") in your browser and look for "memory_limit".
If you want to diagnose the problem correctly then work on eliminating possibilities. Go to "https://ourwebsitedomain/" without the "checkout/onepage" bit and if something shows then you know it's not a problem with SSL.
If the admin section (not cpanel) is working then you have the option of disabling the secure "https" address temporarily. It's not as safe but not required when using paypal, also it's understandable if the alternative is missing out on the biggest shopping day of the year.
当 display_errors 关闭时,PHP 页面只会变成空白(由于致命错误)。进入 /index.php 并向下滚动到文件末尾附近。取消注释该行
ini_set('显示错误', 1);
并让我们知道您收到的错误是什么,然后我们就可以从那里开始。
PHP pages only go blank (from fatal errors) when display_errors is turned off. Go into /index.php and scroll down near the end of the file. Uncomment the line
ini_set('display_errors', 1);
and let us know what the error you receive is, then we can go from there.