tracker issue : CF-4198459

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

[ANeff] ER for: THIS.compileExtForModule

| View in Tracker

Status/Resolution/Reason: To Fix//EnhancementRequired

Reporter/Name(from Bugbase): Aaron Neff / Aaron Neff ()

Created: 03/30/2017

Components: Language, CustomTag

Versions: 2016

Failure Type: Others

Found In Build/Fixed In Build: /

Priority/Frequency: Normal /

Locale/System: / Platforms All

Vote Count: 0

Issue: CF11 continued support for non-CF extensions in cfinclude, but broke support for non-CF extensions in cfmodule.

Repro:
<cfinclude template="my.module"> Works in CF10. Works in CF11+ if THIS.compileExtForInclude allows extensions "*" or ".module".
<cfmodule template="my.module"> Works in CF10. Fails in CF11+, even if THIS.compileExtForInclude allows extensions "*" or ".module".

cfinclude and cfmodule should be treated the same. If one of those tags can accept non-CF extensions via a per-app setting, then the other tag needs to as well. So, it's a bug that one tag does and one tag doesn't.

Possible actions:
1) Change this ticket to "Bug" and allow cfmodule to honor THIS.compileExtForInclude.
2) Implement THIS.compileExtForModule, and allow cfmodule to honor THIS.compileExtForModule.

Attachments:

Comments:

In case you need a full repro case: Application.cfc ---------------------- component { THIS.name = "foo"; THIS.compileExtForInclude = "*"; } index.cfm ---------------------- <cfinclude template="my.module"> <cfmodule template="my.module"> my.module ---------------------- success Actual CF10 result: success success Actual CF11+ result: success Exception (CFMODULE tag only supports including ColdFusion templates.) Expected behavior: CF10's -or- implement THIS.compileExtForModule for cfmodule.
Comment by Aaron N.
981 | March 30, 2017 01:15:57 AM GMT