This post describes the minimum changes necessary to make an existing module immediately compatible with OXID eShop 6.0. In a later blog post we will tell you how to fully port a module or write a new one from scratch so that it fits OXID eShop 6.0 and above.
About Heike Reuter
"Software Developer at OXID eSales since 2007.
Interested in computer sciences, eCommerce, hand spinning, cardweaving and other handicrafts. Cannot live without online shops. Raising the next generation of computer addicts (mother of twins)."
Entries by Heike Reuter
OXID eShop versions 6.0.0 beta was published containing many changes “under the hood”. Read this blog post for the release notes.
Namespaces With the namespaces we introduced new namespaced classes for all former oxSomething classes. The old oxSomething classes have all been marked as deprecated as of V6.0 (@deprecated on b-dev), have no more content and extend their new namespaced analogon. For backwards compatibility, classMap.php has been introduced, which ensures that the usage of all oxSomething […]
We found a nasty little bug in conjunction with MySQL 5.6 setting “block_nested_loop” and OXID eShop Enterprise Edition 5.2.x. Please learn in this blog post how it looks like and how to work around.