Support » Plugin: Gutenberg » Please! No core!

Viewing 8 replies - 1 through 8 (of 8 total)
  • Moderator Jan Dembowski

    (@jdembowski)

    Brute Squad and Volunteer Moderator

    OKAY, I’ll bite. Why do you say “is going to destroy 50% of plugins”? Have you had problems with Gutenberg and some plugins and if so, which ones?

    The first plugin I took was WooCommerce. Try editing a Product.

    @jan, i get the core team is in full force trying to tell people that what they see do not exist, but your sarcasm is out of place. Until plugins and themes will start to announce compatibility there is no reason to assume that they are compatible. Even then, for the ones that will need to release new versions like WC will probably have to do, there will be people that will not be able to upgrade.

    I agree that 50% of all plugins is a far fetched number but even 1 plugin with many installs gona impact huge amount of sites. I can easily imagin sites with 50% of their plugins being impacted.

    Moderator Marius L. J.

    (@clorith)

    Hiya,

    We’re not trying to force people into “not seeing”, we’re honestly curious what plugins users are experiencing issues with.

    It’s worth noting that there’s still some time left before Gutenberg and WordPress 5.0 is released, and I know that WooCommerce are doing some very interesting things with it. We also have fallback mechanics that will be in place when the final product is rolled out to avoid breaking what we can.

    I belive that best bet would be giving a choice, aka leaving tinyMCE as is, and than applying Guttenberg next to it. If that’s possible (Im not really wordpress user myself, just buddies from my company are veeery very worried) I would add guttenberg to output as raw html code to tinyMCE, and leaving handles as is, without breaking anything. Than allow editing via tinyMCE (ex. ‘edit’ link and ‘edit (old editor)’ link, so both parties will stay happy, guttenberg fans, and old plugins)

    Another solution, better one, is setting in code of plugin flag, that its guttenberg compatible. If there is flag, use guttenberg, else, use tinyMCE.

    Mark tinyMCE as deprecated and obstole in wordpress 6.0.

    @clorith
    Feel free to leave what you think about this solution. This will leave current sites intact, and 2.nd solution can force guttenberg where possible and known to work, so both parties happy.

    • This reply was modified 4 days, 8 hours ago by  dubbathony.
    Moderator Jan Dembowski

    (@jdembowski)

    Brute Squad and Volunteer Moderator

    i get the core team is in full force trying to tell people that what they see do not exist, but your sarcasm is out of place.

    That was not even remotely sarcastic. I was asking about this unqualified review:

    That breaking change is going to destroy 50% of plugins

    I was asking about this unqualified review

    Before doing this unqualified review I took 4 plugins and 2 of them were broken. I gave an example. What else would I say?

    Why are you trying to force developers fix their plugins instead of making GTB optional? Even built-in but optional.

    Or can you explain in details why exactly you are sure you are not going to break other plugins by forcing GTB for post types?

    @anton-korotkoff

    It is totally possible, I gave solutions in my previous post how to do it. However, how they will do it is whole another story. I dont know, and I would love to know how their fallback mechanism would work.

    Unfortunately their core code isn’t really very readable for me (I code in waaay different style, Its been awhile since I read such code)

Viewing 8 replies - 1 through 8 (of 8 total)
  • You must be logged in to reply to this review.