Скачать или смотреть How to Fix JavaScript Injection in TinyMCE Editor on WordPress

Learn how to resolve the issue of unexpected JavaScript injection into the TinyMCE editor in WordPress when Gutenberg is deactivated, including potential causes and solutions.
---
This video is based on the question https://stackoverflow.com/q/70166489/ asked by the user 'Choussich0uss' ( https://stackoverflow.com/u/16806363/ ) and on the answer https://stackoverflow.com/a/72088721/ provided by the user 'Facyla' ( https://stackoverflow.com/u/13801929/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: javascript injected in tinymce editor by wordpress when gutenberg is desactivated

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Resolving JavaScript Injection in TinyMCE Editor on WordPress

In a fresh install of WordPress (5.8.2), users have reported encountering unexpected JavaScript code injected into the TinyMCE editor when the Gutenberg editor is deactivated. This issue can be frustrating, especially when it occurs without any apparent cause or installed plugins. In this guide, we will explore the root of the problem and provide an effective solution.

The Problem

When users deactivate the Gutenberg editor—whether by using a plugin or by adding code manually—some have noticed that specific JavaScript code appears in the TinyMCE editor. This can affect content inputs, custom fields (like ACF), and overall performance. Here’s the actual script that has been found injected:

[[See Video to Reveal this Text or Code Snippet]]

This issue raises a couple of questions:

Why is this code being added when Gutenberg is turned off?

How can it be resolved effectively?

Identifying the Cause

After investigating the issue, it appears that the JavaScript code, specifically related to Spector.js, is responsible for this unexpected behavior. The Spector.js extension, commonly used for debugging WebGL content, can sometimes interfere with the WordPress TinyMCE editor.

Findings

Disabling the Spector.js extension resolves the problem.

The issue mirrors similar behavior when Spector is enabled on Firefox; thus, it's likely a conflict between WordPress editor functionalities and the Spector debugging tool.

Solution: Disable the Spector.js Extension

If you're encountering this JavaScript injection in your TinyMCE editor, follow these straightforward steps to disable the Spector.js extension:

Locate the Spector.js Extension:

Open your browser (usually Firefox or Chrome).

Go to the extensions or add-ons section of your browser.

Disable the Extension:

Look for the Spector.js extension in the list of installed extensions.

Click on the toggle switch or the disable button to turn it off.

Restart Your Browser:

After disabling the extension, restart your browser to ensure the changes take effect.

Check Your WordPress Editor:

Open your WordPress dashboard and navigate to the page or post editor.

Check if the JavaScript injection persists in the TinyMCE editor.

If you have completed these steps, the issue should now be resolved. You can now use the TinyMCE editor without the injected JavaScript disrupting your workflow.

Conclusion

Experiencing unexpected JavaScript code injection in your TinyMCE editor can undoubtedly be a hassle. However, by identifying the Spector.js extension as the culprit and disabling it, you can quickly resolve this issue and restore normalcy to your WordPress editing experience.

Don’t hesitate to reach out in the comments if you have any questions or need further assistance regarding this matter.