With OXID eShop version 4.7 (Community and Professional Edition) and version 5.0 (Enterprise Edition) we introduced changes in the module handler. We used to support the modules written for older versions from this time period – but now we want to phase it out with the next minor update (most likely version 4.9/5.2, to be released within the second half of this year).
You probably already know why we want to go this way: we want to get rid of code that is not necessary in order to stay lean and lank but also, the maintenance of these old modules costs time that can be better invested in more important stuff. In the near future we want to improve the module handler (contemplating automatic installation and updates) but the support of the old modules limits us.
What is necessary for the new modules to be compatible with newer shop versions?
Please make sure your module contains at least a metadata.php. Also please move all files to their proper directory structure inside the module folder.
Shop owners, please start the fetch modules diagnostic tool in your admin panel (available in OXID eShop > 4.8/5.1 series) and compare the entries with what is shown in admin -> extensions -> modules. Just in case a module is missing here, it then doesn’t contain a metadata.php and can be seen as a legacy module. Please turn to its provider in this case.