最新消息:Welcome to the puzzle paradise for programmers! Here, a well-designed puzzle awaits you. From code logic puzzles to algorithmic challenges, each level is closely centered on the programmer's expertise and skills. Whether you're a novice programmer or an experienced tech guru, you'll find your own challenges on this site. In the process of solving puzzles, you can not only exercise your thinking skills, but also deepen your understanding and application of programming knowledge. Come to start this puzzle journey full of wisdom and challenges, with many programmers to compete with each other and show your programming wisdom! Translated with DeepL.com (free version)

tinymce - Error in backend: Failed to load plugin: tabfocus from url

matteradmin6PV0评论

I'm getting an error that looks really wierd (notice the red error, running all the way down from top to bottom, over the left sidebar):

The error is:

Failed to load plugin: wordPress from url /wp-includes/js/tinymce/plugins/wordpress/plugin.min.js

But I got an error earlier today, appeared in the same wierd fashion, but the error was then:

Error in backend: Failed to load plugin: tabfocus from url url /wp-includes/js/tinymce/plugins/wordpress/plugin.min.js

The error comes and goes, - and I'm unable to figure out, why it appears. When it appeared earlier today, then I deactivated all plugins; and then the error disappeared. Then I reactivated all my plugins, - and the error was still gone!?

I just tried doing the same thing just now, but this time it didn't solve it.

My original theory is, that it's either because of:

  • Yoast
  • Advanced Custom Fields
  • Or because I'm running on a local environment, using Flywheel

But I don't think so anymore, since the error comes and goes, - and that it persists, even after reactivating the plugins again.

As can be seen on above-shown image, then I've deactivated the editor. I'm doing that with these lines:

/**
 * Disable regular editor
 */
function custom_init_remove_support(){
    remove_post_type_support( 'page', 'editor');
    remove_post_type_support( 'post', 'editor');
}
add_action('init', 'custom_init_remove_support', 100 );

Could that maybe somehow be related to the error?

Post a comment

comment list (0)

  1. No comments so far