When upgrading to a new version, the database upgrades take too long to run in the web browser. Mine timed out, and left me with a half upgraded database which I had to manually fix by reading the upgrade files.
I would like one or all of:
Example command from Updates/0.2.27.php:
visit_goal_converted VARCHAR( 1 ) NOT NULL AFTER
So far that has taken 3 minutes, I suspect it will take about 6. I had a whole bunch of upgrades to run, which in total will take a couple of hours I suspect. Not a realistic thing to do in one web request.
I've marked this critical, as it caused my piwik installation to be totally broke during a routine upgrade.
A command line upgrade is probably the most reasonable path given that:
Going forward, users should be encouraged to stay up-to-date with releases to avoid large database updates.
in a future version (Maciej is working on it) there will be rather big schema update (adding one field to piwik_log_link_visit_action, adding field in piwik_log_visit)..
This problem will happen again. What should we do to quick fix it?
A "command line" message below the normal "Welcome to Piwik! You need to update [...] If your Piwik database is large or very large and you have a shell access to your Piwik server, you can trigger the update by using the following command line: /usr/bin/php5 /path/to/piwik/index.php updateCorePlugins=1" or something similar?
anybody implementing this ticket should feel evil.
the command line tool, if this is the direction are going, could maybe read the max execution time from the config, and let the user know "Your max execution time is Xmin. If you have a medium or large Piwik installation, maybe you would like to increase this limit. Look for X in your php.ini."
(In ) refs #666 - record version of incremental updates as they are done