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

disable plugins in config.ini.php #17708

Closed

kevin-shelaga opened this issue Jun 25, 2021 · 4 comments

Labels

answered

kevin-shelaga commented Jun 25, 2021 •

edited

The following settings do not disable plugins as expected, is this currently possible?

[General]
enable_trusted_host_check = 0
salt = "xxxxxxxxxxxxxxxx"
enable_marketplace = 0
enable_goals = 0
enable_tour = 0
enable_feedback = 0
enable_mobilemessaging = 0
enable_ecommerce = 0

Expected Behavior

Current Behavior

Possible Solution

Steps to Reproduce (for Bugs)

Context

Your Environment

Matomo Version:
PHP Version:
Server Operating System:
Additionally installed plugins:

Browser:
Operating System:

The text was updated successfully, but these errors were encountered:

kevin-shelaga added the Potential Bug label

Member

sgiehl commented Jun 25, 2021

Hi @kevin-shelaga.
It is possible to simple deactivate plugins in the UI. If that doesn't suite you, you can use the console command ./console plugin:deactivate pluginname or remove the plugin from the plugins list in config.ini.php

sgiehl closed this as completed

sgiehl added answered and removed Potential Bug labels

Author

kevin-shelaga commented Jun 25, 2021 •

edited

Thank you @sgiehl how would I disable them from the UI? I could not find instructions for that. I am on 4.3.1.

When I removed the plugin from the config file, it would be automatically added back in a second later. It do you mean remove the plugin from the plugin directory?

Member

sgiehl commented Jun 25, 2021

In administration under System > Plugins. But some plugins can't be disabled as they are required.

Author

kevin-shelaga commented Jun 25, 2021

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment