Evolution CMS 2.0.1 and Shopkeeper 1.3.6: Early Compatibility Notes

One of the most important realities of a major platform upgrade is that the ecosystem does not catch up overnight. This discussion captured exactly that moment for Evolution CMS 2.0.1 and Shopkeeper 1.3.6.

The main friction point was straightforward: older Shopkeeper releases still expected the classic DocumentParser and legacy DBAPI behavior, while Evolution 2 had already moved further toward the newer runtime model. That left developers in an awkward middle state where the core was ready, but an established commerce workflow was not.

What this meant in practice

• Existing Shopkeeper-based stores could not always move to Evolution 2 immediately.
• Teams had to choose between staying on the older stack for stability or updating the project architecture first.
• Compatibility checks became just as important as core release notes.

This kind of post belongs in the blog because it documents a real migration lesson: for production commerce projects, upgrading the CMS and upgrading the store layer are never separate decisions.

If you are reviewing an older Evolution migration path today, the safest historical takeaway is simple. Check the exact package generation a project depends on before planning the upgrade window, and treat commerce compatibility as a first-class migration task rather than a final QA item.

Source: Evolution CMS 2.0.1 release and Shopkeeper package page on Extras.Evolution.