You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ah so the expected behaviour would be that it treats small and large collections of child pages equally, in that it hides or shows them depending on its config?
Presumably if the config says "show in sitetree" and "hide from cms tree" is false, we should still show the "too many pages" message?
Yeah actually it might be a more difficult to solve than I first thought - if you have two “child” classes and one is hidden from the tree and one isn’t, you should still see the “Too many pages” message if the visible children count is too high.
Actually after spotting #86, I need to double check which config things I’ve setedit: they don’t seem to make any difference
Is there any update on this? This seems to be a core issue not showing a small amount of allowed child pages when there are a large amount of hidden pages.
I was able to hide excessive blog posts but show the other pages by using hide_from_cms_tree
The post is visible in lumberjack but not the sitetree - until you edit it.
I’ve worked around this in my project by overriding
CMSMain_SubTree.ss
and checking whether the node has the lumberjack extension (line 4):A proper fix to the module could probably use a similar approach, though it’d need to check
show_in_sitetree
/hide_from_cms_tree
The text was updated successfully, but these errors were encountered: