WordPress creates a .maintenance file during the update process which indicates that your site is in the maintenance mode. Unless this file is removed your site will remain in the maintenance mode and your users will continue to see the notification. Once you have updated WordPress, all you have to do is delete .maintenance file … Read more
In your specific case, I don’t think the answer is a technical one (see my comment on the question for more details). For everyone else, the answer to “How can I easily verify a core or plugin update has not broken anything?” is automated testing. That’s the whole purpose of automated testing, because it’s unreasonable … Read more
Yes there is. But it is primarily meant for short interruptions (such as during upgrades) and not very user-friendly. WP creates .maintenance file in root (with timestamp info about time) to trigger it and removes after it is done. See WordPress Maintenance Mode Without a Plugin for reference. In practice using a plugin is usually … Read more
It works for the whole network, not for a specific sub site. Basically that mechanism is intended to be used when there is a software upgrade, time in which you don’t want to have visitors on the site that might result in some data corruption (especialy logged in users, but not only).
Twitter and other high-volume sites probably do this one layer ahead of the servers. Probably with a load balancer that can detect the server load over all servers and if the load is too high (when machines stop replying) they redirect traffic to a server that returns only the “fail whale” page. This answer on … Read more
You could try to change it through the environment variable: WP_CLI_CACHE_DIR as we have it included in the WP_CLI::get_cache() method (src): $dir = getenv( ‘WP_CLI_CACHE_DIR’ ) ? : “$home/.wp-cli/cache”; You can also check out issue #1848 – Use shared cache directory for multiple installs for usage examples. In the WP-CLI Handbook on make.wordpress.org, we have … Read more
When WordPress goes into maintenance mode, it adds a file named .maintenance to the root directory while the maintenance is being performed, then it’s removed afterwards. You can write a function inside your theme’s functions.php that checks for this file and loads a custom maintenance page from the theme. if ( ! function_exists( ‘wpse84987_maintenance_mode’ ) … Read more
You can actually do this from inside WordPress itself, instead of needing to come up with a confusing and overengineered .htaccess fix. We can hook into the template_redirect filter, which only fires on the front-end (not in wp-admin). We then use the is_page() function to check if we’re viewing a page with the ID of … Read more
WordPress has an embedded feature for handling maintenance mode. When you upgrade a plugin, or WordPress core from WP dashboard, WordPress enters maintenance mode: it tries to load a file named maintenance.php located in the content folder (usually /wp-content), and if that file is not there, WP shows a default message. I suggest you use … Read more
Not really. .maintenance is a temporary file, not viable if you want to put your site in maintenance mode for a long time. If you look at source the maintenance mode is maintained only if $upgrading variable defined in the file is no older than 10 minutes. It means .maintenance is a sort of lock … Read more