Allow initially missing application defined mapping physical paths to be re-checked


When an application first starts, any mappings defined in application.cfc are checked to make sure the physical path exists. If not, the mapping defaults to a path below the web/application root. For example:

If "c:\test" doesn't exist then the mapping will resolve to "(webroot path)\test" wherever that might be.

If I then create "c:\test" after the application has started, the mapping will not be updated even if I restart the application. Instead it will continue to resolve to "(webroot path)\test" until Lucee is restarted. In other words the initial resolution appears to be cached for the life of the server.

To avoid a disruptive restart, it would be useful to be able to programmatically force the physical paths of application defined mappings to be re-checked at runtime.

The following currently unsupported code will achieve this:

See this forum thread for more details


Pothys - MitrahSoft
December 7, 2020, 10:14 AM

I've checked the issue with fixed version It works fine now.
So, I changed the status QA to Deployed.

Michael Offner
December 4, 2020, 4:19 PM

please give the build a try

Michael Offner
December 4, 2020, 4:18 PM

Julian Halliwell
October 22, 2020, 10:16 AM

Thank you

Pothys - MitrahSoft
October 16, 2020, 4:20 PM

I've checked this ticket and confirmed the issue happened on lucee latest version also. While starting the application, if the application-defined mapping path doesn't exist means it defaults to the webroot path. After creating the path means it doesn't take that path it still takes the webroot path. But ACF works as expected.
Also, I've added a fix for this ticket

Pull Request:

Your pinned fields
Click on the next to a field label to start pinning.


Pothys - MitrahSoft


Julian Halliwell