tracker issue : CF-4205250

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

Nest CFOUTPUT error in hotfix 5 (hf-2018-00005-315699)

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/Fixed

Reporter/Name(from Bugbase): Kevin K. / ()

Created: 09/25/2019

Components: Core Runtime

Versions: 2016,2018

Failure Type:

Found In Build/Fixed In Build: hf-2018-00005-315699 / 316194

Priority/Frequency: Critical /

Locale/System: / Win 2016

Vote Count: 32

Problem Description:

A <CFOUTPUT> tag at a higher level (i.e. outside of a function call) will cause a nested tag error if the function call contains a <CFOUTPUT QUERY="">.

Steps to Reproduce:

test.cfm:

{code:java}
<CFSET testObj = new test() />
<CFOUTPUT>#testObj.Test()#</CFOUTPUT>
{code}


test.cfc:

{code:java}
<cfcomponent>
    <cffunction name="test">
        <CFQUERY NAME="GetData">
        SELECT SomeCol FROM SomeTable
        </CFQUERY>
        <CFOUTPUT QUERY="GetData">
            <!--- error --->
        </CFOUTPUT>
    </cffunction>
</cfcomponent>
{code}

Actual Result:

 "Invalid tag nesting configuration."

Expected Result:

No error

Any Workarounds:

Rollback to Update 4

Attachments:

Comments:

Confirmed after rollback that this does not cause an error prior to update 5.
Comment by Kevin K.
31377 | September 25, 2019 01:04:26 PM GMT
I've just attached working code samples using the cfartgallery, courtesy of Charlie Arehart.
Comment by Kevin K.
31378 | September 25, 2019 04:00:02 PM GMT
Installed this update (2018.0.05.315699) in our test environment today (9/25/2019) and I've experienced the same issue.
Vote by Neil L.
31380 | September 25, 2019 05:27:27 PM GMT
This issue is present on our servers as well.
Comment by dakota c.
31379 | September 25, 2019 05:49:33 PM GMT
I just had yet another client report the problem.
Comment by Charlie A.
31391 | September 25, 2019 10:02:38 PM GMT
This is the same problem I am experiencing and reported in https://tracker.adobe.com/#/view/CF-4205257
Vote by Vincent K.
31403 | September 26, 2019 03:25:32 PM GMT
Why does this indicate a reason code of "fixed", without a value for "fixed in build" (as I wrote, on 9/25/19)? How is it "fixed", and/or how does one obtain the fix? (I can't imagine that the fact that there's an offered workaround in the report would be a reason to regard the problem as 'fixed".)
Comment by Charlie A.
31402 | September 26, 2019 05:29:03 PM GMT
Thanks for reporting the bug , we have fixed this in our development branch and once testing is done we shall communicate our plans to make this fix available .
Comment by Suresh J.
31417 | September 26, 2019 07:22:52 PM GMT
As a result of this error (which I've verified on a staging server), means we can't upgrade this in production until this bug is fixed.
Vote by James M.
31431 | September 27, 2019 04:05:02 PM GMT
Confirmed here too. Calling a cfc function with a <cfoutput query="xxx"> tag throws the error when an <cfoutput> surrounds the call the cfc function. Exactly as described. NEED FIX ASAP -- as we are all vulnerable until we can install the original update.
Vote by Michael P.
31438 | September 27, 2019 07:02:57 PM GMT
Adding to Suresh's comment, I have been told elsewhere that Adobe does now have a fix for this. You need to ask them for it. They don't say here how to do it, but try cfsup@adobe.com. BTW, it appears they will not be "refreshing" the update, so those with the error will need to request this. I think that's unfortunate, as people will be bit by this only if/when they upgrade and if/when they do testing, and they may not know to look here, and they may not know they can even ask Adobe for a fix. (And this is not the only bug in this most recent update.) Grr.
Comment by Charlie A.
31437 | September 27, 2019 08:12:24 PM GMT
Vote +1 : NEED FIX ASAP. As this is preventing the critical vulnerabilities update for update 12 on CF2016. Another simple example to reproduce the error is at : https://community.adobe.com/t5/ColdFusion/Errors-after-update-12-on-coldfusion-2016/m-p/10636488 Rolled Back to Update 11.
Vote by Nas K.
31441 | September 28, 2019 02:17:55 AM GMT
Guys, this is crazy. We have live client deployments that are suddenly getting errors because of this. Please fix this and give us a patch asap!
Comment by Nick G.
31444 | September 28, 2019 06:25:56 PM GMT
Hi All, This issue is fixed now. Please reach out to ColdFusion support @ [cfinstal@adobe.com|mailto:cfinstal@adobe.com] to get the patch. -Nimit
Comment by Nimit S.
31459 | September 29, 2019 05:30:44 PM GMT
This issue touches the very foundation of CF and should be marked as critical.
Comment by Nas K.
31467 | September 29, 2019 11:45:32 PM GMT
hi nimit, is this patch going to be available for cf2016?
Comment by luke m.
31475 | September 30, 2019 06:33:26 AM GMT
According to Adobe's website, CF 2016 is under core support until 2/17/2021 so I sure hope this patch is available for CF2016. https://helpx.adobe.com/support/programs/eol-matrix.html#CD
Comment by Vincent K.
31479 | September 30, 2019 03:09:26 PM GMT
Hi Luke & Vincent, Yes, this patch is available for ColdFusion 2016 as well. You can contact ColdFusion Support @ [cfinstal@adobe.com|mailto:cfinstal@adobe.com] to get the patch. -Nimit
Comment by Nimit S.
31480 | September 30, 2019 04:18:43 PM GMT
I received the patch (via Dropbox). I placed the JAR file in the lib/updates sub-directry, restarted the ColdFusion Application service (Windows) and continued to experience the same error using Windows/CF2016u5. I killed the process, allowed it to restart and there wasn't any change. Has anyone received the patch and had it fix the CF error? (Just curious.)
Comment by James M.
31482 | September 30, 2019 06:43:17 PM GMT
Is the fix only good for update 12? I'm still waiting for them to send it to me. I'm on update 12 and getting the same error as you.
Comment by Dave D.
31483 | September 30, 2019 06:46:30 PM GMT
Sorry... I meant CF2016 update 12 (not 5). I'm using 2016,0,12,315717 to be exact.
Comment by James M.
31484 | September 30, 2019 06:53:12 PM GMT
James,  Are you getting any error while starting the CF server? Can you please share the settings summary and coldfusion-out.log/coldfusion-error.log to investigate it further? -Nimit
Comment by Nimit S.
31485 | September 30, 2019 07:31:17 PM GMT
The patch provided does not work for me either. Error: Invalid tag nesting configuration. 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.
Comment by Dave D.
31486 | September 30, 2019 07:35:18 PM GMT
No start up errors for me. I think what I may have been testing was actually badly nested cfml. I migrated my test script to a non-updated CF2016u4 server and it threw the same error. I modified the same sample code in the report (to use CFDirectory instead of CFQuery) and it worked correctly.
Comment by James M.
31487 | September 30, 2019 08:24:09 PM GMT
James, Can you please confirm if it is still an issue or not?   Dave, Can you please share the exception stack trace and sample code that you are trying? I will try the same code at my end.   -Nimit
Comment by Nimit S.
31488 | September 30, 2019 09:02:51 PM GMT
For me, the demonstration script that is available with this bug report does not cause any CF error when the provided patch is applied.
Comment by James M.
31489 | September 30, 2019 11:14:04 PM GMT
I've attached sample script showing it broken. It appears related to the <cfoutput> within a <cfcomponent>. I show two versions, one where it is and one were it is not. Pretty simple code. Seems like a serious bug.
Comment by Dave D.
31491 | October 01, 2019 12:29:14 AM GMT
See nested-query-loop.zip attachment.
Comment by Dave D.
31492 | October 01, 2019 12:29:42 AM GMT
Unzip and place nested-query-loop directory in root and navigate to /nested-query-loop/index.cfm
Comment by Dave D.
31493 | October 01, 2019 12:30:38 AM GMT
Still broken for our codebase after installing the patch for CF 2016 Linux. Installing the patch DOES fix the code as described in this ticket (test.cfm and test.cfc) for CF 2016. However, if youe take it up one more level using a <cfinclude> it breaks again. To re-create error, create one more file that includes the test.cfm via a <cfinclude> surrounded by <cfoutput>: ------------------- test-include.cfm --------------- <cfoutput> <cfinclude template="test.cfm"> </cfoutput> ------------------------------------------------------ Returns the same error message as the original ticket states.
Comment by Michael P.
31494 | October 01, 2019 02:44:25 AM GMT
First, now that <cfloop> has all of <cfoutput>'s looping functionality, <cfoutput>'s looping functionality could be marked deprecated and the docs could recommend that users use <cfloop> instead. Next, since <cfoutput>'s encodefor attribute isn't a substitute for context-specific encoding, <cfoutput> itself could be deprecated :) JK, but.. Some (including me sometimes) just slap <cfoutput> at the top of a file, and </cfoutput> at the bottom, and be done w/ that tag. So, IMO, Michael P.'s example is not edge-case, b/c a <cfoutput> loop could be an arbitrary number of levels deep inside <cfoutput>-wrapped includes and function calls. What ticket is this issue fixing? Thanks!, -Aaron
Comment by Aaron N.
31495 | October 01, 2019 05:43:19 AM GMT
+1 ...........
Vote by Aaron N.
31500 | October 01, 2019 06:42:00 AM GMT
Hi Michael & Dave, I have tried both the suggestion for the repro case but I am unable to repro it with the patch. Can you please share the settings summary and exception stack trace so that I can confirm the patch is applied successfully? -Nimit
Comment by Nimit S.
31499 | October 01, 2019 07:06:45 AM GMT
Just to confirm, I was given patch hf201600-4205269 and running CF2016 Update 12. I this the right patch?
Comment by Dave D.
31511 | October 01, 2019 03:03:16 PM GMT
I placed the patch under /hf-updates instead of /lib/updates on my dev box. When I moved it to the right directory, my broken example works. I also added multiple levels deep as Michael P. suggests. It was still working with the patch. I will confirm in production.
Comment by Dave D.
31512 | October 01, 2019 03:19:37 PM GMT
I tested in our production code and I still get "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." The example I gave must not fully represent our live code. The patch did fix the example, but not in production. I'll continue to try and track down the cause and provide an updated example.
Comment by Dave D.
31513 | October 01, 2019 03:42:05 PM GMT
Ok, it found out where the issue still exists - which is slightly different from the test code. If called from a separate page via <CFINCLUDE> that is surrounded by <CFOUTPUT> and the function in the cfc is called via <CFINVOKE> instead of directly instantiating the cfc via 'new' or 'createObject' , it will throw the error: Detail: A query driven queryloop tag is nested inside a queryloop tag that also has a query attribute. If the <CFINCLUDE> is not surrounded by <CFOUTPUT> it will not throw the error. I've got test files created that i attached above: test-cfinclude-cfinvoke.zip - Michael
Comment by Michael P.
31514 | October 01, 2019 04:52:53 PM GMT
EDIT (2019/10/03): I was originally given a hotfix for CF2018 instead of CF2016. I contacted Adobe Support and got the correct hotfix, installed, and everything is working properly now. Please refer to my comment on the left side for more detailed info. ---------------------------------- +1. Created this account just to vote. I contacted cfinstal@adobe.com to receive the hotfix file. I renamed the .zip file to .jar as instructed, placed it in the cfusion/lib/updates folder, restarted CF Application Windows service, and still received the nesting code error. Tried putting the .jar file in the cfusion/hf-updates folder, restarted, and still receiving the error. I even went as far as trying to install the .jar file manually from the command line with: java -jar <jar file location> Received the error: "no main manifest attribute" and the file was not installed. It seems as though CF doesn't even try to read the hotfix file. While I have CF running, I cannot open an older hotfix file in the cfusion/lib/updates folder because it is locked (being used by the CF process). However, I can open this newer hotfix file as if CF isn't even reading it at all. I'm no java expert by any means, but I'm getting the impression this hotfix was not properly compiled.
Vote by Jason H.
31520 | October 01, 2019 08:18:00 PM GMT
+1 for receiving the error. Created this account just to vote. I contacted cfinstal@adobe.com to receive the hotfix file. I renamed the .zip file to .jar as instructed, placed it in the cfusion/lib/updates folder, restarted CF Application Windows service, and still received the nesting code error. Tried putting the .jar file in the cfusion/hf-updates folder, restarted, and still receiving the error. I even went as far as trying to install the .jar file manually from the command line with: java -jar <jar file location> Received the error: "no main manifest attribute" and the file was not installed. It seems as though CF doesn't even try to read the hotfix file. While I have CF running, I cannot open an older hotfix file in the cfusion/lib/updates folder because it is locked (being used by the CF process). However, I can open this newer hotfix file as if CF isn't even reading it at all. I'm no java expert by any means, but I'm getting the impression this hotfix was not properly compiled.
Comment by Jason H.
31516 | October 01, 2019 08:19:23 PM GMT
Thanks Dave for the confirmation. I am glad it worked for you.    
Comment by Nimit S.
31517 | October 01, 2019 11:00:31 PM GMT
Michael, I am able to repro the issue with the sample code you provided. Please contact me @ [nimsharm@adobe.com|mailto:nimsharm@adobe.com] so that I can assist you further -Nimit
Comment by Nimit S.
31518 | October 01, 2019 11:02:48 PM GMT
Hi Jason H, This patch should only be placed inside <instance_name>/lib/updates folder. There can be other issue if it is not getting loaded. Can you please share the settings summary and server start up log file @ [nimsharm@adobe.com|mailto:nimsharm@adobe.com] to investigate it further . -Nimit
Comment by Nimit S.
31519 | October 01, 2019 11:15:26 PM GMT
I think Michael has identified the difference between our production code and the example I provide. As a workaround for us, we've decide to just swap out the <cfoutput> tags with <cfloop> where appropriate. However; the example Michael posted is most like our prod issue. "If called from a separate page via <CFINCLUDE> that is surrounded by <CFOUTPUT> and the function in the cfc is called via <CFINVOKE> instead of directly instantiating the cfc via 'new' or 'createObject' , it will throw the error"
Comment by Dave D.
31521 | October 02, 2019 01:58:13 AM GMT
Hi Dave, I have shared the patch with Michael and he has confirmed that the patch is working at his end. You can either contact [cfinstal@adobe.com|mailto:cfinstal@adobe.com] or [nimsharm@adobe.com|mailto:nimsharm@adobe.com] to get the patch.   -Nimit
Comment by Nimit S.
31522 | October 02, 2019 07:56:46 AM GMT
We installed CF2016 HF12 last night on our dev server and this morning all of my developers are a bit peeved at me as all of our websites appear to be impacted by this. Emailed requesting the patch file and I'll report back fix status to see if it resolves all of our issues or if we have the extra problem case others have reported.
Comment by Leith T.
31526 | October 02, 2019 01:28:10 PM GMT
We put the provided hf201600-4205269 in the lib\updates folder and restarted CF. A developer reported an issue they were having stopped but we've found others that continue to happen. I provided a code snippet to the support email I had to get the jar. In essence we have a CFOUTPUT of a query that calls a function that itself then does a CFQUERY and then another CFOUTPUT of that query and the issue happens on the call of the function. This code is in a CFC and is invoked as a method call to an object instance.
Comment by Leith T.
31538 | October 03, 2019 01:21:13 PM GMT
I've attached the hf201600-4205269.jar hotfix that I was given from Adobe support. Note that this was for Coldfusion 2016. This has been working great so far for me. Haven't experienced any nested CFOutput query loop errors since applying the hotfix. We haven't tested it in production just yet, but our dev server is practically identical to prod so I have high hopes. The Adobe support guys recommended deleting everything in this folder before restarting CF with the hotfix: cfusion\wwwroot\WEB-INF\cfclasses I backed mine up first, just in case. You'll have to stop the CF Application service before deleting, obviously. I don't know what this directory is for exactly, but I did notice that some of my CFC functions' names were cached in here. So yeah, guessing it's some sort of cache. Step 1: Make sure your CF server is updated to version 12. Step 2: Stop the CF service and place the jar in - \ColdFusion2016\cfusion\lib\updates folder Step 3: Restart the service and test your application. You can confirm the hotfix was applied by logging into the CF Admin page > Settings Summary > Server Details > Update Level. The hotfix JAR file location should be there.
Comment by Jason H.
31541 | October 03, 2019 08:24:14 PM GMT
@ All: This should work after the latest patch that is being shared by Adobe Support team, If anyone is still facing problems please let us know the exception with a standalone reproducible case for us to verify. Thanks
Comment by Ashudeep S.
31562 | October 08, 2019 07:22:12 AM GMT
@Ashudeep: hf201600-4205269.jar hotfix does not address all errors caused by 2016 update 12 - at least not on our test server. The errors we are still experiencing are two levels deep (cfoutput around a cfinclude that then uses cfinvoke to call a cfc with cfoutput query). I have shared the code with Sandip at cfsupport and I am still waiting for an update. Thanks
Comment by Shirzad K.
31563 | October 08, 2019 11:44:29 AM GMT
Can someone share here the hotfix jar for CF2018? What Jason offered (in the "attachments" section here) was the jar for CF2016 only. If anyone could offer it either as an attachment or a link (that Adobe may have shared), that would be appreciated. Of course, it would be best if it was offered by someone from Adobe, so that we know it's an official hotfix file. Also, really hoping someone will address how some folks say that the fix is NOT solving the problem completely for them. See Shirzad's comment just before mine, for instance. It's hard to put full faith in this fix, otherwise.
Comment by Charlie A.
31567 | October 08, 2019 06:55:59 PM GMT
We've been waiting to get the re-released patch from support because I'm not going to download a jar file from a non-Adobe employee to put on my servers.
Comment by Leith T.
31575 | October 09, 2019 12:53:17 PM GMT
Leith, Please send an email @ [nimsharm@adobe.com|mailto:nimsharm@adobe.com] so that I can share the patch with you. -Nimit
Comment by Nimit S.
31576 | October 09, 2019 04:43:00 PM GMT
Installing the patch for ColdFusion 2018 Update 5 eliminated my coldfusion.tagext.QueryLoop$InvalidQueryNestingException: Invalid tag nesting configuration.
Comment by Adrian W.
31583 | October 10, 2019 03:15:12 PM GMT
RE: Installing the patch for ColdFusion 2018 Update 5 I also deleted all files from \ColdFusion2018\cfusion\wwwroot\WEB-INF\cfclasses before restarting (per ColdFusion support instructions).
Comment by Adrian W.
31584 | October 10, 2019 03:20:58 PM GMT
This bug seems to still be occurring in our environments. It appears that the custom patch we received is being reverted/lost and the errors end up reoccurring. Restarting ColdFusion will temporarily fix the issue, however, it eventually resurfaces again... Is anyone else still experiencing this problem? All files have been deleted from the class folder.
Comment by dakota c.
31648 | October 18, 2019 02:07:05 PM GMT
We've noticed this error is also produced if the component (that contains a cfoutput block) is called from within a cfmail tag.
Comment by Nathan B.
31670 | October 21, 2019 08:23:19 PM GMT
We've noticed this error is also produced if the component (that contains a cfoutput block) is called from within a cfmail tag.
Vote by Nathan B.
31671 | October 21, 2019 08:44:37 PM GMT
QUESTION: What's the official status on this bug? The status changed from "normal" to "critical" today (10/31/2019), but the status of this is already "fixed"? If fixed, why are there still reports of pre-existing CFML code still not working properly. NOTE: I've installed the patch on a development CF2016 server, but don't have any way of testing the 12 update + privately distributed patch against every codebase in order to determine if it reliably works everywhere. As a result, I'm not updating anything to 12 and will probably wait until 13 (or a publicly available updater with an announcement) is released.
Comment by James M.
31740 | October 31, 2019 01:44:39 PM GMT
Tracker appears to be very casual and doesn't maintain a changelog to track changes in status. Here's the latest: 11/3/2019 08:00-ish Pacific - Component updated to 'Core Runtime' - Component updated from 'Installation/Config : Hotfix Installer' to an empty value
Comment by James M.
31741 | November 04, 2019 02:29:19 PM GMT
I reached out to both cfinstal@adobe.com and nimsharm@adobe.com a week ago and have yet to receive a reply. How are we supposed to reliably get the patch for our 2016 and 2018 CF installs? Has anyone else failed to receive an email reply when reaching out to them? I see someone posted the jar file but I'd prefer to receive it directly from someone at Adobe.
Comment by City A.
31742 | November 04, 2019 04:38:25 PM GMT
Hi City A, Please share your email address with us and we will share the patch with you.
Comment by Abhishek J.
31743 | November 05, 2019 01:36:40 PM GMT
Abishek, how about doing a blog post instead, like was done for the updated connector fix for the same Sep 2019 uodate: https://coldfusion.adobe.com/2019/10/error-accessing-coldfusion-administrator-using-connector-port/
Comment by Charlie A.
31744 | November 05, 2019 02:19:19 PM GMT
I agree with Charlie A. Why does this particular patch seem so secretive that people must contact Adobe directly to obtain it? Seems like such a strange practice. Anyways, can an Adobe employee please email both the 2016 and 2018 patches.
Comment by City A.
31745 | November 05, 2019 02:37:46 PM GMT
UPDATE: The update sent by Adobe did resolve my issue. You will not want to clear the previous update in the /lib/updates folder but add that jar to the folder together - that kind of bit me for a second but the install was clean besides that (and no where did they say to do it - I just made a bad assumption). It's breaking my apps too and I'm at the point where I cannot revert back due to security requirements/scanning but need this fixed. It's been nearly two months!
Vote by JONATHAN V.
31756 | November 06, 2019 12:18:10 PM GMT
And Adobe, if you do create a post, or a readme, please clarify for people some things that comments and vote comments here show have tripped people up: a) how they're to copy the new hf jar file they're given and paste it into the lib/updates folder of the cfusion directory of cf, and then restart cf b) how they're NOT to remove any chf jar there (that's the jar that the cf update put there, and the hf jar extends that. Note also that the next cf update will itself automatically remove any jars in the folder, thus cleaning up after this fix) c) and finally. for those NOT in CF standard, (for those on cf enterprise, trial, or developer editions), how they need to also put the new jar in the lib/updates folder of any sibling folder to cfusion which represents the name of any additional "instance" of cf, that they or a colleague may have created. Then restart that instance. It could be that any mistake in the above steps would explain how some say "I applied the update and still have the bug". Or worse, in the case of b, how whole new classes of errors may crop up (if people mistakenly delete the chf jar that the cf update put there). These are all problems that we dealt with in cf9 and before, when people were always having to manually copy/paste hf jar files, especially for security fixes then. We've been blessed since 2012 (cf10) to have this more automated cf update process. But when such fixes to updates are needed, people need to be reminded of these important points.
Comment by Charlie A.
31746 | November 06, 2019 02:26:10 PM GMT
Hi City A, We have sent the patch to the provided email address. Please acknowledge once you receive it. -Nimit
Comment by Nimit S.
31747 | November 06, 2019 04:24:55 PM GMT
Hi City A/Charlie, Keeping the fix secret is not our intent any day. We are already working on an update which involves few other customer reported issues. The cumulative update will be released by Mid November to everyone. Meanwhile for users who are blocked by this bug we are providing a hot fix through the support channel and also encouraging them to reach out to us directly. -Nimit
Comment by Nimit S.
31748 | November 06, 2019 04:27:54 PM GMT
Completely agree with Charlie, if manual hotfix updates are to continue going forward. I understand the need for an occasional hotfix, so Charlie's comments should definitely be taken on board. Suggestion: in this particular case, rather than supplying these hot fixes on an ad hoc basis to only those who know to come here and ask for them, how about putting together Update 12a, which includes all the hot fixes, and releasing it to everyone through the normal channels. That way we all get the security fixes from Update 12 AND the fixes to these issues (which I dare say most if not all installations will experience). Just my 2c.
Comment by Michael C.
31749 | November 06, 2019 04:35:08 PM GMT
Hi Nimit, I received the patch for 2016. The email got caught in our quarantine so it appeared as though no one had responded. Thank you for your reply. The patch fixed the issue on our CF2016 server. However, I would like to echo Charlie and Michael. Why not post an article or blog about this issue?
Comment by City A.
31750 | November 06, 2019 05:16:22 PM GMT
Hi All, As everyone knows this issue has been been fixed now. The fix for this issue will be available as part of an upcoming update of ColdFusion 2016 and ColdFusion 2018. These updates will be released by mid November. Hence, I am closing this bug. -Nimit
Comment by Nimit S.
31751 | November 06, 2019 05:35:54 PM GMT
Wait, what? You say "everyone knows this issue has been fixed now", and so you will close it. But everyone following this thread will also "know" that at least 3 people have reported that the fix (as it stands) did not resolve the problem for them: in reverse order reading above, Dakota, Shirzad, and Leith, to name a few. So Nimit, are you saying that you have heard from them and their issues are resolved? Or that their issues are so different as to be a different bug? Or is it that they have not replied to you all directly with more detail? I just want to hear from you that in closing this bug, whether you are or are not considering these folks who said the problem remained, even with the fix. (Though I will say again, it could be that they mis-applied the manual implementation of this hf jar file. Since we only have first names and initials, I have no way to reach them all directly to ask. And I don't know if you guys would do that.)
Comment by Charlie A.
31752 | November 06, 2019 05:53:37 PM GMT
gg
Comment by Matthew L.
31753 | November 06, 2019 05:58:38 PM GMT
oops.. sorry for that miscomment^ Got this issue resolved by following directions from CF support through their email, as well as the comment by Jason H. Charlie A. goes through a more detailed explanation as well. Thanks
Comment by Matthew L.
31754 | November 06, 2019 06:00:10 PM GMT
Charlie, I have received the confirmation from Shirzad and Leith that the fix is working at their end. However, I do not have any confirmation from Dakota till now. -Nimit
Comment by Nimit S.
31755 | November 06, 2019 06:02:38 PM GMT