This error occurs in the following situations:
Note: As of Highcharts 5.0.8 it\'s possible to bypass this error message by setting Axis.prototype.allowNegativeLog to true, and add custom conversion functions. View live demo. It is also possible to use a similar workaround for colorAxis. View live demo.
This error occurs in the following situations:
As of Highcharts 5.0.8 it\'s possible to bypass this error message by setting Axis.prototype.allowNegativeLog to true and add custom conversion functions. ">View Live Demo. It is also possible to use a similar workaround for colorAxis. View live demo.
This error occurs when using the linkedTo option to link two axes of different types, for example a logarithmic axis to a linear axis. Highcharts can't link these because the calculation of ticks, extremes, padding etc. is different.
This error occurs if the series.data option contains object configurations and the number of points exceeds the turboThreshold. It can be fixed by either setting turboThreshold to a higher value, or changing the point configurations to numbers or arrays.
In boost mode, turbo mode is always on, which means only array of numbers or two dimensional arrays are allowed.
See plotOptions.series.turboThreshold
'}, 13:{title:"Rendering div not found",text:'This error occurs if the chart.renderTo option is misconfigured so that Highcharts is unable to find the HTML element to render the chart in.
If using a DOM ID when creating the chart, make sure a node with the same ID exists somewhere in the DOM.
'},14:{title:"String value sent to series.data, expected Number",text:"This happens if using a string as a data point, for example in a setup like this:
series: [{\n data: ["3", "5", "1", "6"]\n}]Highcharts expects numerical data values.
The most common reason for this error this is that data is parsed from CSV or from a XML source, and the implementer forgot to run parseFloat on the parsed value.
Note: For performance reasons internal type casting is not performed, and only the first value is checked (since 2.3).
"}, 15:{title:"Highcharts expects data to be sorted",text:"This happens when creating a line series or a stock chart where the data is not sorted in ascending X order.
For performance reasons, Highcharts does not sort the data, instead it requires that the implementer pre-sorts the data.
"},16:{title:"Highcharts already defined in the page",text:"This error happens if the Highcharts namespace already exists when loading Highcharts or Highstock.
This is caused by including Highcharts or Highstock more than once.
Keep in mind that the Highcharts.Chart constructor and all features of Highcharts are included in Highstock, so if using the Chart and StockChart constructors in combination, only the highstock.js file is required.
This error happens when setting chart.type or series.type to a series type that isn't defined in Highcharts. A typical reason may be that the module or extension where the series type is defined isn't included.
For example in order to create an arearange series, the highcharts-more.js file must be loaded.
This error happens when setting a series' xAxis or yAxis property to point to an axis that does not exist.
This error happens when applying too many ticks to an axis, specifically when adding more ticks than the axis pixel length.
With default value this won't happen, but there are edge cases, for example when setting axis categories and xAxis.labels.step in combination with a long data range, when the axis is instructed to create a great number of ticks.
In Highstock, when trying to add a point using the object literal configuration syntax, it will only work when the number of data points is below the series' turboThreshold. Instead of the object syntax, use the Array syntax.
"},21:{title:"Can't find Proj4js library", text:'Using latitude/longitude functionality in Highmaps requires the Proj4js library to be loaded.
'},22:{title:"Map does not support latitude/longitude",text:'The loaded map does not support latitude/longitude functionality. This is only supported with maps from the official Highmaps map collection from version 1.1.0 onwards. If you are using a custom map, consider using the Proj4js library to convert between projections.
'}, 23:{title:"Unsupported color format used for color interpolation",text:"Highcharts supports three color formats primarily: hex (#FFFFFF), rgb (rgba(255,255,255)) and rgba (rgba(255,255,255,1)). If any other format, like 3-digit colors (#FFF), named colors (white) or gradient structures are used in for example a heatmap, Highcharts will fail to interpolate and will instead use the end-color with no interpolation applied.
We've chosen to preserve this limitation in order to keep the weight of the implementation at a minimum.
"}, 24:{title:"Cannot run Point.update on a grouped point",text:"Running Point.update in Highstock when a point is grouped by data grouping is not supported.
This is not supported because when data grouping is enabled, there won't be any references to the raw points, which is required by the Point.update function.
Using the global.timezone option requires the Moment.js library to be loaded.
'}, 26:{title:"WebGL not supported, and no fallback module included",text:"This happens when the browser doesn't support WebGL,and the canvas fallback module (boost-canvas.js) hasn't been included OR if the fallback module was includedafter the boost module.
If a fallback is required, make sure to include boost-canvas.js, and that it's included before boost.js.
Please note that the fallback module is not intended as a fully-featured one. Rather, it's a minimal implementation of the WebGL counterpart.
"}, 27:{title:"This browser does not support SVG",text:"This happens in old IE when the oldie.js module isn't loaded.
If compatibility with IE versions 6, 7 and 8 is required, add the module after loading highcharts.js. In a website context, it's a good idea to load it in a conditional comment to avoid traffic overhead and dead code in modern browsers:
<!--[if lt IE 9]>\n <script src='https://code.highcharts.com/modules/oldie.js'></script>\n<![endif]-->"}, 28:{title:"Fallback to export server disabled",text:'
This happens when the offline export module encounters a chart that it can\'t export successfully, and the fallback to the online export server is disabled. The offline exporting module will fail for certain browsers, and certain features (e.g. exporting.allowHTML ), depending on the type of image exporting to. For a compatibility overview, see Client Side Export.
For very complex charts, it\'s possible that exporting fail in browsers that don\'t support Blob objects, due to data URL length limits. It\'s always recommended to define the exporting.error callback when disabling the fallback, so that details can be provided to the end-user if offline export isn\'t working for them.
'}, 29:{title:"Browser does not support WebAudio",text:"This happens when you attempt to use the sonification module on a chart in a browser or environment that does not support the WebAudio API. This API is supported on all modern browsers, including Microsoft Edge, Google Chrome and Mozilla Firefox.
"},30:{title:"Invalid instrument",text:"This happens when you try to use a sonification instrument that is not valid. If you are using a predefined instrument, make sure your spelling is correct.
"}, 31:{title:"Non-unique point or node id",text:"This error occurs when using the same id for two or more points or nodes.