Skip to main content

as user2694249 said correctly, the problem is a missing backwards compatibility of magento relative to php 5.3/4

The "bug" is already fixed in the newer Zend_Framework 1 versions, but magento has old versions shipped with it.

The bug is fixed with a patch, magento offersThe bug is fixed with a patch, magento offers. A EE fix is accessable via your internal account area.

as user2694249 said correctly, the problem is a missing backwards compatibility of magento relative to php 5.3/4

The "bug" is already fixed in the newer Zend_Framework 1 versions, but magento has old versions shipped with it.

The bug is fixed with a patch, magento offers. A EE fix is accessable via your internal account area.

as user2694249 said correctly, the problem is a missing backwards compatibility of magento relative to php 5.3/4

The "bug" is already fixed in the newer Zend_Framework 1 versions, but magento has old versions shipped with it.

The bug is fixed with a patch, magento offers. A EE fix is accessable via your internal account area.

Source Link
Fabian Blechschmidt
  • 35.4k
  • 8
  • 75
  • 182

as user2694249 said correctly, the problem is a missing backwards compatibility of magento relative to php 5.3/4

The "bug" is already fixed in the newer Zend_Framework 1 versions, but magento has old versions shipped with it.

The bug is fixed with a patch, magento offers. A EE fix is accessable via your internal account area.