tracker issue : CF-4203491

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

Bar Chart Node Issue

| View in Tracker

Status/Resolution/Reason: To Track//BugVerified

Reporter/Name(from Bugbase): Jim Romano / ()

Created: 11/21/2018

Components: Charting/Graphing

Versions: 2016,11.0,2018

Failure Type: Non Functioning

Found In Build/Fixed In Build: CF 11 Update 12 /

Priority/Frequency: Normal / All users will encounter

Locale/System: English / Win 2008 Server R2

Vote Count: 0

Hello,

We have a process that produces an "academic standing" bar chart that depicts the academic standing  for each of our students, compared to the rest of the class (S = superior, O = outstanding, etc). When the graph is generated in HTML, it renders properly, with an arrow pointing to the Node/series that relates to the student. This is done using the hook":"node:index=x" (where x = 0,1,2 or 3). But when the same graph is rendered to a JPG file, the arrow gets stuck in the corner, outside the plotting area. It is as if the node is null or something to that effect.

The charting process works fine for both html and jpg in version CF11 Update 11, but since Update 12, it does not render the JPG chart properly.

Also note that we installed CF 2018 and the problem still persists.

I’ve attached a standalone application that mimics our producing process and outlines the issue (standalone_app_chart_issue.zip). Please note the bar_bad_jpg.jpg and bar_good_html.jpg files that depict the issue. Simply deploy the application in the Update 12 environment and when “html” is selected, it works fine, but when “jpg” is selected, the arrow gets stuck in the corner.

Can you please give me an idea on what type of a timeframe we would be looking at for a resolution? Please don’t hesitate to contact me if more information is needed.

Thanks,
Jim Romano
romanoj@upstate.edu

Attachments:

Comments:

Hello, I submitted this bug 6 weeks ago and it is still in "Open" status. In looking at the AdobeTrackerFAQ.pdf document, shouldn't the status be changed to one of the nine Open statuses by now (i.e. Unverified, Unassigned, ToSpec, .... NeedsReview)? I am hoping to have an update on this soon so that I can plan accordingly. Is this a bug that will be addressed, and if so, what is the time frame for addressing/fixing? Thanks, Jim Romano (315) 464-8899 romanoj@upstate.edu
Comment by Jim R.
30085 | January 02, 2019 06:58:57 PM GMT
Hi, Can someone please provide an update on this bug so that we can plan accordingly. Thanks, Jim Romano (315) 464-8899 romanoj@upstate.edu
Comment by Jim R.
30118 | January 14, 2019 08:21:04 PM GMT
Hello! It looks like the last ColdFusion 2016 update was released in September 2018 (Update 7). Can I expect CF-4203491 to be included in the next update for ColdFusion release 2016? If so, is there an expected release date for this software update? We are in a bit of a bind and just want to know if we need to come up with a fallback plan for this, or if the software will be released in time for us to use. Thanks
Comment by Jim R.
30223 | February 11, 2019 04:17:11 PM GMT
Hello, It looks like this bug didn't make CF16 Update 8 or CF 2018 Update 2? Just curious if the bug list for these releases is accurate here => https://helpx.adobe.com/coldfusion/kb/bugs-fixed-coldfusion-2018-update-2.html#bugsfixed Thanks
Comment by Jim R.
30244 | February 13, 2019 05:28:21 PM GMT