Details
-
Type:
Bug
-
Status: Done/Fixed
-
Priority:
Minor
-
Resolution: Fixed/Completed
-
Affects Version/s: 4.0.0
-
Fix Version/s: 4.0.0
-
Component/s: Core CiviCRM
-
Labels:None
Description
As 3.4 and 4.0 both are same as per schema point of view and currently all upgrade related code is handled in 3.4
So we need to handle special case when user is upgrading from 4.0.alpha1 and there might be some changes in 3.4.alpha2 ..
Proposed Solution :
When user is upgrading from 4.0.alpha1
1. Here we could assume that db has all changes up to 3.4.alpha1
2. Now we have to run the matching counter part of 3.4. upgrade php functions and sqls in a incremental way.
so when user upgrading from 4.0.aplha1 -> 4.0.beta1 - run all upgrade files from 3.4.alpha2 to 3.4.beta1 with incremental way.