Counting Resource Views in Evolution CMS with a Reusable `countViews` Pattern

View counters are one of those features that look trivial but often fail quietly. In the old Evolution topic behind this post, the data source existed, the frontend rendered, but the counter still showed zero.

Where the Real Problem Usually Lives

When a counter never changes, the rendering layer is rarely the root cause. The real issue is usually in the update path:

• the increment code is not firing on page load
• the new value is not being written back correctly
• caching prevents the updated value from surfacing
• the stored field is not the one the template actually reads

A Good Pattern

Keep the view counter logic narrow: increment one clearly defined field, then render that same field in listings or detail pages. Do not mix several counting strategies unless you really need separate analytics concepts.

This old post still matters because counters are often added as a lightweight business feature, but they only stay trustworthy if the update step is explicit and testable.