Quote:
|
Originally Posted by franki
I'm having the same issues. Version is still shown as 4.1.7, the choice to upgrade to 4.1.8 is sitll there, and when I run the upgrade again, all the files that were updated previously were shown as "already patched". 4.1.7 is still shown as the current.
There were 28 files that were not patched, and when I go through them to patch them manually (using the diff file), most of those codes aren't even in the original 4.1.7 versions???
I'm encountering other issues with this upgrade, sucg as the patch.sql does not get applied udring the process, and creates error in the customer's front end. Manually installing patch.sql solve this problem.
|
we have nearly the same problem with you.
the version is 4.1.6 -> 4.1.8