When disabling a Matrix field and saving the entry, the Matrix field gets deleted. There is no way to enable it again – except reverting to a recent revision.

Unfortunately we were not able to reproduce this. Can you send in a support ticket to [email protected] with a database backup so we can try with your DB?
I noticed the same problem on a website with Craft RC6. Disabled blocks of matrix fields are deleted when saving the page. It is interesting that it does not appear on another website (also Craft 3 RC6). The difference is that one website is multilingual (where the problem occurs) and the other is not.
Ah thanks @abinggeli! Able to reproduce it now.
And fixed. Thanks guys.
Similar problem in Craft CMS 2.6.3019
Works fine in the default en_US environment/locale. But when using other locale the block disappears instantly when disabled (not when saving).
@herrajon Sounds unrelated. Can you please post a new issue with specific steps to reproduce?
Will do
@brandonkelly No need to worry
I am using a plugin, Matrix Colors to color my matrix blocks. That is all good. But.
A little bogus there. I had some old definitions inside the plugin; The colors for the matrix blocks are define by the blocktype there. Some blocktypes no longer existing where defined.
I removed those old definitions and voila. My lost and I thought deleted blocks reappeared.
Things back to normal. Now you only need to worry about 7.714 things.
Hah! Glad you got it sorted :) You may want to submit an issue the bug at the Matrix Colors repo though.
Hi all, we have the same issue now - running Craft Pro 3.1.33
Same issue also on Craft 3.2.7
@DavidKabelitz @juliansthl What plugins do you guys have installed?
@brandonkelly
We're using Super Table and the matrix field is a "subfield" of the Super Table…
Plugins & versions:
Hi @brandonkelly those are on our list:
In our case the matrix field is also a sub of a Super Table
Craft Pro 3.1.33
Thanks guys, that ended up being a Super Table issue (verbb/super-table#288). Just submitted a PR that fixes it.
Most helpful comment
Thanks guys, that ended up being a Super Table issue (verbb/super-table#288). Just submitted a PR that fixes it.