Download the PHP package ultraleet/wp-requirements-checker without Composer
On this page you can find all versions of the php package ultraleet/wp-requirements-checker. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download ultraleet/wp-requirements-checker
More information about ultraleet/wp-requirements-checker
Files in ultraleet/wp-requirements-checker
Package wp-requirements-checker
Short Description Helper library for WordPress plugins to check for minimum PHP and WP versions.
License MIT
Informations about the package wp-requirements-checker
WordPress Requirements Checker
Helper library for WordPress plugins to check for minimum PHP and WP versions.
When there's any version mismatch when your plugin is activated, the library will display notices about required versions on the admin page. It will also automatically deactivate the plugin.
This way, when unsupported PHP language features or WP functionality is used in your plugin, it won't break the site and make it difficult for the admin to fix the issues.
Since version 1.1.0, you can also add in other plugins that your plugin depends on (for instance, when creating an add-on).
Usage
There are multiple ways to use this library, depending on the way you are developing your plugin. The main ones are using Composer, and just including the library manually. You can find instructions for both of these below.
Using Composer
Require the library like so:
In your main plugin file, first make sure that the Composer autoloader is included:
Then, instantiate the library and check the requirements. Make sure you continue loading your plugin only when the check passes:
Note, that only elements with the comment 'Required' are needed for the library to work. You can pick and choose which ones of the other options you want to check for.
Using manual loading
Download the file src/RequirementsChecker.php
from this repository and place it somewhere within your project tree.
Let's say you placed it in the lib
directory in your plugin root. Then include the file in your main plugin file:
The rest of the process is exactly the same as shown above.