The usage of composer for projects was introduced with OXID eShop version 4.9.6 and 5.2.6. Please learn in this blog post how it was implemented, what this implementation is supposed to do and what not.
A couple of days ago we were working on Bug #5892. The reporter complaint about random deadlocks with increasing traffic in OXSEO table where InnoDB is used. After debugging and analysing the InnoDB status message, he sorted out the culprit:
Symfony’s HttpKernel and it’s role when switching OXID to Symfony framework
Elaborations about dependency injection when switching OXID eShop to Symfony basis
Elaborations about usage of composer and autoloader in OXID eShop
As part of OXID SDK, we recently published OXID eShop Testing Library. It is intended to be an easy to use tool for writing Unit (PHPUnit), Integration (OxidTestCase) and acceptance (Mink/QUnit) tests for extension developers. In particular, it is possible to test modules against OXID eShop and against other modules (where no module activation is […]
There are some things that are often forgotten but should be checked before going live with a new shop. This Checklist should help you to remember these things: Language-settings Do you really start a multilanguage-shop? No? Deactivate the languages you don’t need. Else the shop would check the browserlanguage and will redirect you to the […]
Following up his last article Accepting Credit Card Payments with OXID eShop CE and Authorize.Net at Zend Developer Zone, Vikram Vaswani explains how to integrate the AlertPay interface into the OXID eShop. In opposit to the former article, where a transaction-oriented API was illustrated, the new article describes the implementation of a payment gateway that requires the shopping cart to transfer control to its own user interface and returns control to the shopping cart once the transaction is complete.