Pain points: - browser times out on lengthy updates - users without shell access - failing because users lack sufficient mysql privileges
pre-flight checklist (useful at time of installation too) if not php cli mode ignore_user_abort disable max_execution_time if exec() is not disabled exec('nohup php index.php >/dev/null 2>/dev/null &') // run the update in the background redirect to tmp/latest/progress.html // a static file that is overwritten by the updater else run updater // for each update, echo 'something' to the client and flush output buffers to (try) keep connection alive else run updater // foreach update, write to progress.html
See also #910
Anthon, we've made some good improvements to the update screen in 0.5.5 and users have not had issues it seems. I'd like to move this to post 1.0 - thoughts?
Insuffiicient permissions is still a problem. So, at minimum, we should do the pre-update check before 1.0.
I missed that first line.
My suggestion would be to be to show the report only if there are errors (not warnings, as warnings could have been shown during the install too and would be the same). The exception being the file integrity warnings that we already display.
That said, I think this would be a must do only if we happen the change the requirements (that would trigger an "error") for Piwik before 1.0.
Looks like I already had a ticket for the pre-flight. #927
I just tested piwik upgrade on a 10Gb piwik_log_* DB and the shell option worked like a charm. I don't think there would be users without shell option and with a very large DB that would cause problem in the UI.