Turns out that the TagManager core plugin needs some extra care and attention if it wasn't initially enabled when first starting with Matomo. Attempting to activate it the usual way causes Matomo to break.
This GitHub Issue documents that problem and provides a simple (but strange) solution:
For our container-based deploy, this means
- connect to the running container
- ensure that a simple text editor is available in the container
- deactivate the TagManager plugin:
./console plugin:deactivate TagManager - edit the config/config.ini.php file to remove the
PluginsInstalled[] = "TagManager"line - run the
core:updatecommand:./console core:update(nothing should happen) - activate the TagManager plugin:
./console plugin:activate TagManager - run the
core:updatecommand again:./console core:update(nothing should happen)
The appropriate updates to the database will now be in place.
At this point, proceed with updates to this repository by updating the config.ini.php file to match the file from the container.