Maximus
esforim
This is what I did:
(1) Restored my instance to version 6.0.8 - no problems
(2) Performed an upgrade and it rolled up to 6.0.10.
(3) Checked the log and whole bunch of errors shows up, similar to the previous error which was posted under https://forum.espocrm.com/forum/inst...data-truncated . (refer to screencap)
(4) Then i upgraded again which rolled-up to version 6.1.3 after a very long time.
(5) The same errors were logged in but the upgrade was successful (i think!)
(6) Delete the logs and loaded the instance. No errors logged.
(7) Did a rebuild and voila! the same error appears again.
Its odd, as i can remember that my problem surfaced when i upgraded 6.0.10 previously. Unfortunately, the upgrade from 6.0.8 steps through version 6.0.10 and seem to be creating the same issue. Thereafter any further upgrade appears to carry forward the problems. Espocrm developers need to investigate this.
I have halted at version 6.0.9. That's it for the time being because i am worried about the integrity of the database once i cross into any further upgrade which manifests the same errors in the log. I feel Espocrm need to perform the upgrade straight through from 6.0.8 or 6.0.9 to version 6.1.x instead of 6.0.10 step up.
esforim
This is what I did:
(1) Restored my instance to version 6.0.8 - no problems
(2) Performed an upgrade and it rolled up to 6.0.10.
(3) Checked the log and whole bunch of errors shows up, similar to the previous error which was posted under https://forum.espocrm.com/forum/inst...data-truncated . (refer to screencap)
(4) Then i upgraded again which rolled-up to version 6.1.3 after a very long time.
(5) The same errors were logged in but the upgrade was successful (i think!)
(6) Delete the logs and loaded the instance. No errors logged.
(7) Did a rebuild and voila! the same error appears again.
Its odd, as i can remember that my problem surfaced when i upgraded 6.0.10 previously. Unfortunately, the upgrade from 6.0.8 steps through version 6.0.10 and seem to be creating the same issue. Thereafter any further upgrade appears to carry forward the problems. Espocrm developers need to investigate this.
I have halted at version 6.0.9. That's it for the time being because i am worried about the integrity of the database once i cross into any further upgrade which manifests the same errors in the log. I feel Espocrm need to perform the upgrade straight through from 6.0.8 or 6.0.9 to version 6.1.x instead of 6.0.10 step up.
Comment