I don't believe the admin panel will allow you to delete many objects over 100 in one go. I know i've hit limits previously, where it advised me to use ezsubtreeremove.php.
I used this recently to delete a bunch of unrequired objects:-
Does the ezsubtree remove delete the parent object as well? that is, if I use it to remove users, will it also delete the user group they're contained in?
I'm trying to avoid that as I think we'll have to rewrite a custom script we've had written for us that refers to the specific node id of the user group.
<i>
Does the ezsubtree remove delete the parent object as well? that is, if I use it to remove users, will it also delete the user group they're contained in? </i>
Good question. I haven't used it to remove user objects, but as your're probably going to use the User Group node id to delete all the user below, i would assume yes it will delete the user group as well.
Like i said i haven't tried it with user objects. Definitely worth testing it on another unimportant dev ez pubish base first, to check the behavior.
Try creating a new user group called "delete me" or something, then swapping it with the group with all the accounts you want to delete. If you want to keep some of the accounts in that group, you can move them back in the original group after you swap it. This will keep the existing group in tact while giving you a new subtree that you can remove completely.
"Swap with another node" is a function in the Advanced submenu of the Content Structure Menu popup menu.
You definitely want to use the command line script to delete a subtree with that many objects in it.
>Try creating a new user group called "delete me" or something, then swapping it with the group with all the accounts you want to delete.
Just guessing here, but I think Ciaran want to keep it to avoid recreating any role assignments. If so I would consider creating a copy of the script where you fetch the children node id's of the passed nodes and pass those id's to '$deleteIDArrayResult'.
Rough ( as in not tested) 4.x patch for the script so it doesn't remove the root of the subtree:
Thanks for your help. In the end we just created a new empty user group and started using that instead which allowed us to delete the old group including the parent node.
You must be logged in to post messages in this topic!