Upgrading from 2.2.0.0 to 3.x - What are the benefits/needs, security issues, and writing extensions
Posted: Thu Jul 05, 2018 11:54 pm
Hello,
I recently took over a running Opencart project that is currently 2.2.0.0. I come from a Ruby on Rails and mobile development background and PHP experience. Looking through the docs, I have a reasonable understanding of how the technology is setup in an MVC-L fashion. Nothing new here. The only thing I have not worked with is TWIG and Smarty (tpl).
The client will want me to develop a few custom extension for him. A few on the front end, but more for the back end for admin purposes and reports. Therefore, before I get my hands dirty, I am wondering if I should tackle upgrading to 3.x first or if 2.2.0.0 is stable and secure to keep online?
Poking around in the docs and Wiki, there seems to be more complete documentation on building extensions for the 2.x flavor. The wiki for 3.x is incomplete. Also I am aware that TWIG is deployed in 3.x where Smarty in 2.x. I'd rather not have to dive into 2 template languages, but I really don't know the pros and cons of each to the other.
Generally, with software, the newer versions address security risks that pop up over time. Are there any known risks or breaches in 2.2.0.0 that would warrant taking action on a 3.x upgrade immediately?
I could certainly use some advice on what makes the most sense - plan to stay in 2.x or move to 3.x before any custom work.
Thanks for any advice in advance....
TJ
I recently took over a running Opencart project that is currently 2.2.0.0. I come from a Ruby on Rails and mobile development background and PHP experience. Looking through the docs, I have a reasonable understanding of how the technology is setup in an MVC-L fashion. Nothing new here. The only thing I have not worked with is TWIG and Smarty (tpl).
The client will want me to develop a few custom extension for him. A few on the front end, but more for the back end for admin purposes and reports. Therefore, before I get my hands dirty, I am wondering if I should tackle upgrading to 3.x first or if 2.2.0.0 is stable and secure to keep online?
Poking around in the docs and Wiki, there seems to be more complete documentation on building extensions for the 2.x flavor. The wiki for 3.x is incomplete. Also I am aware that TWIG is deployed in 3.x where Smarty in 2.x. I'd rather not have to dive into 2 template languages, but I really don't know the pros and cons of each to the other.
Generally, with software, the newer versions address security risks that pop up over time. Are there any known risks or breaches in 2.2.0.0 that would warrant taking action on a 3.x upgrade immediately?
I could certainly use some advice on what makes the most sense - plan to stay in 2.x or move to 3.x before any custom work.
Thanks for any advice in advance....
TJ