Releases: balbuf/composer-wp
Fix method signature
Fix variable reference that prevented proper error handling
v1.2.5 Fix variable reference
Trust SSL cert for built-in repos by default
Allows SVN repos to be configured so that their certificates are automatically trusted. This fixes an issue where composer would just fail as it was not able to proxy the question from SVN about whether to trust the certificate.
All built-in SVN repos are set to be trusted; user-defined repos will have to be explicitly set to be trusted in their config OR the user must run svn ls $URL and permanently trust the host for the SVN repo to work.
Fixes #9
Fix incompatibility with newer composer updates
Allows the RepositoryConfig objects to be handled as if they were arrays, which composer assumes they are within the RepositoryManager class.
Fix installers precedence logic so Composer-WP installer plays nicely with others
Adds a custom InstallerManager class that helps better pick which installer to use when it comes to Composer-WP package types.
Correct method signature to be compatible with composer 1.0.0
ComposerRepository::whatProvides() has added a new argument - method signatures are now compatible but new argument has yet to be implemented.
Update mu-plugins autoloader to include a function that fixes some inaccurate plugins_url() calls
Some plugin authors make the reasonable (but inaccurate) assumption that their plugin files reside within the plugins directory, so they use plugins_url() by just passing the directory name of their main plugin file. This addresses that and allows these plugins to work inside of the mu-plugins directory.
Fix package name resolving for plugins of wp-zip repo type
Using the main plugin file's filename is not reliable, as the plugin author may use something generic like "index.php".
Give more control over composer autoloader path
The path can now be specified explicitly in composer.json or within the WordPress instance with the COMPOSER_AUTOLOADER constant. See readme for further details.