Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Console commands to enable/disable plugins #6801

Closed
mnapoli opened this issue Dec 3, 2014 · 8 comments
Closed

Console commands to enable/disable plugins #6801

mnapoli opened this issue Dec 3, 2014 · 8 comments
Labels
answered For when a question was asked and we referred to forum or answered it. Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc.
Milestone
Backlog (Help wan...

Comments

@mnapoli
Copy link
Contributor

mnapoli commented Dec 3, 2014

In all tutorials and guides we say:

  • generate a plugin: ./console generate:plugin
  • activate the created plugin under Settings => Plugins

Having a console command to enable or disable plugins would be really useful when developing one.
@mnapoli mnapoli added the Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc. label Dec 3, 2014
@mattab
Copy link
Member

mattab commented Dec 3, 2014

There is already such command, but I guess we should document it everywhere where it makes sense:

./console core:plugin activate PLUGIN_NAME_HERE

@mattab mattab added this to the Short term milestone Dec 3, 2014
@mnapoli
Copy link
Contributor Author

mnapoli commented Dec 3, 2014

ha yep and ./console list doesn't list it (since it's a subcommand of core:plugin).

We should maybe rename it plugin:activate?

@mnapoli mnapoli closed this as completed Dec 10, 2014
@mattab
Copy link
Member

mattab commented Dec 18, 2014

@mnapoli maybe core:plugin:activate and core:plugin:deactivate ?

@mattab mattab added the answered For when a question was asked and we referred to forum or answered it. label Dec 18, 2014
@mnapoli
Copy link
Contributor Author

mnapoli commented Dec 18, 2014

I tend to find "core" pretty redundant and useless, it just makes the command longer but not clearer.

@tsteur
Copy link
Member

tsteur commented Jan 4, 2015

👍 for plugin:activate, plugin:list, ... core makes no sense there. It doesn't provide any meaning and is rather "technical". Also I noticed the ManagePlugin.php command contains actually 3 commands and should be refactored into 3 actual commands, meaning 3 files. One more clue we should actually rename this.

This would not be only code-wise much better but also for an end user since all commands would appear when executing ./console etc.

Maybe we can reopen this issue or create a new one for it?

@mnapoli mnapoli mentioned this issue Jan 4, 2015
Closed
@mnapoli
Copy link
Contributor Author

mnapoli commented Jan 4, 2015

Definitely! I opened #6915

@mattab
Copy link
Member

mattab commented Jan 5, 2015

+1

@mnapoli
Copy link
Contributor Author

mnapoli commented Jan 11, 2015

For the record I renamed the commands in #6915

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
answered For when a question was asked and we referred to forum or answered it. Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc.
Projects
None yet
Milestone
Backlog (Help wanted)
Development

No branches or pull requests
3 participants
@tsteur @mattab @mnapoli