Download the PHP package stellarwp/plugin-absorber without Composer
On this page you can find all versions of the php package stellarwp/plugin-absorber. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package plugin-absorber
Plugin Absorber
Safely load bundled WordPress plugins inside a host plugin — togglable or always-on — without re-declaration fatal errors.
Requires PHP 7.4+ and WordPress 6.4+.
Install
Use Strauss — two plugins shipping different versions of this library will collide otherwise. Installing has the one prefixing rule you must not get wrong.
Quick start
The container is required, and any StellarWP ContainerInterface implementation will do — the one
you already hand to Telemetry or Uplink.
If your plugin can run on multisite, add
Config::set_host_plugin_basename( plugin_basename( __FILE__ ) ). It is a no-op off a network, so set
it unconditionally: it stops the library deactivating a network-active standalone when your host
plugin is not itself network-activated, which would leave the network's other sites with no copy of
it at all.
Keep the , 0. Anything below plugins_loaded priority 5 wires cleanly; priority 0, in the
block that owns your container rather than a service provider, is the recommendation. Booting at 5
or later still works, with the whole sequence running inline and reported through
_doing_it_wrong(). Configuration explains both, and closes with a complete
bootstrap — two sub-plugins, every optional key.
Docs
- Installing — Composer, Strauss, and the constants Strauss must leave alone.
- Configuration — the hook prefix, the container, every sub-plugin key.
- Recipes — a settings toggle, a manifest of add-ons, and staging the absorption across releases.
- Git history — a script that brings the standalone's commits and blame across with its code.
- Conflict handling — the policies, when they run, and the guard's limits.
- Filters — the runtime overrides for policies and notice text.
- Actions — what the library reports as it loads and skips.
- Notices — where the queue lives, who may see it, and how to render it yourself.
- Extending — swapping out a piece of the library.
- Tests — running the suite, the fixtures and traits it offers, and every scenario it drives the library through.
docs/ and tests/ are both export-ignored, so neither ships in a vendored copy — these links
point at the repository rather than at paths that would be missing beside the installed source.
License
This program is free software; you can redistribute it and/or modify it under the terms of the
GNU General Public License as published by the Free Software Foundation; either version 2 of the
License, or (at your option) any later version. See LICENSE.
