blocks|key|959052|text|是的，在你应该先上传的主要idex文件中，放入如下内容：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|959053|<h1>Page+under+update</h1>
<h2>Please+revisit+after+10+minuts</h2>
<?php+die();?>
//+...+Your+code+is+belowe|code-block|syntax|javascript|959054|现在您可以更新其他文件，当更新结束时，从主index.php中删除上面的那些行|959055|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Yes, in Your main idex file witch You should upload first put something like this:

<pre><code>&lt;h1&gt;Page under update&lt;/h1&gt;
&lt;h2&gt;Please revisit after 10 minuts&lt;/h2&gt;
&lt;?php die();?&gt;
// ... Your code is belowe
</code></pre>

Now You can update other files and when it's over remove those above lines from main index.php

blocks|key|243576|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|243577|您可以通过以下方式随时关闭所有错误报告：|ordered-list-item|243578|243579|error_reporting(0);|code-block|syntax|javascript|243580|(老实说，这是一个糟糕的解决方案)。|243581|243582|然而，这可能不是你想要的。另一种消除错误的方法是在行前添加@。所以你可以通过写：|243583|来解决这个问题。|243584|@require_once(FILE)|243585|(再一次-糟糕的解决方案。你不会只想让错误消失)。|243586|243587|您可能希望使用include_once而不是require_once，这将使您能够在文件不在的情况下继续加载页面。|243588|243589|(也许可以做得更好，不是吗？)|243590|243591|最推荐做的事情是先检查file_exists，然后做任何你想做的事情。如果页面对于其余代码是必需的，则您可能希望放置您自己的自定义错误消息，并停止加载页面。|243592|243593|try+{
++++if+(!file_exists('page.php'))+{
++++++++throw+new+Exception('Page+has+not+been+found,+please+try+again+later.');
++++}
++++if+(!@include_once('page.php'))
++++{
++++++++throw+new+Exception('Page+under+construction,+please+try+again+later.');
++++}
}
catch(Exception+$e)+{++++
++echo+$e->getMessage();
}|243594|(我认为这才是真正的事情)。|243595|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|-4|4|5|6|1A|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|1B|7|@]|8|@]|9|$]]|$1|D|3|-4|4|5|6|1C|7|@]|8|@]|9|$]]|$1|E|3|F|4|G|6|1D|7|@]|8|@]|9|$H|I]]|$1|J|3|K|4|5|6|1E|7|@]|8|@]|9|$]]|$1|L|3|-4|4|5|6|1F|7|@]|8|@]|9|$]]|$1|M|3|N|4|C|6|1G|7|@]|8|@]|9|$]]|$1|O|3|P|4|5|6|1H|7|@]|8|@]|9|$]]|$1|Q|3|R|4|G|6|1I|7|@]|8|@]|9|$H|I]]|$1|S|3|T|4|5|6|1J|7|@]|8|@]|9|$]]|$1|U|3|-4|4|5|6|1K|7|@]|8|@]|9|$]]|$1|V|3|W|4|C|6|1L|7|@]|8|@]|9|$]]|$1|X|3|-4|4|5|6|1M|7|@]|8|@]|9|$]]|$1|Y|3|Z|4|5|6|1N|7|@]|8|@]|9|$]]|$1|10|3|-4|4|5|6|1O|7|@]|8|@]|9|$]]|$1|11|3|12|4|C|6|1P|7|@]|8|@]|9|$]]|$1|13|3|-4|4|5|6|1Q|7|@]|8|@]|9|$]]|$1|14|3|15|4|G|6|1R|7|@]|8|@]|9|$H|I]]|$1|16|3|17|4|5|6|1S|7|@]|8|@]|9|$]]|$1|18|3|-4|4|5|6|1T|7|@]|8|@]|9|$]]]|19|$]]

1.
You can always turn off all error reporting by:

<pre><code>error_reporting(0);
</code></pre>

(Well, to be honest - bad solution).

2.
However, that's probably not what you want.
Another way of getting error silenced, is to add @ before the line. So you can solve it by writing:

<pre><code>@require_once(FILE)
</code></pre>

(Again - bad solution. You don't want to just get error silenced).

3.
You maybe want to use include_once instead of require_once, which will give you the ability to continue loading the page even if the file isn't there.

(Probably can do better, nah?)

4.
The most recommended thing to do is to check if file_exists first, and then doing whatever you want to do. If the page is necessary for the rest of the code, you might want to put your own custom error message and stop the loading of the page.

<pre><code>try {
 if (!file_exists('page.php')) {
 throw new Exception('Page has not been found, please try again later.');
 }
 if (!@include_once('page.php'))
 {
 throw new Exception('Page under construction, please try again later.');
 }
}
catch(Exception $e) { 
 echo $e-&gt;getMessage();
}
</code></pre>

(I think that's the real thing).

blocks|key|4791162|text|您是否研究过FTP以外的其他部署选项？许多部署工具，比如通过SSH工作的Capistrano，会将新文件复制到新文件夹中，然后在完成整个上传和更新过程后将current目录符号链接到新文件夹。这确保了原子(全部或全部不更新)更新。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4791163|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/capistrano/capistrano^0|25|7|10|A|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]]|D|@$9|Q|A|R|1|S]]|E|$]]|$1|F|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|G|$H|$5|I|J|K|E|$L|M]]]]

Have you looked into deployment options other than FTP? Many deployment tools like <a href="https://github.com/capistrano/capistrano" rel="nofollow">Capistrano</a>, which works via SSH, copy new files into a new folder, then symlink the <code>current</code> directory to the new folder if and when the whole upload and update process is finished. This ensures atomic (all or nothing) updates.

blocks|key|243639|text|使用符号链接指向您的web应用程序目录，并在您的web服务器配置中引用该符号链接。将所有内容上传到实时web应用程序的不同目录；然后在一切就绪后简单地更改符号链接。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|243640|编辑|offset|length|style|BOLD|243641|或者..。如果您使用APC进行操作码缓存，请上传所有内容，并且原始文件应该仍在操作码缓存中(您应该在生产服务器中禁用apc+stat测试)；然后在上传所有内容后刷新操作码缓存。|243642|entityMap^0|0|0|2|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

Use a symbolic link to point to your web application directory, and reference that symbolic link in your webserver config. Upload everything to a different directory to the live web app; then simply change the symbolic link when everything is in place.

EDIT 

Alternatively.... if you're using APC for opcode caching, upload everything, and the original should still be in the opcode cache (you should have the apc stat test disabled in a production server); then flush the opcode cache when everything has been uploaded.

I've got a website that I do the coding and testing for locally, and when ready I upload the files via FTP to a remote server which can be a little slow at times.

If a user tries to access a page containing a require_once of a page that's currently being uploaded, they will get errors as at that specific moment in time the file appears not to exist or is only partially uploaded. Even if a user tries to access a page directly e.g. example.php they could experience the same problem.

I overcame the require_once issue by creating a custom include function that checks the last line of the file for a marker but this doesn't help for non include pages and is really messy.

Is there a better way to update the site without pissing off the users with errors?

Best way to update a PHP based site without errors

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我有一个网站，我在本地做编码和测试，当准备好时，我通过FTP将文件上传到远程服务器，这有时可能会有点慢。如果用户试图访问包含当前正在上载的页面的require_once的页面，他们将收到错误消息，因为在该特定时刻，该文件似乎不存在或仅部分上载。即使用户试图直接访问页面，例如example.php，他们也会遇到同样的问题...

问无错误地更新基于PHP的站点的最佳方法
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问无错误地更新基于PHP的站点的最佳方法EN