We have recently updated from 6.2.6.19 to 6.2.8.20 and have noticed, what we consider to be significant change - if not bug, in how the inspect templates “Auto (Optimized Perfomance)” functionality now works.
With 6.2.6.19 any change we made to any CFM/CFC file was immediately picked up Lucee and could be checked in our application. With 6.2.8.20 we are now having to resort to rebuilding our application for file changes to be recognised. In our view this is a massive retrograde step which seems to have been caused by Jira.
From our POV “Auto” now seems to be working more like “Never”
Can this be looked at (and fixed)? Or is there a way, in the short term at least we can set it up so that either “Once (Good)” or “Always (Not recommended)” ?
Yes, the Inspect Templates Auto fix landed in 6.2.9.3, and the line is now at 6.2.9.4-SNAPSHOT. Docker Hub already has lucee/lucee:6.2.9.4-SNAPSHOT* images from Monday, including the nginx variants. There’s no separate 6.2.9.3 Docker tag, so use a 6.2.9.4-SNAPSHOT image. Until you upgrade, the workaround is still to set Inspect Templates to “Once” (or “Always”).
@ABrunt quick update: Inspect Templates “Auto” not picking up changes to .cfm/.cfc files since 6.2.8.20 is fixed in 6.2.9.4-RC, which is out now: Lucee 6.2.9.4-RC available for testing. The Docker images are lucee/lucee:6.2.9.4-RC plus the -light, -zero and -nginx variants.
The fix (PR #2809) and a regression test are merged into 6.2, tracked as LDEV-6482. Lucee 7 isn’t affected.
It would be great if you could try the RC with Inspect Templates back on “Auto” and let us know if your edits are picked up again.