you can use template_redirect action hook to php include your maintenance mode template file using a simple option in options database. When you turn maintenance mode on add an option for example: add_option(‘maintenance_mode_on’); then with this code you check if that option is set and if so you redirect to your desired template file: function … Read more
Depends. One argument could be that if the requested page use all sizes then there will be a lot of image calls (slower response, bandwidth etc) but you can bypass that i.e. by loading images with JS. Also more sizes means more disk space usage. I don’t think there is any significant performance concern related … Read more
You can edit the page at any time after it is published. I would not recommend using maintenance mode, as then your entire site will be unavailable while you are editing the page. When you are editing, your site is unaffected until you click “Update” and save the changes to the published post. No users … Read more
It could be easily done by creating .maintenance file in the root of your WordPress instance. Your script should look like this: // create maintenance file before starting the long lasting process file_put_contents( ABSPATH . ‘.maintenance’, ‘<?php $upgrading = ‘ . time() . ‘;’ ); // do stuff … // after finishing working on your … Read more
If you look inside of /wp-admin/includes/update-core.php there is some good info within a comment around line 826. Here are the steps the upgrader should take… Test unzipped location for select files to ensure that unzipped worked. Create the .maintenance file in current WordPress base. Copy new WordPress directory over old WordPress files. Upgrade WordPress to … Read more
I presume WordPress plugins are made by third parties. For the moment, yes; all except for “Hello Dolly!” and “Akismet”, which are part of the core distribution. Do plugins have to be kept up to date with WordPress upgrades? Certainly they should be; but they’re not required to be kept up-to-date. Can plugins become obsolete? … Read more
Using a plugin is always a quick and easy thing to do, until it goes wrong. I am a fan of less plugins (unless you really need them) and more hard-code reason is that you then have full control of what goes into your project. And at the comment on “plugins can become outdated and … Read more
What you have does indeed sound more like production and development. General practice it that between these two the data only goes from production to development, but never the other way. Having true staging, you can push the data from to production, is challenging precisely for the reasons you describe. There are solutions around, but … Read more
Always remove any code you do not use which is easy to remove, like unused plugins and themes. Too many times even an unused code proved to be a vector through which sites were hacked.
Is it safe to delete from db orphaned posts i.e. whose post_parent no longer exists?