Breaks TreeDropDownField

[quamsta]

We're having an issue where we'd like our blog posts to be hidden from the CMS tree, but still selectable in the TreeDropDownField (we feature blog posts on our homepages and in other areas using an easy dropdown picker). This used to be possible in SilverStripe 3.x, but not sure what's changed, or if it's related to Lumberjack specifically.

[robbieaverill]

Interesting. I wonder if TreeDropdownField is also ignoring the hide_from_sitetree setting for pages. If that's the case, we might need to transfer this issue into silverstripe/framework

[OldStarchy]

Any updates on this?

[michalkleiner]

Ping

[OldStarchy]

@michalkleiner don't forget to thumbs up the original comment

[christopherdarling]

Having the same issue on a clients blog. Did anyone end up raising an issue on framework, searched but couldn't find anything

[wilr]

The issue with children not appearing in latest release is due not to hide_from_hierarchy nor hide_from_cms_tree options but because it's > the TreeDropdownField::node_threshold_total config value (defaults to 30)

SilverStripe\Forms\TreeDropdownField:
  node_threshold_total: 200

Note that this does have a significant performance hit when I tested so I think not showing all of them by default is wise.

Posts show up fine when using the search function so perhaps use this. Alternatively, TreeDropdown should fallback to showing the top node_threshold_total recently edited children to select rather than 0.