Blog Sections Open
Why resource.php Broke After Updating to Evolution CMS 1.0.13
When a helper library writes broken INSERT statements after an upgrade, the problem is usually a changed expectation in the CMS data layer.
Custom helper libraries such as resource.php were often built around assumptions about how the core database layer accepted field arrays. After an update, those assumptions can break, turning clean saves into malformed SQL.
What this teaches
Any library that wraps low-level document creation should be treated as version-sensitive infrastructure. If the upgrade changes the expected insert format or field handling, the wrapper has to be updated too.
This is a good example of why custom save helpers belong in the ecosystem layer: they are part of the project’s runtime tooling, not just application content.
Source: Evolution CMS on GitHub.
What evoFilter Promised for Evolution CMS Product Filtering
A short ecosystem note on the need for a more convenient filter stack in Evolution-era catalog projects.
Extending the aDate Snippet for More Flexible Date Output
How the aDate snippet evolved to support richer date formatting patterns in Evolution CMS output templates.