tracker issue : CF-3621816

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

Arbitrary restriction on IMPORT

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/Duplicate

Reporter/Name(from Bugbase): Adam Cameron / Adam Cameron (Adam Cameron)

Created: 08/30/2013

Components: Language

Versions: 10.0

Failure Type:

Found In Build/Fixed In Build: Final / CF11 Update3

Priority/Frequency: Normal / Few users will encounter

Locale/System: English / Win XP All

Vote Count: 0

Duplicate ID:	CF-3780136

The docs for import ( say this:
importImport in cfscript is only equivalent of <cfimport path="">. ***You cannot use <cfimport taglib=""> in cfscript.***

(my ***emphasis***)

Why? Why place this seemingly arbitrary restriction on the script-equiv of the tag? This just increases the FUD in the ColdFusion CFScript implementation in that wherever possible the tag & script equivalents should actually be *equivalent*

This is not a theoretical case: I just had a situation in which for various reasons I have a script block to perform some logic at the top of a file that goes on to have mark-up and tags, and I'm not able to import my tag lib in my script block, for seemingly no good reason at all.

Raising as a bug rather than a feature request because this sort of incongruity is a design bug.

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3621816

External Customer Info:
External Company:  
External Customer Name: Adam Cameron.
External Customer Email:  
External Test Config: My Hardware and Environment details:



Got fixed in due course.
Comment by Awdhesh K.
14592 | December 04, 2014 08:14:44 AM GMT
This bug is fixed. Related bug Ids:CF-3754672,CF-3811008,CF-3780136. But the documentation has not changed .So sending the bug to Frank.
Comment by Suchika S.
14593 | January 15, 2015 07:06:04 AM GMT
Closing this bug as duplicate and logging a separate documentation bug.
Comment by Suchika S.
14594 | January 15, 2015 07:11:51 AM GMT
Cool one, cheers Suchika. Can you pls update the fix version on the ticket so we know WHEN it was fixed? Cheers.
Comment by External U.
14595 | January 15, 2015 07:12:16 AM GMT
This bug was fixed for CF 11 Update 3. Thanks, Suchika.
Comment by Suchika S.
14596 | January 15, 2015 07:19:10 AM GMT