Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Document upgrade/installation procedures for Git checkouts (with composer.phar install --no-dev and git submodule update --init --recursive) #8717
A little bird told me I could upgrade from one version straight to another without going through intermediate version upgrades. However this failed for me today:
And yet I did not make any hacks/modifications to my setup:
So I reverted back to my previous version:
Ah, you mean running
However, I've encountered a subproblem now:
Contents of that log file:
Shared hosts (or most locked-down web servers) will not have C compilers lying around, for security reasons. Can we do something about that?
Ah yes, that worked... but it seems there's still a bug left to investigate in the process:
Running the DB upgrade script:
But now, the bug is this: when visiting the web interface, no data shows up, and I get this error shown in the Admin settings:
Again, not sure why this would happen, it seems like the file really is missing:
changed the title from
Upgrading directly from 2.0.3 to 2.14.3 fails to run console core:update script - fatal error: class 'Piwik\Common' not found
Document upgrade/installation procedures for Git checkouts (with composer.phar install --no-dev and git submodule update --init --recursive)
Sep 5, 2015
IIRC there should be a page in the FAQ about deploying Piwik using Git, but that might be a bit outdated. Btw. It is not the common use case maintaining Piwik using Git. Normaly it should be installed using the downloadable build and the built-in auto update mechanism.
Ah that FAQ is interesting! It's missing a few bits that I learned in this bug report though.
So instead of:
Maybe it could say:
Hoping that's useful.