# Mystified by laminas-mvc app configuration cache

**URL:** <https://discourse.laminas.dev/t/mystified-by-laminas-mvc-app-configuration-cache/1560>\
**Category:** Components & MVC\
**Created:** [April 26, 2020, 9:29pm UTC](https://discourse.laminas.dev/t/mystified-by-laminas-mvc-app-configuration-cache/1560 "2020-04-26T21:29:43Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![davidmintz](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.laminas.dev/davidmintz/32/213_2.png) [@davidmintz](https://discourse.laminas.dev/u/davidmintz)\
**Post date:** [April 27, 2020, 1:10pm UTC](https://discourse.laminas.dev/t/mystified-by-laminas-mvc-app-configuration-cache/1560/3 "2020-04-27T13:10:17Z")

</div>

@powerkiki thanks for the suggestion. Since posting, I did figure out that (not surprisingly) the fault is in my code somewhere, not the framework’s, by creating a new skeleton app and fiddling with `composer development-(enable|disable)`. Again, no surprise, but one always has to rule that out.

I believe I started with the skeleton, but it was 4+ years ago; it was ZF2, became ZF3, became Laminas, and has diverged vastly from the skeleton. Either I must have removed those composer scripts from my `composer.json` or else they didn’t exist back then.

* * *

**UPDATE:**

`composer require laminas/laminas-development-mode` and the rest is simple.

Thanks!

---

_[View the full topic](https://discourse.laminas.dev/t/mystified-by-laminas-mvc-app-configuration-cache/1560)._