Updating to the latest version across production to assist in troubleshooting efforts of license key errors as of February 25th, 2026
As of 11.20am EST on February 25th, the Brightspace Editor was rolled back to version 7.7.0 across production environments.
We identified 2 issues across users who reported an error using the Brightspace Editor.
- The first affected macOS users who are using legacy or unsupported (warning) versions of Safari (14, 15 or 16), and showed up with a console error `SyntaxError: Left hand side of operator '=' must be a reference`.
- The second affected macOS or Windows users, with Chrome, using 3rd party apps or programs such as 'Survey Junkie' and showed up with a console error `plugin.min.js:27 Uncaught TypeError: _0x40551e is not a function`
Details of both of these issues can be found on our Known Issues List:
At this time the information gathered with the help of affected users is being investigated by D2L and TinyMCE. We thank everyone for their assistance in helping us track down these issues and once again apologize for any disruption that a user may have experienced while the update was applied.
Updating to the latest version across production to assist in troubleshooting efforts of license key errors as of February 12th, 2026
In our December 20.25.12 release, we updated our Brightspace Editor from version 7.7.0 to version 8.0.2, to take advantage of TinyMCE defect fixes. Unfortunately, when the update was applied to environments, we had reports from a limited number of clients with a small number of users who found that the update had unexpected impact, leaving them unable to use the editor as it reported an error “The editor is disabled because the TinyMCE license key could not be validated”.
To mitigate impact, the update to version 8.0.2 was rolled back in early January 2026, to ensure that all users could continue to use the Brightspace Editor successfully, while we investigated the issue to find a resolution. This was reported on our Fixed Issues List here: Brightspace Editor - Sporadic reports that the editor license key could not be validated - Brightspace.
Since this time, we have been investigating the reports, testing different operating systems, browsers and browser versions, but this issue has never been reproduced by D2L. We have reached out to our 3rd party vendor, TinyMCE, to assist in our investigation, however they too have been unable to reproduce. We have worked with previously affected clients to assist in our troubleshooting efforts, and we have re-enabled the editor updated across testing environments – however there have been no additional reports of errors occurring. We have ensured that we have an immediate response and next steps ready, should there be any reports, so that we can act swiftly to troubleshoot affected users, to determine if, for example, there might be a browser plugin or VPN preventing the use of the editor.
Unfortunately, D2L has exhausted all avenues of testing and investigation to reproduce the issue to locate a permanent resolution.
To move forward, we will be re-enabling the Brightspace Editor update across production environments as of Thursday 19th February 10am EST. This is an investigation to gain deeper understanding of the issue and determine why the error occurs.
As soon as we have gathered information, the update will be rolled back to revert the Brightspace Editor to the previous known good version.
This is required to ensure that we can gather information for further troubleshooting of the error, should it occur again, to determine a permanent resolution. Updates to the Brightspace Editor version are critical to ensure that we continue to receive defect and security fixes from TinyMCE and take on any future updates and improvements, while maintaining a current valid license key.
We ask that should issues arise, you immediately contact our Support teams so that we can take steps to gather information from any affected users and troubleshoot the error while it is occurring. We sincerely apologize in advance for any disruption to your users should the error return, however we must move forward with Brightspace Editor updates to ensure that we can continue to utilize the Brightspace Editor successfully.