tracker issue : CF-4205265

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

Invalid tag nesting configuration Bug

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/Duplicate

Reporter/Name(from Bugbase): Jason S. / ()

Created: 09/26/2019

Components: Language, General

Versions: 2018

Failure Type:

Found In Build/Fixed In Build: 2018.0.05.315699 /

Priority/Frequency: Normal /

Locale/System: / Windows 10

Vote Count: 1

Problem Description:

We have some code that calls a component method. The method does a cfquery and uses cfsavecontent and cfoutput to generate html content using the query results. The html string is returned by the method. 

The content is then generated on a .cfm page like this.

<cfoutput>#myComponent.getContent()#</cfoutput>

After CF 18 update 5 this code started throwing this error.

Invalid tag nesting configuration Bug.

A query driven queryloop tag is nested inside a queryloop tag that also has a query attribute. This is not allowed. Nesting these tags implies that you want to use grouped processing. However, only the top-level tag can specify the query that drives the processing.

Steps to Reproduce:

See the attached code to reproduce.

Actual Result:

Invalid tag nesting configuration Bug.

Expected Result:

HTML content on the screen.

Any Workarounds:

This seems to work.

<cfset myComponent = new Mycomponent()>
<cfset content = myComponent.getContent()>
<cfoutput>#content#</cfoutput>

Attachments:

Comments:

Hi Jason, Thanks for reporting this issue. However, this is a duplicate of another bug [https://tracker.adobe.com/#/view/CF-4205250] We are tracking this issue as part of that other bug. Hence, I am withdrawing this bug as duplicate. Please feel free to comment if you have any concern.   -Nimit
Comment by Nimit S.
31412 | September 26, 2019 08:36:43 PM GMT
Nimit, Thanks for letting me know. The ticket you reference says it is fixed. Do you have any estimate on when that will be released? We would like to install the hotfix becuase of the security patches but this bug is holding us up. Jason
Comment by Jason S.
31413 | September 26, 2019 09:20:21 PM GMT
Jason, We are in the process of testing the patch. We can provide an early patch for this fix if you are interested. -Nimit    
Comment by Nimit S.
31420 | September 27, 2019 04:13:18 AM GMT