Version Pilot Pro - Provides an efficient, secure, and user-friendly version update mechanism for non-official WordPress plugins.

Description

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 is a professional add-on for the free "Version Pilot" plugin. You must have the free Version Pilot plugin installed and activated to use this Pro add-on.

Version Pilot Pro extends the core functionality of Version Pilot, transforming it into a more powerful and commercial-ready software distribution platform.

Pro Features:

* Premium Plugin Update Authentication: Introduces a robust authentication mechanism for developers who sell private or premium plugins. This feature allows you to require a license key and/or a user ID for plugin updates, ensuring that only authorized customers receive them. The system is designed to be highly flexible, giving you, the plugin author, complete control over your own validation logic. By using simple WordPress filter hooks, you can integrate with any licensing system, whether it's based on a custom database table, a third-party API, or WordPress user roles. This protects your revenue and provides a seamless, secure update experience for your legitimate customers directly within their WordPress dashboard.

* Minimum Required Version: This Pro feature gives you granular control over the update path by allowing you to set a minimum required version for each new update package. This is essential for managing updates that depend on code from a specific previous version, such as after a major refactor or when a security fix can only be applied to a recent release. When a client plugin checks for an update, the system will now find the newest available version that the client is eligible to install, ensuring a safe and compatible upgrade path for all your users.

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 in Version 2.0:

* Plugin-Centric Workflow: First, add your plugin's core information. Then, add multiple versions to that plugin. This is more intuitive and reduces data redundancy.

* Dedicated Versions List: A new "All Versions" screen gives you a complete history of all releases across all your plugins.

* AJAX-Powered UI: Enable or disable updates directly from the versions list with a single click, no page reload needed.

* Streamlined Process: The "Add New Version" screen is simplified, automatically linking to its parent plugin and requiring only version-specific details.

* Modern Codebase: Fully refactored for better performance, security, and adherence to modern WordPress best practices.

Install the plugin and try the free version, or get more from WowOwn.

Installation

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. Upload the version-pilot-pro folder to the /wp-content/plugins/ directory on your website.

3. Activate the "Version Pilot" and "Version Pilot Pro" plugins through the 'Plugins' menu in WordPress.

4. Navigate to the new "Version Pilot (Pro)" menu in your admin sidebar.

5. Go to "All Plugins" and click "Add New".

6. 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.

7. Return to the "All Plugins" list. Find your plugin and click the "Add New Version" link.

8. Fill in the version-specific details (e.g., Version Number, Package URL, Changelog) and Publish.

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](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.

Screenshots

1. "All Plugins" Management Interface: The main screen to manage all your plugin projects.

2. "All Versions" Management Interface: A complete history of all releases, with filtering and quick status toggles.

3. "Add New Plugin" Screen: The clean interface for adding a new plugin's core information.

4. "Add New Version" Screen: The streamlined process for releasing a new update for an existing plugin.

5. User's Update Experience: The standard WordPress 'Plugins' page showing an update notification for your plugin.

6. "View Details" Modal: The update details pop-up, populated with information served by the Version Pilot API.

Frequently Asked Questions

= 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.