First - yes indeed the Confirmation Email I would expect to be totally a different issue - but the problem did/does go along with the change from 1.5 to 2 - so I mentioned it. But it seems we can just put that to one side.

However I have a working install ZC 1.5.5f using responsive classic which works fine with OPC1.5.
Indeed there are a number of changes I have made but nothing I can see which would be SO basic as to just stop OPC dead.

I have a full backup code and DB which I am using as reference - done BEFORE the original 1.5 OPC install .

I install 1.5 - all works as expected

Starting from the same point I install OPC 2.

I get the confirmation message - "The One-Page Checkout plugin was successfully upgraded from [] to [2.0.0 (2018-04-27)].
I set Enable One-Page Checkout? to true.
So far exactly as 1.5
BUT the Checkout sequence remains as standard !


So wheel off somewhere - I am a bit suspicious that I may have problem with template definition but cant see where.

So the simple question is - if the OPC says it is installed and the switch is set to true - what would stop the OPC firing and the standard one running??


I am IT guy of tens of years of experience - but could I just check precisely what you mean when you talk about merging files just in case your definition is not the same as mine - i am using WinMerge.

I have a file " The old ONE " from ZC I have a file "the new one" from the OPCInstall
They are different .
By Merge do you mean
Retain all the old code but overwrite any differences including additions from the New or
Aditionally dump any parts of the old code which do not exist in the new
or do I simply replace the old with the new?
May seem obvious but always good to check !

If no one can give me a pointer then I shall do an install from base ZC and add OPC 2 from scratch