Classic block hidden from the inserter in WordPress 7.1

Hidden_Panda

Since the core team has now merged a change to hide the Classic block from the inserter in 7.1 https://make.wordpress.org/core/2026/06/23/hiding-the-classic-block-from-the-inserter-in-wordpress-7-1/, while not affecting current instances of the classic block. My concern is more when our users continue to use the block to past in Word texts. i guess the answer would be that its the correct move, but is this truly the right move?

ivanvallejo

The right move at this time, as long as existing posts using classic block will still be working.

The post also names a filter plus a companion plugin. I think that restore this option in the inserter for those sites that want or need it.

vijaY.jOSePh

I use a new classic block in a weekly post to display an old fashioned newsletter on the site.

Currently I just insert a new classic block weekly.

If we hide this it becomes a request for help, instead of a quick task.

MellowThistle0520

There's the companion plug-in mentioned in the post as well that brings it back in the inserter with one install (and it doesn't need any code 😉. I only hope that this new feature won't break someones carefully crafted setup.

That being said.

I do agree with you: hiding this should've been left for a later date.

evan

One question though - does that filter work on a per-user or per-site basis?

Is this irrelevant to those running the Classic Editor plugin?

ivanvallejo

It doesn't affect the sites using the Classic Editor plugin because that plugin doesn't use the block inserter.

And the filter is just a PHP filter. Unless you are checking user identity, this change will affect all of your posts, pages, products, etc.

jared.lee

A dependency I have is when pasting Word documents with tables from my client.

Only works with Classic block!

DYLAN

I have always used it, pasting Word documents directly into the block editor as we have done for years.

It even creates Table blocks for existing tables in those documents.

Hidden_Panda

Just did that in a new post at 7.0, the cells remained and the merged header rows got flattened

Turkan.Turgut

What are you people using to send off the client's content instead of Word?

Myself I use Google Docs - I use it all the way through on a daily basis.

But in this case the client actually asks for Word doc, I just convert it before sending off - just have to do this so when they come up to get their content, it can be 'as is' what we had.

christopher

Classic in my case would really be the pasted Word document with all its inline styles...

MellowThistle0520

Oh, getting back to the original question here, hiding that block indicates a direction and it would make sense to do some kind of training right now so people are comfortable with blocks (in case it's removed totally and completely someday soon™).

It would make sense to plan the client training on blocks right now not when the block vanishes completely forever, right?

I suppose some people don't want to learn just yet, but with WordPress going towards blocks. It would be best to do that before it vanishes someday.

Mattia

It has been reverted so the Classic block is available in the inserter in WordPress 7.1.

If there's anything more to look at in relation to the Classic block, we can discuss it more.

Regarding training for working with blocks - it still makes sense to get comfortable working with them.

Hope this helps, @Hidden_Panda

vijaY.jOSePh

Phew, glad, saved the companion plugin to bookmark for whenever it returns 🙂

ivanvallejo

Mattia wrote
If there's anything more to look at in relation to the Classic block, we can discuss it more.

That does sound fair, since it was the WP core itself that retracted. For a point release, the approach of filter plugin was too abrupt.

Hidden_Panda

That is also fair - nothing changed in 7.1 and in any case the newsletters are being converted into blocks as we see the trend.