Details
-
Type:
Bug
-
Status: Done/Fixed
-
Priority:
Critical
-
Resolution: Fixed/Completed
-
Affects Version/s: 2.2.0, 2.2.1, 2.2.2, 2.2.3, 2.2.4, 2.2.5, 2.2.6, 2.2.7, 2.2.8
-
Fix Version/s: 2.2.9
-
Component/s: None
-
Labels:None
Description
A NULL value for civicrm_domain.version column which could be accidental / truncation of civicrm_domain table (NOT RECOMMENDED) in an attempt to clear config_backend, causes Upgrade script to give the message - "Your database is already upgraded to latest version" and doesn't actually upgrade the db.
Problem goes unnoticeable for smaller rev upgrades (as the schema change is not significant).
Note: This has already been fixed in 3.0 (r23181)
If possible we should also maintain some kind of log for change in civicrm_domain.version.