Dependency Management
The Dependency Management card lets you browse Packagist and install PHP packages directly from your WordPress admin, without SSH access.
Where packages are stored
Section titled āWhere packages are storedāLoopress maintains its own composer.json under wp-content/lps/. Installed packages land in wp-content/lps/vendor/. This location is separate from the plugin itself so packages survive plugin updates and can be used anywhere on the site via the Composer autoloader.
wp-content/ lps/ composer.json ā managed by Loopress vendor/ autoload.php ā require this in your snippets guzzlehttp/guzzle/ ...Installing a package
Section titled āInstalling a packageā- Type the package name or a keyword in the Search a Composer package field (minimum 2 characters)
- Select the package from the dropdown
- Choose a version (compatible versions are pre-selected automatically based on your PHP version)
- Click Install
Version compatibility indicators:
| Icon | Meaning |
|---|---|
| š¢ | Compatible with your PHP version |
| š“ | Requires a different PHP version |
| ā | No PHP constraint declared |
Removing a package
Section titled āRemoving a packageāIn the Installed Packages card, click Remove next to the package you want to uninstall.
The Repair action runs composer update against wp-content/lps/composer.json. Use it when:
- The autoloader is missing after a server migration
- The lockfile has drifted from
composer.json - A previous install left the dependencies in an inconsistent state
The autoload error banner at the top of the page appears automatically when Loopress detects a missing or broken autoloader and prompts you to run Repair.
- All write operations (install, remove, repair) are blocked on production environments.
- Composer is executed in-process (via the
composer/composerlibrary). Long-running installs extend the PHP execution time limit to 5 minutes automatically. - Only stable versions are shown in the version picker (no
dev-*releases).