Skip to content

Plugin migration doesn't correctly copy private plugins to the nucleus dir #1

@MeMattStone

Description

@MeMattStone

Describe the bug
When you run nucleus plugins:migrate plugins that aren't found on the WordPress plugin directory get deleted instead of being moved to the nucleus folder in the project. There is also no message to say that a plugin was private/premium.

To Reproduce
Steps to reproduce the behavior:

  1. Run 'nucleaus plugins:migrate' on a WordPress project
  2. Check for plugins that have not been added to composer.json, they should be moved to ./nucleus/plugins/
  3. The plugins folder in that location will be empty

Expected behavior
Plugins that are not found on the WordPress plugin directory should be moved to ./nucleus/plugins/ ready for the user to manually sort them and add to release belt etc.

Screenshots
Image

Environment

  • OS: macOS
  • Terminal/Shell: [e.g. Apple Terminal with zsh, iTerm2 with bash, VSCode with fish]

**Nucleus CLI version **
v1.0.0

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions