Blog Sections Open
Laravel 9 Lands in the Evolution CMS 3.2.x Branch
A useful development note about the move to Laravel 9 inside the 3.2.x branch and why branch-level testing mattered before the next release cycle.
Not every important platform change arrives as a polished release note. Sometimes the useful signal appears earlier, when maintainers announce that a major dependency shift has landed in a working branch and needs validation on real projects. That is what made this Telegram update worth keeping.
The core message was straightforward: Laravel components had been updated to version 9 in the 3.2.x branch, the fresh install path already looked healthy, and the next step was testing against real-world projects. For Evolution CMS developers, that kind of note matters because framework upgrades affect package compatibility, bootstrap assumptions, and the broader confidence teams have in the next release line.
Why this kind of branch update matters
- it shows the platform moving in step with the Laravel ecosystem
- it documents the testing window before the change reaches a formal release
- it gives developers an early signal to check their projects and packages
Source: Telegram post and Evolution CMS 3.2.x branch.
A Simple Stop-War Widget for Evolution CMS Sites
An ecosystem archive post preserving a small stop-war widget shared during the first days of the full-scale invasion of Ukraine.
start-evo3: A Demo Site on Controllers for Evolution CMS 3
An ecosystem note about the start-evo3 demo site and why controller-based examples mattered for the early Evolution CMS 3 learning curve.