Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

Problems updating from Piwik 0.1 to trunk #894

Closed
robocoder opened this Issue · 6 comments

1 participant

Anthon Pang
Anthon Pang
Collaborator
  • warning when updating user_language
  • installer does not prompt to re-use existing tables before database update
  • mandatory updates don't consistently throw Piwik_Updater_UpdateException

Table inconsistencies between fresh install and upgrade path:

  • the 0.2.33 update (utf8 conversion) misses tables created by plugins
  • also in 0.2.33, TEXT fields became MEDIUMTEXT fields
  • in 0.2.27, visit_goal_converted is inconsistent between Piwik.php and the update (VARCHAR vs TINYINT)
  • the 0.2.12 update didn't drop the index_idaction INDEX on log_action table
  • in 0.2.2 (there was no update), feedburnerName changed from NOT NULL to DEFAULT NULL on site table
  • in 0.1.7 (there was no update), location_provider changed from NOT NULL to DEFAULT NULL on log_visit table

Re-open #522:

  • tables created with login column still VARCHAR(20)
Anthon Pang
Collaborator

(In [1351]) fixes #894, refs #666 - fix problems and inconsistencies between fresh install and upgrade path

Only the utf8 side-effects of converting of TEXT columns to MEDIUMTEXT columns was unchanged.

Anthon Pang
Collaborator

(In [1352]) refs #894 - a little refactoring

Anthon Pang
Collaborator

(In [1354]) refs #894 - fix broken Updater.test.php

Anthon Pang
Collaborator

(In [1355]) refs #894 - generate friendly error message if configuration file exists but points to an empty database

Anthon Pang
Collaborator

(In [1356]) refs #894 - update comments

Anthon Pang
Collaborator

(In [1365]) refs #894 - updates for third party plugins

Anthon Pang robocoder added this to the Piwik 0.4.3 milestone
Anthon Pang robocoder self-assigned this
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.