{"id":1915,"date":"2018-09-04T09:00:07","date_gmt":"2018-09-04T13:00:07","guid":{"rendered":"http:\/\/www.thatsoftwareguy.com\/blog\/?p=1915"},"modified":"2018-09-04T09:00:07","modified_gmt":"2018-09-04T13:00:07","slug":"what-does-a-nuc-opencart-change-look-like","status":"publish","type":"post","link":"https:\/\/www.thatsoftwareguy.com\/blog\/2018\/09\/04\/what-does-a-nuc-opencart-change-look-like\/","title":{"rendered":"What does a NUC OpenCart Change look like?"},"content":{"rendered":"

To further explain the grievance I posted last time about OpenCart NUC changes<\/a>\u00a0and how harmful they are to the ecosystem around OpenCart, I though it would be useful to post an example.\u00a0 \u00a0We’ll look at how the language file is loaded in Better Together for OpenCart<\/a>.<\/p>\n

The first version of Better Together for OpenCart was created to work with OpenCart 1.5.\u00a0 The controller for this module is created in<\/p>\n

admin\/controller\/total\/better_together.php<\/pre>\n
which defines the object<\/p>\n
class ControllerTotalBetterTogether extends Controller<\/pre>\n
Here’s how a language file was loaded in that version:<\/p>\n
$this->language->load('total\/better_together');<\/pre>\n
But in OpenCart 2.0, this changed!\u00a0 The code had to be refactored as follows:<\/p>\n
$this->load->language('total\/better_together');<\/pre>\n
Again, in OpenCart 2.3 – supposedly a minor version update – the code changed again, because the file system was restructured:<\/p>\n
$this->load->language('extension\/total\/better_together');<\/pre>\n
Not only that, but the class itself had to be renamed – and this happened\u00a0in a minor version update<\/strong>.<\/p>\n
class ControllerExtensionTotalBetterTogether extends Controller {<\/pre>\n
Language loading did not change in OpenCart 3.0, but many, many more things did.\u00a0 The net result is that to fully support my open source contribution, I would have to maintain separate, different copies<\/em>\u00a0of all the code files for Better Together for<\/p>\n