SaffireTech

Disable All WordPress Updates and Theme Editors is a handy tool that allows you to not only disable all types of WordPress updates but also allows you to disable WordPress theme and plugin editors.
So, this plugin is developed with an intention to prevent all types of accidental modifications that can happen on your site without your knowledge thus keeping your site safe all the time.
By default, all types of automatic updates are enabled on WordPress – Be it plugin, theme and even WordPress itself. All of these updates happen automatically in the background without requiring your consent or permission. Although it is always advised to keep WordPress updated, during an automatic update, your site can undergo a lot of changes to a point that can even break your site. And the last thing you want is that your customers see a broken version of your site. So it is always advisable to plan updates carefully by testing them on a staging environment first and then deploying them on the live site.
Apart from the updates, there are times when an amateur developer working on your site can try editing files directly from your dashboard using theme editor or plugin editors offered by WordPress. Sometimes changes made through these editors can badly break your site.
As a bonus, we also added a functionality that allows you to Disable WordPress’s default Gutenberg block editor and Manage Debug mode on WordPress This plugin uses the highly reliable and tested <a href="https://github.com/wp-cli/wp-config-transformer" rel="nofollow ugc">wp-cli/wp-config-transformer</a> command for writing constants to wp-config.php.
This plugin serves as a single solution to five major problems on your WordPress site. Thus saving you effort and time to install and configure multiple extra plugins to accomplish all of these! This plugin allows you to disable or manage –
<ul>
<li>Disable All major and minor updates of WordPress.</li>
<li>Disable All theme & plugin updates.( Automatic & Manual)</li>
<li>Disable Theme editor and plugin editor.</li>
<li>Disable Gutenberg block editor.</li>
<li>Debugging mode on your WordPress site.</li>
</ul>
HIRE THE EXPERTS
Need a tailor-made solution for WordPress that solves complex business problems? Our team of experienced developers have helped many businesses like yours to accomplish these goals. <a href="https://www.saffiretech.com/wordpress-development-services" rel="nofollow ugc">Find out more</a>.
Keep up to date with ‘Disable All WordPress Updates and Theme Editors’ by <a href="https://www.saffiretech.com/blog" rel="nofollow ugc">subscribing to the newsletter</a>, <a href="https://twitter.com/saffiretech" rel="nofollow ugc">following us on Twitter</a> and <a href="https://www.facebook.com/saffiretech" rel="nofollow ugc">liking us on Facebook</a>.
If you enjoy using the software <a href="https://wordpress.org/support/plugin/disable-automatic-updates-and-theme-editors/reviews/" rel="ugc">we’d love it if you could give us a review!</a>

Disable All WordPress Updates and Theme Editors

Disable All WordPress Updates and Theme Editors is a handy tool that allows you to not only disable all types of WordPress updates but also allows you …

Andy Fragen

Ari Stathopoulos

Colin Stewart

Paul Biron

This is a feature plugin is for testing Rollback Auto-Update, aka Rollback part 3. This feature only protects plugins during the auto-update process.
As part of the normal Rollback process, the currently installed version of the plugin is moved to <code>wp-content/upgrade-temp-backup/plugins</code>. An active plugin is checked to ensure it doesn’t cause a PHP fatal error when visiting the site. An inactive plugin is not checked because it cannot cause your site to white screen.
Rollback parts 1 was merged into WordPress 6.2 as the <code>move_dir()</code>. Rollback part 2 was merged into WordPress 6.3 and protects the manual update process of plugins and themes.
<ul>
<li><a href="https://core.trac.wordpress.org/changeset/53578" rel="nofollow ugc">r53578</a></li>
<li><a href="https://core.trac.wordpress.org/changeset/55204" rel="nofollow ugc">r55204</a></li>
<li><a href="https://core.trac.wordpress.org/changeset/55219" rel="nofollow ugc">r55219</a></li>
<li><a href="https://core.trac.wordpress.org/changeset/55220" rel="nofollow ugc">r55220</a></li>
<li><a href="https://core.trac.wordpress.org/changeset/55223" rel="nofollow ugc">r55223</a></li>
<li><a href="https://core.trac.wordpress.org/changeset/55720" rel="nofollow ugc">r55720</a></li>
</ul>
<h3>Testing</h3>
<ul>
<li>Requires WordPress 6.3</li>
<li>This only works on auto-updates.</li>
<li>Run the following commands from the terminal. You might need to run the command several times to get it started: 
wp cron event run wp_version_check</li>
<li>When updating a plugin, you should be able to see the old plugin in the <code>wp-content/upgrade-temp-backup/plugins/PLUGINNAME</code> folder. The same should apply for themes. Since updates sometimes run fast and we may miss the folder creation during testing, you can simulate an update failure to demonstrate.</li>
<li>When a plugin auto-update fails, the previous version should be restored. To test that, change the version of a plugin to a previous number, run the update, and on fail the previous version (the one where you changed the version number) should still be installed on the site. To simulate an update failure and confirm this works, use the built-in Simulate failure link. Just activate/deactivate from the <code>plugins.php</code> page action link. This link will only be present if the plugin has an update pending.</li>
</ul>
<h3>Reporting</h3>
Please submit <a href="https://github.com/afragen/rollback-update-failure/issues" rel="nofollow ugc">issues</a> and <a href="https://github.com/afragen/rollback-update-failure/pulls" rel="nofollow ugc">PRs</a> to GitHub.
Logo from a meme generator. <a href="http://hyperboleandahalf.blogspot.com/2010/06/this-is-why-ill-never-be-adult.html" rel="nofollow ugc">Original artwork</a> by Allie Brosh.

Rollback Auto Update

A feature plugin now only for testing Rollback Auto Update, aka Rollback part 3. Manual Rollback of update failures has been committed in WordPress 6.

Disable All WordPress Updates and Theme Editors vs Rollback Auto Update