OXID eShop version 4.8.2 (CE + PE) & 5.1.2 (EE)

General hints for this package

Runs on PHP 5.4 and PHP 5.3. Might run on PHP 5.2 (not tested any longer).

This release had to be recalled because of an unexpected behaviour of the WYSIWYG editor. That’s why the download of this package has been disabled. If you already have downloaded this package, please try to update to OXID eShop version 4.8.3 (PE, CE) or 5.1.3 (EE) as soon as possible or use this hotfix to correct this issue.


See http://www.oxid-esales.com/en/support-services/documentation-and-help/oxid-eshop/installation/oxid-eshop-update-installation.html


Some front end and admin templates were changed slightly due to the SEPA implementation. Also there are a few changes in the language files for the Azure theme and for the admin panel. Please find detailed information about template changes in “templ_docu_azure/index.html” and “templ_docu_admin/index.html” of the cumulative update packages.

Fixed Bugs

New Features

In the admin panel -> Master settings -> Core settings -> Settings, you’ll find a new bullet point “Bank account information (SEPA)” with an option to use IBAN/BIC information only. This option is turned off by default.

Important information for developers

  • With the bug fix #5582, a former behaviour was changed so the error messaged leads to offline.html in case the database cannot be reached for some reason. This is valid for OXID eShop in productive mode; in development mode, the regular error message will appear.
    The method _handleDbConnectionException was introduced for this reason and can be overloaded by a module if you’d like to implement a different behaviour. Please also see this comment in the bug entry:
  • The fix for #5568 shall be seen as a security tweak: only public methods can be triggered from outside the shop framework, protected functions can’t any longer. This is an important information especially for module developers. This way, we streamline the restrictions for module writers and care that the shop cannot be attacked even if a module was coded an insecure way.
  • Marked as deprecated
    • oxModule::isExtended
    • oxSepaValidator::isValidIBANRegistry
    • oxSepaValidator::setIBANRegistry
    • oxSepaValidator::getIBANRegistry
  • New config option “blDoNotDisableModuleOnError” to prevent from automatically disabling a module if it is corrupted during the development.

0 replies

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published. Required fields are marked *