tomjn / composerpress Goto Github PK

Retroactively creates a composer.json for a WordPress site

PHP 100.00%

composerpress's Introduction

Composerpress

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:

packagist
wpackagist
private mercurial repositories
private git repositories
private svn repositories
non-composer plugins residing in git/svn/mercurial repositories

Installation Notes

Install as a regular plugin and then run composer install on the wp-content/plugins/composerpress' plugin folder to install dependencies.

For instructions on installing composer: see here for *nix and here for Windows

TODOs:

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... 😄

Author articles

composerpress's People

Contributors

Stargazers

Watchers

Forkers

richaber mathews5 th3architect nitinthewiz kilbourne raruto

composerpress's Issues

Fatal error in gitonomy

Getting this error in plugin's page (after admin menu, no other output):

Fatal error: in C:\server\www\dev\wp-content\plugins\composerpress\vendor\gitonomy\gitlib\src\Gitonomy\Git\Repository.php on line 550

Dumping what $error var holds around there nets this gem:

error while running config output: """git"" �� �� ७�� 譥� ��, �ᯮ��塞�� ணࠬ�� 䠩��. "

Win7x64

Poll WPackagist

Not all plugins are on WPackagist, Composer-press should look at RepositoryInterface::findPackage in the Composer APIs to ascertain if a package is present or not

proc_open

Fatal error: Uncaught Symfony\Component\Process\Exception\RuntimeException: The Process class relies on proc_open, which is not available on your PHP installation. [...]

Could the use of proc_open be avoided?

Export only active plugins to composer.json

We have a lot of inactive plugins but we only wanted to export only the active plugins because those are the ones that are useful to production. Is it possible?

Theme Support

There's no equivalent of WPackagist for themes, but if VCS is present I have the tools to add and install the theme

'wpackagist-plugin' instead 'wpackagist'

composerpress generates the lines with just wpackagist/[...] -
but they had to be changed to wpackagist-plugin/[...] -
otherwise composer cannot find the packages:

[...]
Your requirements could not be resolved to an installable set of packages.

Problem 1
    - The requested package wpackagist/login-lockdown could not be found in any version, there may be a typo in the package name.

Potential causes:
 - A typo in the package name
 - The package is not available in a stable-enough version according to your minimum-stability setting
   see <https://getcomposer.org/doc/04-schema.md#minimum-stability> for more details.

Read <https://getcomposer.org/doc/articles/troubleshooting.md> for further common problems.

Example:
wpackagist/login-lockdown": "v1.7.1",
should be
wpackagist-plugin/login-lockdown": "v1.7.1",

wpackagist package names incorrectly resolved

@tomjn: Thanks for this very helpful plugin! I is a great timesaver for Bedrock based sites.

Some package names are incorrectly resolved. - Examples:

google-analytics-dashboard-for-wp-gadwp should be google-analytics-dashboard-for-wp
text-blocks should be reusable-text-blocks
updraftplus-backuprestore should be updraftplus
wordfence-security should be wordfence
yoast-seo should be wordpress-seo

The plugin name in wordpress.org plugin directory is apparently also used by wpackagist.

'Tomjn\ComposerPress\Model' not found

Plugin could not be activated because it triggered a fatal error:

Class 'Tomjn\ComposerPress\Model' not found in /site/wp-content/plugins/composerpress/plugin.php on line 37

WP Version 4.5.2
Composerpress Version: 1.0