Classic Editor not working with WidsmLabs Instructor (original) (raw)

Viewing 7 replies - 1 through 7 (of 7 total)

• Hi @healthmanifested – thanks for the suggestion. Whilst the Classic Editor continues to be generally supported it’s unlikely to undergo any development to add extra support – so the requirement would be on the plugins to opt in and support the Classic Editor itself.
  Thats too bad. I wish I could fix it myself. I really like the plugin.
  Hi, @healthmanifested 👋🏻 The Classic Editor plugin re-enables a built-in core feature of WordPress, so as @jordesign noted, it would be up to those plugins to ensure compatibility (in this case, backward compatibility with WordPress’s classic editor). From a technical standpoint, the plugin doesn’t add this functionality, but turns it on again for those who prefer the old editing experience.
  As this plugin should only affect the post/page editor, it may be possible for the other plugins to disable the classic editor when modifying post types dedicated to those plugins (conditionally reversing Classic Editor from setting the old editor as default).
  Possible workaround?
  While waiting for an update from the other plugins’ authors, if the errors you’ve experienced are occurring only when you access their “post” edit screens (but not on, say, the WP admin dashboard), then you could try swapping the plugin’s default settings for “default editor” and allowing editor switching:
  
  This would prevent Classic Editor from forcing the old editor to load when modifying those plugins’ post types, and then on normal posts/pages you could “switch” to the classic editor on a per-post basis.
  Thank you. I dont see those options. Are they only available when classic editor is active? The classic editor is messing up LearnDash and giving me 500 errors so. I can’t keep it activated.
  Yes, those options are only available when the plugin is active. If saving with those settings doesn’t subsequently resolve the issues with the other plugins, then unfortunately my idea of the workaround doesn’t pan out ☹️. It will be up to those plugin authors to resolve the conflict when the old editor is enabled. It was worth a try!
  Thanks. I can’t keep the plugin acive it gives me 500 errors.
  Gotcha. Hopefully the other plugins’ authors can extend backward compatibility support for the classic editor 🤞🏻 I’ll close this topic for now.

Viewing 7 replies - 1 through 7 (of 7 total)