An Error Has Occurred

12. Editor: A system error has occurred.

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

• ane.3.3+: A system error has occurred (more information)
• 1.three.2-: An error has occurred - Delight contact the organization administrator

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

Diagnosis

If the server didn't reply to Editor's Ajax asking with valid JSON data, we need to know what it did reply with, and then nosotros can take corrective activeness. Typically, the response will consist of an error message from the program on the server which is being used to create the JSON, which volition be the starting betoken for resolving the issue fully.

Server data

Modernistic browsers all come with built in developer tools, which can be used to discover 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

2. Enable developer menu

iii. Show page resources

4. Ajax response

1. By default Safari hides its congenital-in developer tools. If y'all don't have a Develop carte shown in Safari information technology needs to be enabled. If y'all do, jump to step 3.
   • Open the Safari menu and select Preferences...
2. Enable the programmer carte du jour in the Avant-garde tab
   • Click the Advanced tab in the Preferences window
   • Bank check the box for Evidence Develop menu in menu bar option
   • Close the preferences - the Develop menu volition now be shown
3. View the resources the page has loaded
   • Select the Show Folio Resource selection from the Develop carte du jour.
   • The programmer console will show at the bottom of the page
   • Reload the folio and so Safari can capture all network requests
4. Details well-nigh the Ajax request are shown.
   • Safari will show a list of all resources (images, scripts etc) which have been loaded for the page. Locate the Ajax request that has been made to the server and click it. Safari will testify detailed information about the asking.
   • Note that on pages with a large number of resources, Safari volition grouping the resource by type into folders. If this happens on your site, look for the "XHRs" folder for the Ajax requests.

Please annotation that these instructions were written with Safari 7 every bit the version used. Newer versions might take slightly unlike steps.

Chrome

1. Open debugger

2. Panel displayed

3. Show Network tab

iv. Ajax response

1. To access the developer tools in Chrome:
   • Mac: Access the View > Programmer > Developer Tools carte selection.
   • Windows: Click the Chrome carte du jour (to the correct of the address bar) and select Tools > Programmer Tools.
2. The Developer tools are shown at the bottom of the current browser window. Chrome will show the Javascript console past default.
   • Click on the Network tab to view network requests
   • Refresh the page to allow Chrome to capture all requests
3. The network console 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 request made by Editor
4. Details nearly the Ajax asking are shown.
   • Click the Response tab in the Ajax view to come across the exact data that was returned from the server. This is what we are interested in!

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

Firefox

ane. Open debugger

2. Network requests

three. Ajax requests

iv. Ajax response

1. To access the developer tools in Firefox:
   • Mac: Access the Tools > Web Developer > Network menu option.
   • Windows: Click the Firefox menu (top left of the window) and select Web Programmer Network option.
2. The Programmer tools are shown at the bottom of the current browser window.
   • Refresh the page to allow Firefox to capture all requests
3. The network panel will show all of the requests made by Firefox to load the folio.
   • 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 fabricated by Editor
4. Details almost 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 have slightly dissimilar steps.

IE

1. 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 menu (pinnacle right, a cog icon) and select the F12 programmer tools choice.
2. The Developer tools are shown at the lesser of the electric current browser window. IE will show the document tree past default.
   • Click on the Network tab to view network requests
3. IE requires that network traffic be specifically tracked, which we want here.
   • Click the Offset capturing button to capture network requests
   • Refresh the page to permit IE to capture all requests
4. The network panel will evidence all of the requests made by IE to load the page.
   • Double click the Ajax asking fabricated past Editor - information technology will likely exist at or near the bottom of the asking listing
5. Details about the Ajax request are shown.
   • Click the Reponse body tab in the Ajax view to come across the exact data that was returned from the server. This is what nosotros are interested in!

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

Opera

i. Open debugger

2. Element inspector

3. Testify Network tab

4. Ajax response

1. To access the developer tools in Opera:
   • Mac: Right click or ctrl click the document and select the Audit element pick.
   • Windows: Right click the document and select the Inspect element option.
2. The Developer tools are shown at the bottom of the current browser window. Opera volition show data about the element that was clicked on.
   • Click on the Network tab to view network requests
   • Refresh the page to allow Opera to capture all requests
3. The network panel volition show all of the requests fabricated by Opera 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 about the Ajax asking are shown.
   • Click the Reponse tab in the Ajax view to run into the exact data that was returned from the server. This is what we 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 take slightly unlike steps.

Error handler

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

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

Resolution

In one case yous have followed the instructions above to notice out what the information from the server actually is, it will provide the information required to resolve the underlying outcome. The about mutual issues are:

• PHP 5.ii or earlier is being used (the Editor PHP libraries require PHP 5.3 or newer)
• A syntax error has been introduced into the code somewhere
• A problems exists in Editor causing PHP to dump an error message.

In whatever support requests, please ensure that you include the data returned from the server and then we tin can help to resolve the error.

nealguine1938.blogspot.com

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

Share this post