Debugger

FusionCharts framework is designed to be non disruptive in execution. This means that in case of an error, the library would attempt recovery or graceful fallback or not render a chart. It should ideally not raise a JavaScript runtime error unless at places that is intended to raise error or when unexpected runtime errors occur.

For known error causing situations, this error event is raised with an error code and a message guiding to the possible cause of error. In situtations where charts behave unexpectedly, this event can be subscribed to discover possible errors.

Furthermore, these events are forwarded to the debugger output and when debugger is enabled, any such error event would be visible.

Certain implementation setup, browser or combination of the both cause unexpected scenarios during the rendering process of a chart. Whenever such situations are encountered that "may" cause issue but, during the propagation of the event, has been compensated for. FusionCharts keeps the developer in the loop by issuing this warning event.

Specifies how to format the output of the function that will accept output from the debugger.

The debugger of FusionCharts framework is cabaple of receiving all messages, logs and events that occur internally within the framework. However, the debugger has no way to output these messages. So, the debuggerCallback function needs to be attached to the debugger to which all such debug messages get forwarded. This lets to output a custom function to output the message at a desired location.

This method allows specifying the function to which the debugger output will be redirected, i.e., the activities of the debgger will be forwarded to a function provided through this method.

The FusionCharts debugger is not enabled by default. This method allows us to enable the debugger and also optionally provide basic debugger configuration.

The debugger works in conjunction with the browser's JavaScript console or any other special console-like implementation that you may have. To enable the debugger, call this function and pass a callback that outputs the message to the JavaScript console. The code would log the activities of every chart and the entire framework.

FusionCharts['debugger'].enable(true, function (message) {
    console.log(message);
});

If you have added this code right after including the fusioncharts.js script in a page that renders a single chart with id "myChart", your output would look somewhat like:

#1 [FusionCharts] fired "ready" event.
#2 [myChart] fired "beforeinitialize" event.
#3 [myChart] fired "beforedataupdate" event.
#4 [myChart] fired "dataupdated" event.
#5 [myChart] fired "initialized" event.
#6 [myChart] fired "beforerender" event.
#7 [myChart] fired "internal.loaded" event.
#8 [myChart] fired "internal.drawstart" event.
#9 [myChart] fired "dataloaded" event.
#10 [myChart] fired "internal.domelementcreated" event.
#11 [myChart] fired "loaded" event.
#12 [myChart] fired "drawcomplete" event.
#13 [myChart] fired "rendercomplete" event.

The output clearly shows that FusionCharts declared itself as ready and then the chart followed the routine of initialising itself, loading data, loading dependencies and then completing the rendering process. Had there been any error, it would have reflected in the output.

The debugger is not intended to be kept enabled on a production server since it has performance and > memory requirement overhead. It is meant for pre-production debugging only.

The debugging events error and warning pass on the "nature" of the error/warning as its argument. The value of this argument is one from the following list - giving a summary of the category of the error/warning raised.

When debugger is enabled, it forwards its output to a callback function as explained in debuggerCallback. The parameters that can be forwarded to this callback function can be adjusted based on the outputFormat set on the debugger. The outputFormat can be configured using the function outputFormat or by passing a format to the third parameter of the function enable.

The different output formats that the debugger provides are:

1. text - (default) Meant for simple text output from the debugger 2. event - Outputs the debugger messages in an event-like format, similar to eventListener. 3. verbose - Forwards all debugger messages and its associated arrguments as separate parameters.

AJAX runtime error. Raised when AJAX transactions raise error (security or others). The error message describes the nature of the error.

This error occurs when the FusionCharts constructor is called without the new keyword and also without passing a reference chart id as the parameter. In case you are rendering a new chart, ensure you do a new FusionCharts({}); or in case you are using the constructor as a getter, ensure you pass the chart Id (string) as first parameter.

This error occurs when a new chart is created (instantiated) with the an id that has been already assigned to an existing chart. Change the chart Id or dispose the other chart with the duplicate id.

The parameters passed on to the debugger callback function is in line with the value of outputFormats specified via outputTo.

FusionCharts JavaScript Library automatically determines the location where it was loaded from within the server. This it does by probing the <script> tag that has fusioncharts.js as a part of its src attribute. In case, this baseUri cannot be determined, this error is raised. Usually, this occurs when 1. fusioncharts.js has been loaded by a script / resource loader like requireJS or jQuery 2. fusioncharts.js has been renamed to something else and then loaded 3. fusioncharts.js is loaded from an external domain and as search browser has enforced cross-domain security restrictions.

FusionCharts can be configured to block loading of external JavaScript files by setting the internal constant BLOCK_EXTERNAL_SCRIPT_LOADING=true;. When this has been done, and some chart still needs external resource (script) that has not been manually loaded, this warning is issued. Ensure that the relevant files, such as, fusioncharts.charts.js, fusioncharts.widgets.js or other such files are already included in page before rendering the chart.

Since FusionCharts 3.4.0, the use of .swf suffix in chart types is deprecated since, Flash variant of charts are no longer supported. As such, a warning message is issued to notify developers to follow steps specified in '3.4.0 Migration Guide" to upgrade to the newest API.

Use of deprecated getChartFromId() or getMapFromId() global objects detected. Developer needs to upgrade to usage of the latest API and access chart instances using items or FusionCharts("chart-id").

The event name has not been provided while adding an event listener. Ensure that you pass a string to the first parameter of addEventListener.

The event listener passed to addEventListener needs to be a function.

The event listener passed to removeEventListener needs to be a function. Otherwise, the event listener function has no way to know which function is to be removed.

The event name passed to removeEventListener needs to be a string.

configureLink accepts a configuration object or an array of configuration objects as its parameter. Check whether some other data type has been passed or not.

setChartAttribute was called while chart data was not set or while chart data had an error. Check whether dataLoaded had been successfully fired before renderComplete and that none of the data load error events such as dataLoadError or {@link FusionCharts.event:invalidData} has been fired.

getChartAttribute accepts only a string or an array of attribute names as its paramater. Check whether your call to the function involved passing some other type of parameter.

The reference to the theme name provided as part of the chart data is not registered. Verify whether the corresponding theme file has been included in page.

This warning is issued when a chart's rendering process and the process of data being fetched from an URL has happened simultaneously. FusionCharts delays the rendering of the chart in anticipation of the arrival of data and in the process reduces redundant re-rendering of the charts. This warning is for information purpose only and does not require any action.

When an invalid data format has been passed to setChartDataUrl or other data- url-setter functions, this warnig is raised. The chart continues to use the last used data format in this situation. Ensure that you are using one of the data url prefixed formats specified in dataFormats.

When an invalid data format has been passed to setChartData or other data- setter functions, this warnig is raised. The chart continues to use the last used data format in this situation. Ensure that you are using one of the data formats specified in dataFormats.

This error is raised when FusionCharts data setter functions receive a dataFormats that is not internally registered successfully. It is very less likely that this error will be raised unless the implementation of FusionCharts is done using a non-standard way (e.g. directly chart.options.dataFormat has been changed.)

When an invalid data format has been passed to getChartData or other data- getter functions, this error is raised. Ensure that you are using one of the data formats specified in dataFormats.

This error is encountered when either the source or the target parameter of transcodeData receives a value that is not part of the list of data formats in dataFormats. Note that url-prefixed data formats are not intended to be supplied to the transcoder function.

FusionCharts supports construction parameters to have dataSource and dataFormat to be provided. As such charts render with the data provided during construction. However, if a chart has been rendered by calling render, but no data has been provided to the chart, this warning is raised. Unless this is intentionally implemented, try furnishing the chart with data before .render() is called.

When browser lacks native support for JSON, FusionCharts uses internal JSON parser. This error is raised when even the internal parser fails to initialise. The application or implementation needs to be debugged to identify the cause of this issue.

Every instance of FusionCharts has a set of functions that are specific to a chart type and set of functions that are available only after a chart has been rendered. In case a call to such functions are made before the chart has been completely rendered, this error is raised. The error message includes the name of the function in question.

Ensure you programmatically interact with a chart (with respect to the function involved,) after the renderComplete event has been fired.

This is an error that occurs when FusionCharts failed to render the chart. When render is called, it expects the rendering process to complete and a corresponding chart be available on the browser DOM having the same id as the chart id.

• Check whether the chart being rendered has a unique ID. - Ensure that the chart container being rendered in is not within a frame or iframe. - Ensure that the container being rendered in is not deleted or manipulated during the rendering process. Avoid updating the innerHTML of the container once a chart has been rendered within it; use standard DOM append, prepend, insert, remove functions. - Check whether any third-party JavaScript or JavaScript UI library is not interfering with the rendering process.

This error is raised when the chart cannot internally access the DOM functions of the rendered chart. The likely cause of this issue is an internal failure to enumerate the basic DOM functions that are needed for the chart to render. Ensure that your browser has not enforced cross-domain script security restrictions that was intended.

FusionCharts raises this error to ensure that the charts function reliably on older Internet Explorer browsers (IE 8 and below.) Ensure that you have unique name for your chart id and that it does not correspond to any global variable, DOM element id or frame name.

FusionCharts could not find the container DOM element while rendering chart. Ensure that a DOM element exists which has an id attribute same as the one provided in renderAt construction parameter or when passed to the render function.

The id of the container element provided has more than one element with the same id. This would cause problems in referring to the correct chart during its operation.

Ensure that no other DOM element exists on the page with the same id attribute as of the container element where the chart is supposed to be rendered.