DHTMLX Docs & Samples Explorer

Index
others

### Incorrect order of js files

Symptom: One of next error appears

1. “dhtmlx is undefined”
2. “dhtmlxExcell is undefined”
3. “dhtmlX[Something] is undefined”

Solution: Check order of js files, it must be

1. dhtmlxcommon.js
2. dhtmlx[Component].js ( dhtmlxgrid.js for grid, dhtmlxtree.js for tree and etc. )
3. any extensions for the component

In case of dhtmlxgrid

1. dhtmlxcommon.js
2. dhtmlxgridcell.js
3. dhtmlxgrid.js
4. any extensions for the grid

In case of layout, windows, tabbar, accordion components you need to include dhtmlxcontainer.js as well

Alternative solution: full package contains dhtmlx_full.zip ( dhtmlx_standard_full.zip ) archive, which contains “all included” dhtmlx.js, which can be used instead of separate js files. Including this single file is equal to including all base and extension files at once.

### Incorrect XML

Symptom: “Incorrect XML” message.

Reasons:

1. Incorrect XML structure - it may be caused by incorrectly formed XML tags, or by using some special content (& < > chars) inside the tag values. The simplest way to detect the reason for an XML error is open the url used for XML loading in a separate browser window. It will show the error details and exact position of the problematic code;
2. (IE specific) Usage of incorrect content type - if you are using dynamic XML source (generate it by the script), you need to send the data with Content-type:text/xml;
3. (FF specific) In case of FF the problem may occur because of any whitespace before <?xml declaraton (the declaration must be the first text in the output).

If you are using a dynamic XML source, pay attention to the fact that the output during a stand alone test may not be equal to the output during the usage of the same feed with the component. You can try to use the debug version of dhtmlxcommon to check which urls are used and which xml output was sent during the data loading.