content.ini [RemoveSettings] MaxNodesRemoveSubtree (default: 100) is a limit on the amount of subtree items you can delete over HTTP. If you try to remove more than this, you get an warning message:
"The lines marked with red contain more than the maximum possible nodes for subtree removal and will not be deleted. You can remove this subtree using the ezsubtreeremove.php script."

This mechanism is implemented in template code, and only in the admin and admin2 designs. In frontends like ezwebin and ezflow the warning is not shown, but the mechanism still works. The consequence for the end user is that when he tries to delete large subtrees, nothing happens. The page reloads, and the subtree is still there. No warning.

The bug applies to any design that allows you to delete content. The fix would be to add the warning message to these templates:
design/standard/templates/node/removeobject.tpl
extension/ezwebin/design/ezwebin/templates/node/removeobject.tpl

The code for the warning message can be found in:
design/admin/templates/node/removeobject.tpl
design/admin2/templates/node/removeobject.tpl
(look for "exceeded_limit_of_subitems")

Steps to reproduce

• Set content.ini [RemoveSettings] MaxNodesRemoveSubtree to 1
• Create a Folder with 2 sub items
• Go to a frontend design, such as ezwebin or ezflow
• Try to remove the folder you created: nothing happens. (BUG)