How long will this work?

  • Resolved rvturnage

    (@rvturnage)


    6 years, 4 months ago

    Not technically “support”, I know, but I’m hoping you can help me understand. How long will this approach of disabling Gutenberg work? For example, I have a dozen sites or so that use WP Bakery Page Builder. Gutenberg must be disabled for those to work, so I will use this plugin to make that happen at least in the interim. But how long will “disable Gutenberg” be an option if it’s in core? Will they kill that option completely in WP 5.1? 5.2? Or is this something that they can’t “turn of”? This gets even more pressing because I’m in the early stages of a new site for a client I was planning on using a Page Builder for. If WP can make this plugin non functional in the future by removing the ability to “disable Gutenberg”, I have to completely rethink what we had planned to do.

    • This topic was modified 6 years, 4 months ago by rvturnage.
Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author Jeff Starr

    (@specialk)

    It all depends on how things change with WordPress. If it helps, as with all of my plugins, the plan is for the long term. As long as WordPress provides a mechanism by which the Gutenberg editor can be replaced with the Classic Editor, there is nothing to worry about imho. I hope this helps, let me know if I can provide any further infos.

    Thread Starter rvturnage

    (@rvturnage)

    Thanks for the reply. I guess I’m just worried they won’t continue to provide that mechanism indefinitely. Trying to think long-term for a new site we’re about to start developing. The timing is terrible for me.

    In the meantime, I’ve downloaded WP5 beta and your plugin works like a charm. It’s certainly going to be a huge life saver on most of my sites!

    Plugin Author Jeff Starr

    (@specialk)

    Best of luck to you, rvturnage!

    They’re now saying Classic Editor has three years:
    https://wptavern.com/classic-editor-plugin-may-be-included-with-5-0-updates-support-window-set-to-end-in-2021

    D

    (@clocksaysnow)

    First, thanks for making this plugin. I’m definitely not a fan of Gutenberg. Two quick questions:

    1.) As plugins adapt to Gutenberg, will those plugins fail to work properly if I’m still using the classic editor?

    2. Will the Disable Gutenberg plugin allow me to continue using the classic editor beyond the three-year point mentioned by nyssamccanmore in the above post? Or will future WP updates cause everyone eventually to lose access to the classic editor—even those people using the Disable Gutenberg plugin?

    Thanks!

    Plugin Author Jeff Starr

    (@specialk)

    Glad to help:

    1) Should be fine as good plugins that “adapt to Gutenberg” will do nothing if Gutenberg is disabled.

    2) I have no such time/date limit on my plugin development and support. I will continue developing and supporting Disable Gutenberg for as long as possible, Lord willing well beyond 2021. Of course, it all depends on how extensive JS spreads in core. At some point, the core of WP will be consumed/replaced by JavaScript, which will change just about everything.

    I thought Javascript has been accused of slowing down sites and often breaking, so it’s been severely restricted by AMP. It causes headaches when optimizing my sites, and I’ve seen plugins stop working as well when they switch to JS. I’d rather see less of it, but they’re putting in more?

    I’m really not feeling too good about these WordPress changes….. ??

    The developers seriously need to think about all these millions of legacy WP installations – and what it will mean if they force something like Gutenberg upon millions of sites and users. Even 3 years isn’t anywhere near enough time to force change on everyone. NO change to existing, legacy sites and installations is what is needed. WP installs should be permitted to stay exactly how they are – forever. Backwards compatibility is absolutely essential.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘How long will this work?’ is closed to new replies.