<p>No. Matrix blocks do not work in that manner. However you define it in the field is how it'll show when you edit it. If it's really important not to show that block type you can write a plugin that checks for an entry type, and hide certain block types based on that result. Granted that's a lot of work for very little gain. You would be better off ignoring the unwanted block types or building a new matrix field.</p>

CC BY-SA 3.0
2014-06-18T22:11:49.897Z
... or make this a feature request in the g+ feedback section :)
carlcs
CC BY-SA 3.0
2014-06-18T22:14:14.567Z
I don't know. It seems too much like an edge case to me. It would take a lot of users needing the feature make the work worth it.
Bryan Redeagle
CC BY-SA 3.0
2014-06-18T22:33:50.597Z
I don't think that it always needs "a lot of users" needing a feature to make it worth being implemented. P+T is always very open to feedback and in this case they might come up with a solution, not only addressing that particular "problem" in field management.
carlcs
CC BY-SA 3.0
2014-06-18T23:31:03.367Z
A check box selector in the block settings would be ideal.  If my page types share the same matrix, they can also share the same partials, otherwise i have to code everything twice because the matrix handles are different; unless there's something I'm missing.
Steve Adams
CC BY-SA 3.0
2014-06-18T23:46:34.473Z
@pixelJitsu The setting would need to be somewhere else. Fields, as I understand them, are meant to be reusable pieces. Having such a setting there would make things overly convoluted for users that don't need it. Instead it would work better in the field layout of each entry type.
Bryan Redeagle
CC BY-SA 3.0
2014-06-19T00:26:56.520Z
Perhaps. I don't think it would be that obtrusive to have a single check box that would expand to show the related entry types when selected. Just like the current user permission tree works now. This would only appear in the matrix block type settings.
Steve Adams
CC BY-SA 3.0
2014-06-18T22:07:56.803Z
2014-06-18T22:07:56.803Z
Bryan Redeagle
<p>I have 2 primary entry types, one for a full width page, and one for a sidebar page. The sidebar page shares about 90% of the same block types as the full width page.  The other 10% do not apply to the sidebar page at all.</p>

<p>Instead of going to the trouble of duplicating (and maintaining) an additional Matrix set for the sidebar page, sans the non-applicable block types, I have decided to use the same Matrix for both pages.</p>

<p>I am looking for a way to disable / hide the unused block types on the sidebar page entry type. Just as with the normal fields which can be assigned or not to the entry types, shouldn't the matrix block types also work in the same manner?</p>

<p>Any ideas?</p>

<matrix><field><block-types><conditional>
Is there a way to hide Matrix blocks based on the Selected Entry Type?
# Is there a way to hide Matrix blocks based on the Selected Entry Type?

(Asked by: username_0 on 2014-06-18)

I have 2 primary entry types, one for a full width page, and one for a sidebar page. The sidebar page shares about 90% of the same block types as the full width page. The other 10% do not apply to the sidebar page at all.

Instead of going to the trouble of duplicating (and maintaining) an additional Matrix set for the sidebar page, sans the non-applicable block types, I have decided to use the same Matrix for both pages.

I am looking for a way to disable / hide the unused block types on the sidebar page entry type. Just as with the normal fields which can be assigned or not to the entry types, shouldn't the matrix block types also work in the same manner?

Any ideas?

**Tags:** matrix, field, block-types, conditional


---

## 1 answers

### Answer by username_1 on 2014-06-18. Score: 2

No. Matrix blocks do not work in that manner. However you define it in the field is how it'll show when you edit it. If it's really important not to show that block type you can write a plugin that checks for an entry type, and hide certain block types based on that result. Granted that's a lot of work for very little gain. You would be better off ignoring the unwanted block types or building a new matrix field.

> **Comments:**
> **username_2**: ... or make this a feature request in the g+ feedback section :)  
> **username_1**: I don't know. It seems too much like an edge case to me. It would take a lot of users needing the feature make the work worth it.  
> **username_2**: I don't think that it always needs "a lot of users" needing a feature to make it worth being implemented. P+T is always very open to feedback and in this case they might come up with a solution, not only addressing that particular "problem" in field management.  
> **username_0**: A check box selector in the block settings would be ideal.  If my page types share the same matrix, they can also share the same partials, otherwise i have to code everything twice because the matrix handles are different; unless there's something I'm missing.  
> **username_1**: @pixelJitsu The setting would need to be somewhere else. Fields, as I understand them, are meant to be reusable pieces. Having such a setting there would make things overly convoluted for users that don't need it. Instead it would work better in the field layout of each entry type.  
> **username_0**: Perhaps. I don't think it would be that obtrusive to have a single check box that would expand to show the related entry types when selected. Just like the current user permission tree works now. This would only appear in the matrix block type settings.  

---

