System Error Occurred

12. Editor: A organisation error has occurred.

When an Editor asking is fabricated and the returned information is not in the expected format (JSON), Editor will show an error message stating that an error has occurred:

• 1.3.3+: A system mistake has occurred (more information)
• 1.3.2-: An error has occurred - Delight contact the system administrator

This is a generic error message that Editor displays in the UI when it is unable to parse the returned data as JSON.

Diagnosis

If the server didn't reply to Editor's Ajax request with valid JSON data, we demand to know what it did reply with, and then we can take corrective activeness. Typically, the response volition consist of an error bulletin from the program on the server which is existence used to create the JSON, which will exist the starting bespeak for resolving the upshot fully.

Server data

Modern browsers all come with built in developer tools, which can be used to detect out what data the server is responding to the Editor Ajax asking with. Instructions on how to do this with your browser are shown below.

Safari

1. Open preferences

two. Enable developer menu

3. Prove page resources

iv. Ajax response

1. By default Safari hides its built-in developer tools. If you don't have a Develop bill of fare shown in Safari it needs to be enabled. If yous do, jump to stride iii.
   • Open up the Safari menu and select Preferences...
2. Enable the developer menu in the Advanced tab
   • Click the Advanced tab in the Preferences window
   • Cheque the box for Show Develop menu in menu bar option
   • Close the preferences - the Develop menu will now be shown
3. View the resource the folio has loaded
   • Select the Bear witness Page Resources option from the Develop bill of fare.
   • The developer console will testify at the lesser of the page
   • Reload the page so Safari tin can capture all network requests
4. Details nearly the Ajax asking are shown.
   • Safari will show a list of all resources (images, scripts etc) which take been loaded for the page. Locate the Ajax request that has been fabricated to the server and click it. Safari will show detailed data about the request.
   • Note that on pages with a big number of resources, Safari will group the resources by type into folders. If this happens on your site, look for the "XHRs" binder for the Ajax requests.

Please note that these instructions were written with Safari seven every bit the version used. Newer versions might have slightly different steps.

Chrome

1. Open up debugger

2. Console displayed

3. Show Network tab

iv. Ajax response

1. To access the developer tools in Chrome:
   • Mac: Admission the View > Developer > Developer Tools menu option.
   • Windows: Click the Chrome menu (to the right of the address bar) and select Tools > Developer Tools.
2. The Developer tools are shown at the bottom of the current browser window. Chrome will show the Javascript console by default.
   • Click on the Network tab to view network requests
   • Refresh the page to allow Chrome to capture all requests
3. The network panel will show all of the requests made by Chrome to load the page.
   • Click the XHR option at the bottom of the window to reduce the requests to just the Ajax (XHR) requests.
   • Double click the Ajax asking made by Editor
4. Details about the Ajax request are shown.
   • Click the Response tab in the Ajax view to encounter the exact data that was returned from the server. This is what we are interested in!

Delight note that these instructions were written with Chrome 31 Mac equally the version used. Newer versions, or those on unlike platforms might have slightly unlike steps.

Firefox

ane. Open debugger

ii. Network requests

3. Ajax requests

four. Ajax response

1. To access the developer tools in Firefox:
   • Mac: Access the Tools > Web Programmer > Network menu choice.
   • Windows: Click the Firefox carte (top left of the window) and select Web Developer Network choice.
2. The Developer tools are shown at the bottom of the electric current browser window.
   • Refresh the page to permit Firefox to capture all requests
3. The network panel volition evidence all of the requests fabricated past Firefox to load the page.
   • Click the XHR option at the bottom of the window to reduce the requests to just the Ajax (XHR) requests.
   • Double click the Ajax request made by Editor
4. Details virtually the Ajax request are shown.
   • Click the Reponse tab in the Ajax view to see the exact data that was returned from the server. This is what we are interested in!

Please note that these instructions were written with Firefox 26 Windows as the version used. Newer versions, or those on different platforms might accept slightly unlike steps.

IE

ane. Open debugger

2. Element inspector

3. Show Network tab

4. Ajax response

4. Ajax response

1. To access the developer tools in IE:
   • Press F12 or,
   • Click the tools carte (top right, a cog icon) and select the F12 developer tools option.
2. The Developer tools are shown at the lesser of the electric current browser window. IE will show the certificate tree by default.
   • Click on the Network tab to view network requests
3. IE requires that network traffic exist specifically tracked, which we desire here.
   • Click the Start capturing button to capture network requests
   • Refresh the page to let IE to capture all requests
4. The network panel will show all of the requests made by IE to load the page.
   • Double click the Ajax request made by Editor - it will likely be at or near the bottom of the request list
5. Details about the Ajax request are shown.
   • Click the Reponse body tab in the Ajax view to see the verbal information that was returned from the server. This is what we are interested in!

Please annotation that these instructions were written with IE 10 as the version used. Newer versions might accept slightly different steps.

Opera

ane. Open debugger

2. Element inspector

iii. Show Network tab

four. Ajax response

1. To access the developer tools in Opera:
   • Mac: Right click or ctrl click the document and select the Inspect chemical element option.
   • Windows: Right click the document and select the Audit element option.
2. The Developer tools are shown at the bottom of the electric current browser window. Opera volition evidence data about the element that was clicked on.
   • Click on the Network tab to view network requests
   • Refresh the page to permit Opera to capture all requests
3. The network panel will prove all of the requests fabricated past Opera to load the page.
   • Click the XHR choice at the bottom of the window to reduce the requests to just the Ajax (XHR) requests.
   • Double click the Ajax request made by Editor
4. Details virtually the Ajax request are shown.
   • Click the Reponse tab in the Ajax view to meet the verbal data that was returned from the server. This is what nosotros are interested in!

Please note that these instructions were written with Opera 18 Mac as the version used. Newer versions, or those on different platforms might accept slightly different steps.

Fault handler

It tin can too be useful to use the submitError event that Editor emits when an mistake occurs. The effect has a number of parameters passed into it which can be useful for diagnosis:

``js editor.on( 'submitError', function ( e, xhr, err, thrown, data ) { this.error( xhr.responseText ); } ); ```

Resolution

Once you take followed the instructions above to find out what the data from the server actually is, it will provide the information required to resolve the underlying upshot. The most common issues are:

• PHP 5.two or earlier is being used (the Editor PHP libraries crave PHP v.3 or newer)
• A syntax error has been introduced into the lawmaking somewhere
• A bug exists in Editor causing PHP to dump an error message.

In whatever back up requests, please ensure that you include the data returned from the server so nosotros can help to resolve the error.

penaclaid1966.blogspot.com

Source: https://datatables.net/manual/tech-notes/12

Share this post