maksonlee

<p>Content Version for Git stores editable WordPress content snapshots in a configured GitHub repository. It versions posts, pages, terms, and optionally media metadata and original media files. Editors can preview, diff, and restore previous versions from the WordPress admin.</p>
<p>The plugin writes and reads Git objects through the GitHub API. It does not keep a local Git repository and does not call the git CLI.</p>
<p>Features include:</p>
<ul>
<li>Automatic Git versions for normal post and page saves.</li>
<li>Side-by-side content diffs and field diffs.</li>
<li>Full restore and content-only restore modes.</li>
<li>Deleted Resources view for posts, pages, and tracked media.</li>
<li>Restore deleted posts/pages as new drafts and deleted media as new attachments.</li>
<li>Optional media metadata and file tracking.</li>
<li>Manual import of existing posts, pages, and media.</li>
<li>Version store dashboard with branch, latest commit, tracked file count, and GitHub version store status.</li>
<li>Direct GitHub API commits without a local Git worktree.</li>
</ul>
<h3>External Services</h3>
<p>This plugin connects to GitHub when the “Enable GitHub version store” setting is enabled and a repository URL, branch, and personal access token are configured.</p>
<p>When enabled, the plugin writes Git commits directly to the configured GitHub repository using the GitHub API. Commit data may include post/page content, metadata, term references, media metadata, and media files if media tracking is enabled.</p>
<p>The GitHub version store is disabled by default. No data is sent to GitHub unless a site administrator enables and configures it. Without the GitHub version store, this plugin does not keep durable local Git versions. GitHub’s terms and privacy policy apply:</p>
<ul>
<li>https://docs.github.com/en/site-policy/github-terms/github-terms-of-service</li>
<li>https://docs.github.com/en/site-policy/privacy-policies/github-privacy-statement</li>
</ul>


Content Version for Git

GitHub-backed version history for WordPress posts, pages, and media.

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.

Content Version for Git vs Version Locker