Linux 软件免费装

在这里免费安装WordPress以及其他软件

Banner图

Version Pilot - Plugin Update Manager

开发者 wowown
更新时间 2025年9月5日 18:58
PHP版本: 7.0 及以上
WordPress版本: 6.8
版权: GPL v2 or later
版权网址: 版权信息

标签

auto-update self-hosted plugin-updater custom-updater version-control

下载

2.0.0 2.1.0

详情介绍:

Version Pilot offers a decentralized and seamless update solution for WordPress plugin developers who host their plugins outside the official repository. It perfectly mimics the native WordPress update experience without relying on a central server. This solution consists of two parts:
  1. Author-side Plugin ("Version Pilot"): You install this plugin on your own WordPress site. It provides a clean interface to manage all your plugins' update information. This information is then exposed via a secure REST API endpoint.
  2. Client-side Integration Code: A lightweight PHP snippet that you, the developer, embed in your distributed plugins. This code uses WordPress's built-in hooks to periodically check your Version Pilot API for updates. When a new version is detected, it integrates seamlessly into the standard WordPress update system, allowing your users to update with a single click from their admin dashboard, just like any official plugin.
Key Features:

安装:

This plugin has two installation processes: one for you (the plugin author) and one for integrating the updater into your plugins. Part 1: For You (The Plugin Author)
  1. Upload the version-pilot folder to the /wp-content/plugins/ directory on your own website.
  2. Activate the plugin through the 'Plugins' menu in WordPress.
  3. Navigate to the new "Version Pilot" menu in your admin sidebar.
  4. Go to "All Plugins" and click "Add New".
  5. Fill in your plugin's permanent information (e.g., Plugin Name, Plugin Slug, Homepage) and Publish. The "Plugin Slug" must be unique and match the one used in the client code.
  6. Return to the "All Plugins" list. Find your plugin and click the "Add New Version" link.
  7. Fill in the version-specific details (e.g., Version Number, Package URL, Changelog) and Publish.
  8. Optionally, set a "Minimum Required Version" to ensure clients meet compatibility requirements before receiving this update.
  9. Your update API is now live for that version!
Part 2: Integrating the Updater into Your Plugin
  1. Copy the version-pilot-client-updater.php file (from the /client/ directory) into your own plugin's folder.
  2. In your plugin's main PHP file, include and instantiate the updater class.
```php // Include the updater class. require_once dirname( FILE ) . '/path/to/version-pilot-client-updater.php'; // Instantiate the updater. new Version_Pilot_Client_Updater( 'https://your-author-site.com', // The URL where your Version Pilot plugin is installed. 'my-awesome-plugin', // The unique slug for THIS plugin. plugin_basename( FILE ), // The plugin's basename (e.g., my-awesome-plugin/my-awesome-plugin.php). '1.0.0' // The CURRENT version of THIS plugin. ); ``` That's it! Your plugin will now automatically check for updates with advanced version matching.

屏幕截图:

  • **"All Versions" Management Interface**: A complete history of all releases, with filtering and quick status toggles, including the new "Min Client Version" column.
  • **"Add New Plugin" Screen**: The clean interface for adding a new plugin's core information.
  • **"Add New Version" Screen**: The streamlined process for releasing a new update, now with minimum version requirements field.
  • **User's Update Experience**: The standard WordPress 'Plugins' page showing an update notification for your plugin.
  • **"View Details" Modal**: The update details pop-up, populated with information served by the Version Pilot API.

升级注意事项:

2.1.0 Enhanced version with integrated Pro features including advanced version matching, minimum version requirements, and authentication support. Fully backward compatible. 2.0.0 This is a major update that completely refactors the plugin's architecture. It is highly recommended to back up your database before upgrading.

常见问题:

Do my users need to install Version Pilot?

No. That is the main advantage. Your users do not need to install any extra plugins. The update logic is bundled within your own plugin.

Is this secure for my users?

Yes. All communication should be over HTTPS (which you must configure on your server). Furthermore, WordPress itself performs validations on the update package before installation. Version Pilot simply informs WordPress where to get the update.

Will this slow down my users' websites?

No. The update check leverages WordPress's built-in transient API. WordPress only checks for updates twice a day (every 12 hours), so the impact on performance is negligible.

What is the "Minimum Required Version" feature?

This new feature allows you to set compatibility requirements for updates. For example, if you release version 3.0.0 that requires users to be on at least version 2.5.0, you can set this requirement. Users on older versions won't see this update until they manually update to an intermediate version first.

Can I control who gets updates?

Yes! Version Pilot includes built-in authentication support. You can hook into the version_pilot_update_verify filter to implement license verification or other access control mechanisms.

更新日志:

2.1.0 2.0.0 1.0.0