Docs: Moved error doclets into markdown files.

errors/10/readme.md

@@ -0,0 +1,14 @@
+# Can't plot zero or subzero values on a logarithmic axis
+
+This error occurs in the following situations:
+
+- If a zero or subzero data value is added to a logarithmic axis
+
+- If the minimum of a logarithimic axis is set to 0 or less
+
+- If the threshold is set to 0 or less
+
+Note: As of Highcharts 5.0.8 it is possible to bypass this error message by
+setting Axis.prototype.allowNegativeLog to true and add custom conversion
+functions.
+[View live demo](https://jsfiddle.net/gh/get/library/pure/highcharts/highcharts/tree/samples/highcharts/yaxis/type-log-negative/).

errors/11/readme.md

@@ -0,0 +1,6 @@
+# Can't link axes of different type
+
+This error occurs if you are using the linkedTo option to link two axes of
+different types, for example a logarithmic axis to a linear axis. Highcharts
+can't link those because the calculation of ticks, extremes, padding etc. is
+different.

errors/12/readme.md

@@ -0,0 +1,9 @@
+# Highcharts expects point configuration to be numbers or arrays in turbo mode
+
+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 the turboThreshold option to a higher value, or changing your point
+configurations to numbers or arrays.
+
+See
+[plotOptions.series.turboThreshold](https://api.highcharts.com/highcharts#plotOptions.series.turboThreshold)

errors/13/readme.md

@@ -0,0 +1,6 @@
+# Rendering div not found
+
+This error occurs if the
+[chart.renderTo](https://api.highcharts.com/highcharts#chart.renderTo)
+option is misconfigured so that Highcharts is unable to find the HTML element to
+render the chart in.

errors/14/readme.md

@@ -0,0 +1,17 @@
+# String value sent to series.data, expected Number
+
+This happens if you pass in a string as a data point, for example in a setup
+like this:
+
+```js
+series: [{
+    data: ["3", "5", "1", "6"]
+}]
+```
+
+Highcharts expects the data values to be numbers. The most common reason for
+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).

errors/15/readme.md

@@ -0,0 +1,6 @@
+# Highcharts expects data to be sorted
+
+This happens when you are trying to create 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 is required that the implementer pre-sorts
+the data.

errors/16/readme.md

@@ -0,0 +1,7 @@
+# Highcharts already defined in the page
+
+This error happens the second time Highcharts or Highstock is loaded in the same
+page, so the `Highcharts` namespace is already defined. Keep in mind that the
+`Highcharts.Chart` constructor and all features of Highcharts are included in
+Highstock, so if you are running `Chart` and `StockChart` in combination, you
+only need to load the highstock.js file.

errors/17/readme.md

@@ -0,0 +1,7 @@
+# The requested series type does not exist
+
+This error happens when you are setting `chart.type` or `series.type` to a
+series type that isn't defined in Highcharts. A typical reason may be that your
+are missing the extension file where the series type is defined, for example in
+order to run an `arearange` series you need to load the `highcharts-more.js`
+file.

errors/18/readme.md

@@ -0,0 +1,4 @@
+# The requested axis does not exist
+
+This error happens when you set a series' `xAxis` or `yAxis` property to point
+to an axis that does not exist.

errors/19/readme.md

@@ -0,0 +1,8 @@
+# Too many ticks
+
+This error happens when you try to apply too many ticks to an axis, specifically
+when you add more ticks than the axis pixel length.
+
+With default value this will not 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.

errors/20/readme.md

@@ -0,0 +1,6 @@
+# Can't add object point configuration to a long data series
+
+In Highstock, if you try to add a point using the object literal configuration
+syntax, it works only when the number of data points is below the series'
+[turboThreshold](https://api.highcharts.com/highstock#plotOptions.series.turboThreshold).
+Instead of the object syntax, use the Array syntax.

errors/21/readme.md

@@ -0,0 +1,5 @@
+# Can't find Proj4js library
+
+Using latitude/longitude functionality in Highmaps requires the
+[Proj4js](http://proj4js.org)
+library to be loaded.

errors/22/readme.md

@@ -0,0 +1,8 @@
+# Map does not support latitude/longitude
+
+The loaded map does not support latitude/longitude functionality. This is only
+supported with maps from the
+[official Highmaps map collection](https://code.highcharts.com/mapdata)
+from version 1.1.0 onwards. If you are using a custom map, consider using the
+[Proj4js](https://proj4js.org)
+library to convert between projections.

errors/23/readme.md

@@ -0,0 +1,10 @@
+# Unsupported color format used for color interpolation
+
+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 just
+jumps to the end color.
+
+We have chosen to preserve this limitation in order to keep the weight of the
+implementation at a minimum.

errors/24/readme.md

@@ -0,0 +1,4 @@
+# Cannot run Point.update on a grouped point
+
+This happens in Highstock when a point is grouped by data grouping, so there is
+no reference to the raw points.

errors/25/readme.md

@@ -0,0 +1,5 @@
+# Can't find Moment.js library
+
+Using the global.timezone option requires the
+[Moment.js](https://momentjs.com/)
+library to be loaded.

errors/26/readme.md

@@ -0,0 +1,8 @@
+# WebGL not supported, and no fallback module included
+
+This happens when your browser does not support WebGL, **and** the canvas
+fallback module (`boost-canvas.js`) has not been included OR if the fallback
+module was included **after** the boost module.
+
+Make sure you include `boost-canvas.js`, and that it's included before
+`boost.js`.

errors/27/readme.md

@@ -0,0 +1,13 @@
+# This browser does not support SVG
+
+This happens in old IE when the `oldie.js` module is not loaded.
+
+If you need to target IE versions 6, 7 and 8, add the module after loading
+`highcharts.js`. In a website context, it is a good idea to load it in a
+conditional comment to avoid traffic overhead in modern browsers:
+
+```html
+<!--[if lt IE 9]>
+    <script src='https://code.highcharts.com/modules/oldie.js'></script>
+<![endif]-->
+```

errors/28/readme.md

@@ -0,0 +1,17 @@
+# Fallback to export server disabled
+
+This happens when the offline export module encounters a chart it can not 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](https://api.highcharts.com/highcharts/exporting.allowHTML)
+), depending on the type of image exporting to. For a compatibility overview,
+see
+[Client Side Export](https://www.highcharts.com/docs/export-module/client-side-export).
+
+For very complex charts, it is possible that export can fail in browsers that
+don't support Blob objects, due to data URL length limits. It is always
+recommended to define the
+[exporting.error](https://api.highcharts.com/highcharts/exporting.error)
+callback if you disable fallback, so that you can provide details to your users
+if export is not working for them.