GlideEditorJS is not defined — syntax editor does not load or displays incorrectlyIssue When the syntax editor is not working as expected, the browser console may log an error similar to GlideEditorJS is not defined. This error typically occurs because the file GlideEditor5Includes.js — which applies styling to the script editor — is inaccessible due to an internal network firewall or VPN restriction. Additional symptoms can include the following: - Code appears in black and white.- The Format code button is not working.- Script block fields display in all grey text.- Toggling the editor has no effect. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } All releasesCause This issue is likely due to an internal network firewall blocking access to the file GlideEditor5Includes.js. This file applies the style for the script editor. When this file is inaccessible, the syntax editor fails to load or render correctly. Resolution Follow the steps below to confirm whether GlideEditor5Includes.js is being blocked by the network. 1. Open the browser developer tools and go to the **Network** tab.2. With the **Network** tab open, log in to the instance and navigate to a script include or a business rule record.3. In the **Network** tab, search for the file GlideEditor5Includes. Check whether the file downloaded successfully. If it failed, note the HTTP reason code or status shown in the network request row. A 200 status indicates success. Any 4xx or 5xx status, or no response at all, indicates a network-level block.4. If the file failed to download without a reason code, follow the steps below to test access from the command line. 1. Open Terminal (macOS) or Command Prompt (Windows). 2. Run the following command: ```curl -s https://<instance-name>.service-now.com/scripts/GlideEditor5Includes.jsx?v=04-29-2021_2308``` *Note: Check the console error for the correct date to use at the end of the path.* 3. If the command returns no content or an error, this confirms the file is being blocked. Share the output and any error codes with the internal network team to identify what is blocking access (a firewall, a VPN, or similar). If the syntax editor is not working after an upgrade to the Utah release, a known workaround is to add the system property `glide.ui.syntax_editor.polaris` and set its value to `false`, then clear the instance cache by navigating to cache.do, or set the system property `glide.ui.escape_all_script` to `true`. The permanent fix was targeted for Utah Patch 4. Related Links - [Syntax editor plugin overview and configuration](https://docs.servicenow.com/bundle/utah-application-development/page/script/general-scripting/concept/c_SyntaxEditorPlugin.html)- [Syntax editor keyboard shortcuts and supported actions](https://docs.servicenow.com/script/general_scripting/reference/r_SyntxEdtrKybrdSrtctsActn.html)