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

Support use of staging and dev environments for TagManager #1126

Open
diosmosis opened this issue May 31, 2024 · 0 comments
Open

Support use of staging and dev environments for TagManager #1126

diosmosis opened this issue May 31, 2024 · 0 comments
Labels
Enhancement For new feature suggestions that for example enhance Matomo's cabapilities..

Comments

@diosmosis
Copy link
Member

Currently, Matomo for WordPress explicitly limits the number of available environments to TagManager. Only live is allowed.

From what I understand, this was done for simplicity. The assumption was that most users would not need the other environments, as users with that need would be more likely to use a standalone Matomo instance.

Some users do want the other environments, however, so we should allow a way for them to access and configure them.

  • A new setting should be introduced for TagManager that enables/disables the extra environments.
  • The INI config that limits the environments (in common.config.ini.php) should be removed and replaced with PHP code that dynamically limits the environments based on the new setting.
  • The UI for selecting a TagManager container in the tracking code settings needs to be modified to also allow selecting the environment.
@diosmosis diosmosis added the Enhancement For new feature suggestions that for example enhance Matomo's cabapilities.. label May 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement For new feature suggestions that for example enhance Matomo's cabapilities..
Projects
None yet
Development

No branches or pull requests

1 participant