Installation of Custom Reports Plugin #30
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Why these changes are being introduced: UXWS Requested the installation of the Custom Reports premium plugin. The prep work has already been completed (loading the files into the container). Now it's time to move on to enabling the plugin and ensuring that the container definition is up-to-date. How this addresses that need: * Update the config.ini.php file to match the changes that appeared in the running container Side effects of this change: None. Relevant ticket(s): * https://mitlibraries.atlassian.net/browse/INFRA-576
cabutlermit
force-pushed
the
infra-576
branch
from
02d6e96 to
8f94980
Compare
dhrutibc
approved these changes
Sep 17, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
UXWS requested the installation of the Custom Reports premium plugin. The prep work has already been completed (loading the files into the container). Now it's time to move on to enabling the plugin and ensuring that the container definition is up-to-date by updating the
config.ini.phpfile to match the changes that appeared in the running container.How can a reviewer manually see the effects of these changes?
The Custom Reports plugin has been activated in the
dev-matomoinstance. The reviewer can log in todev-matomoand play around with the custom reports to ensure that it is accessible. Further testing will take place after this PR has merged tomainand we deploy the updates instage-matomo.Includes new or updated dependencies?
YES!
What are the relevant tickets?
Developer
Code Reviewer
(not just this pull request message)