Haris Amjed

<p>The Version Control Your Content plugin provides an alternative to the native WP <a href="https://wordpress.org/documentation/article/revisions/" rel="ugc">Revisions</a> feature using Git services.</p>
<h4>Requirements</h4>
<ul>
<li>A GitHub account. If you don’t have one, you can create one <a href="https://github.com/join" rel="nofollow ugc">here</a>.</li>
<li>A GitHub private repository. If you don’t have one, you can create one <a href="https://github.com/new" rel="nofollow ugc">here</a>.</li>
<li>(Optional but highly recommended) A GitHub fine-grained personal access token. If you don’t have one, you can create one <a href="https://github.com/settings/tokens/new" rel="nofollow ugc">here</a>.</li>
</ul>
<p>This plugin provides an option for version control in the following places for now:</p>
<ol>
<li>Block Editor (Gutenberg)</li>
<li>Classic Editor</li>
<li>Additional CSS in the Customizer</li>
<li>Default Settings pages in WP Admin</li>
</ol>
<p>On all supported pages, you will see a “Version Control” box, and you can activate or deactivate it for that page. It will also show you the real-time GitHub API usage in the top admin bar.</p>
<p>This solution will put minimal load on your server because there will be no database entries, no complex SQL operations, and only simple JavaScript-based API calls to external Git services.</p>
<h4>How it works behind the scenes?</h4>
<ol>
<li>When you submit any HTML form, such as saving a post, it captures the form data via JavaScript before sending it to the server backend.</li>
<li>It sanitizes the data and converts it to JSON format (if needed).</li>
<li>It sends that JSON or HTML data to your Git repository via a commit.</li>
<li>In this way, all your changes will be new commits in your Git repo in related JSON or HTML files.</li>
<li>In the commits box, a list of all commits will be shown. It will also provide an option to view the changes or revert to that version.</li>
</ol>
<h4>Planned Upcoming Features</h4>
<p>Currently, I have developed it for three views as described above, and the following features will be added in the future:</p>
<ul>
<li>Integration with page builders like Elementor, Divi, Beaver Builder, WPBakery, etc.</li>
<li>Integration with WooCommerce</li>
<li>Integration with BuddyPress</li>
<li>Integration with bbPress</li>
<li>Integration with WPML, etc.</li>
</ul>


Version Control Your Content

Provides an alternative to the native WP Revisions feature using Git services. Also works for Additional CSS and wp-admin Settings pages.

Vishal Paswan

<p>Version Locker lets you lock specific plugins and themes to their current version. Once locked, they won’t update automatically or manually until you unlock them.</p>
<p>Useful for keeping your site stable when you have customized plugins, client sites, or production environments where you need control over when things update.</p>
<h3>What It Does</h3>
<ul>
<li>Lock individual plugins to prevent updates</li>
<li>Lock individual themes to prevent updates</li>
<li>Block all plugin updates at once (global killswitch)</li>
<li>Block all theme updates at once (global killswitch)</li>
<li>Block WordPress core updates (global killswitch)</li>
<li>Quick toggle locks on/off without page reload</li>
<li>Bulk lock or unlock multiple items</li>
<li>Email alerts when locked items try to update</li>
<li>Search and filter your plugins and themes</li>
<li>Activity log showing who locked what and when</li>
<li>Works on Multisite (each site has its own locks)</li>
</ul>
<h3>How It Works</h3>
<p>The plugin uses WordPress filters to hide update notifications and block update attempts. It doesn’t modify any plugin or theme files.</p>
<h3>Credits</h3>
<p>Thanks to <a href="https://profiles.wordpress.org/nemai/" rel="nofollow ugc">Nemai Naskar</a> for testing and feedback on 1.2.2.</p>


Version Locker

Lock plugin and theme updates to prevent accidental or automatic updates. Simple, secure update control for WordPress.

Version Control Your Content vs Version Locker