• I Think this is an interesting effort, but it might be offered as a plugin, it does not make sense forcing everyone to use it. Specially if it’s going to break custom metaboxes and custom fields.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Tammie Lister

    (@karmatosed)

    Thanks for taking time to leave a review @abrujulaverde. Just to clarify because of the classic editor plugin this isn’t something everyone is being forced to use. If you install that plugin even now, when 5.0 happens you won’t have to use the new experience.

    I would also like to note that in most cases custom metaboxes and custom fields are supported in the new editing experience. Have you found this to not be the case? I ask because knowing all the edges to the experience is important, so you may have valueable insights there.

    This is so incredibly backwards. GUTENBERG should be a plugin, not requiring a plugin to REVERT to a far better system.

    What is this? Is this pride? A power trip? The community is going haywire over this and you just keep on insisting that this is absolutely how it’s going to be. You aren’t listening to the community. Who in the world gave you, Tammie, the power to decide this for the entire community?

    Who are the individuals responsible for doing this against the wishes of the community? I know Matias Ventura, Joen Asmussen, and you, Tammie Lister are listed as the developers. I want the names and contact information of every single person who is taking it upon themselves to implement this in the face of HUGE resistance from the entire community.

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

The topic ‘Better as an optional plugin’ is closed to new replies.