Menu Normal unwanted_asset_types not working in 4.18.6

Squiz Matrix Support
1

For the life of me, I cannot get unwanted_asset_types to work. I set it in my design, but it never hides those asset types from the menus. I use:

<MySource_AREA id_name="normal_menu_1" design_area="menu_normal">    
    <MySource_SET name="unwanted_asset_types" value="folder, file, link" />
    <MySource_SET name="settings.class.normal" value="normal" />
    <MySource_SET name="settings.class.current" value="current" />
    <MySource_SET name="settings.class.hierarchy" value="hierarchy" />
    <MySource_SET name="show_subs" value="always" />
    <MySource_SET name="level" value="1" />
    <MySource_SET name="self_link" value="false" />
    <ul class="normal_sub">
        <MySource_ASSET>
        <li class="<MySource_PRINT var="settings.class" />">
            <MySource_PRINT var="asset_name_linked" />
        </li>
        </MySource_ASSET>
    </ul>
</MySource_AREA>
Seems plain and simple to me. Not sure I could be doing anything wrong.
 
Is this a bug in this version?
2

Not sure, should be working fine in that version. 

 

You don't have any customisations that are overwriting these parse file settings?You can try to replicate either on a brand new parse file with no customisations, or actually set the unwanted list on the customisations screen instead. 

3

not sure if 'file' includes children asset types, that may be the case.

4

This is on a site that already has the parse file created. I have cleared customizations and everything. Do we need to completely remove a customization and add it again? If that is the case, that is horrible, and this is not an option on many large sites.

5

This is on a site that already has the parse file created. I have cleared customizations and everything. Do we need to completely remove a customization and add it again? If that is the case, that is horrible, and this is not an option on many large sites.

 

No you don't have to, you can set the asset restriction on the customisation instead of the parse file. If you do customise a design area in the parse file, it will overwrite any settings you have set directly inline into the parse file. 

6

 

No you don't have to, you can set the asset restriction on the customisation instead of the parse file. If you do customise a design area in the parse file, it will overwrite any settings you have set directly inline into the parse file. 

 

Yeah, I realize that. It just has never worked for us to do that in this circumstance. :(

7

That's strange, never seen that not working. I'll try and setup a test in the latest version tomorrow to confirm that it works with your example parse file and will report back. 

8

We are on 4.18.6 and the unwanted asset types does the job for our system.

9

Tested the same parse file in the latest 5.0 and works correctly there as well.