tracker issue : CF-4203283

select a category, or use search below
(searches all categories and all time range)

On the fly app specific mappings not registering correctly

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/Fixed

Reporter/Name(from Bugbase): Bradley Wood / ()

Created: 08/17/2018

Components: Language

Versions: 2018

Failure Type: Incorrect w/Workaround

Found In Build/Fixed In Build: Final / 2018.0.0.311667

Priority/Frequency: Major / Some users will encounter

Locale/System: / Platforms All

Vote Count: 8

Problem Description:
ColdBox makes regular use of on the fly application specific mappings for modules that are registered.  In 2018, there has been a regression in regards to these working.  

Steps to Reproduce:

var appSettings = getApplicationMetadata();
appSettings.mappings[ '/foobar' ] = 'C:\windows\';
writeDump( expandPath( '/foobar' ) );

If you run the above code, the expandPath() will not correctly expand to C:/windows, but instead to the web root as though the mapping didn't exist.  If you uncomment the extra call to getApplicationMetadata() then it will suddenly start working.

Actual Result:

Mapping is not used unless you call getApplicationMetadata() first.

Expected Result:

Mapping should be used immediately like it is on previous versions of ColdFusion.

Any Workarounds:

Manually call getApplicationMetadata() an extra time



ColdBox continues to be completely broken out of the box on 2018 due to this bug. I see the fix didn't make it into updater 1. Is there hope for updater 2?
Comment by Bradley W.
29700 | September 14, 2018 03:55:28 AM GMT
This is a blocker for anyone using the ColdBox framework who wishes to upgrade to 2018.
Comment by Jonathan C.
29752 | October 02, 2018 09:05:21 PM GMT
This indicates a complete lack of testing against real world CF applications!
Vote by Sean C.
29775 | October 09, 2018 08:48:27 PM GMT
+1 As more and more people are in the process of moving to ColdBox (or other of the Ortus Tools) - this is a show stopper for those of us wishing to use it with 2018
Vote by Sid W.
30152 | January 28, 2019 07:14:17 PM GMT
I am in the process of migrating to ColdFusion 2018 and all of our applications are currently running on ColdBox framework. If this doesn't get fixed soon then we will NOT migrate to ColdFusion 2018.
Comment by Jae J.
30517 | March 15, 2019 12:10:36 PM GMT
Jae, I think the latest 2018 update fixed this. Please give it a try,
Comment by Bradley W.
30518 | March 15, 2019 02:48:47 PM GMT