Retroactively creates a composer.json for a WordPress site. On activation, a composer.json menu appears in the admin area under the Tools menu. This page shows a composer.json that will generate a website close or identical to the site the plugin is installed on.
Includes support for composer packages via:
- private mercurial repositories
- private git repositories
- private svn repositories
- non-composer plugins residing in git/svn/mercurial repositories
Install as a regular plugin and then run
composer install on the
wp-content/plugins/composerpress' plugin folder to install dependencies.
Currently ComposerPress does not perform any control towards wpackagist #2 (or similaries), leaving open these problems:
- when a TextDomain doesn't match a Plugins Name ?
- when a plugin doesn't match its Folder Name ?
- when a Plugin is Custom to a site (ie doesn't exist in the wp.org repo) ?
Keep in mind
At present, if composerpress can not find the source of a plugin, the choice will fall back on the default "composerpress" (to help you recognize them and act accordingly)
If you encounter a false positive try to contact plugin's author and ask him to insert, at least, a
Plugin URI:in the header of the plugin; for example: these two plugins could collide if a URI plugin was not specified
Plugin URI: http://wordpress.org/extend/plugins/wp-less/that will become something like composerpress/wp-less
Plugin URI: https://github.com/sanchothefat/wp-less/that will become something like sanchothefat/wp-less
- You can always give an help and contribute...