|
Correct you did not understand my reply I assume
From what I saw when I debugged the installer it had nothing to do with some hack. I am merely stating if you where adding stuff before that was not included in some release this could have compounded your issue.
What I saw on the installer is on one upgrade we put the wrong version number (2.0) in the version field when doing the 2.0b2 upgrade and another we forget to put the version number so your actually skipping an upgrade on the 2.0 upgrade.
What I did if you compare your base install script with the one I modified and included in the download is you will see I explicitly added the new version numbers properly after each upgrade so when you finish your database should be updated as when you finish one upgrade it will read the proper version number and go to the next incremented one.
|