Invision Community 4: SEO, prepare for v5 and dormant account notifications Matt November 11, 2024Nov 11
March 1, 201510 yr Management I assume you mean the front end features?We were wary to put this in 4.0 because of countless stories of rogue moderators mass-pruning and entire forum before an admin realized what happened.But you are right that the missing low-level options to prune/mass-move is sometimes difficult to work around.
March 1, 201510 yr Author I understand that worry. I limited the ability to just my main admins for that exact reason. It is however something I use on a regular schedule (not often, but at regular intervals throughout a year). I have to move an entire category's worth of topics into a sub-topic by year.
March 1, 201510 yr Management Yes it's something we will work on. Just want to try to find a way to make it a bit safer.
March 1, 201510 yr I too have seen 'accidents' with this feature.I thought about extra protection for it, but thinking again instead of how it was in 3x and 2x ie a global mod option, how about making it only available to those with ACP access and in a global mod group ?Another idea would be to request the users password I guess, although I am starting to think this should *only* be available in the ACP itself rather than appear on the front end...
March 2, 201510 yr Author I would find it easier to work with on the front end, but I agree with most of your other extra protection proposals. Having it only available for people who have ACP access would be a good security check.
March 4, 201510 yr I see my thoughts posted above on making this a "bit safer" were taken into consideration for future implementation, as seen on the Feature Plan page. Moderators will have the ability to perform rule-based actions on the front end to mass move/prune items (Forums app only to start). These actions will be with administrator permission of course (since this is easily abused) and will be based on rules like date, last activity, and more. For security and to prevent accidents, moderators will have to re-authenticate using their password for mass actions.
March 4, 201510 yr I assume you mean the front end features?We were wary to put this in 4.0 because of countless stories of rogue moderators mass-pruning and entire forum before an admin realized what happened.But you are right that the missing low-level options to prune/mass-move is sometimes difficult to work around.​This has always been a worry of mine - whether you get a rouge moderator or someone gets a moderator's password.I just have those functions turned off for moderators to begin with - only the admin can perform those tasks.
March 8, 201510 yr Author ​This has always been a worry of mine - whether you get a rouge moderator or someone gets a moderator's password.I just have those functions turned off for moderators to begin with - only the admin can perform those tasks.​That's how I run things
March 8, 201510 yr What the problem with the Admin choose which groups can Mass Move/Prune?If a Admin don't trust their Mods to do that, he should only give permissions to the Admin Group or even to only himself.I also move old topics to a Section i call Archive.
March 9, 201510 yr What the problem with the Admin choose which groups can Mass Move/Prune?If a Admin don't trust their Mods to do that, he should only give permissions to the Admin Group or even to only himself.I also move old topics to a Section i call Archive.​I agree with letting the admin/site owner determine who can perform this function. It's more than trusting mods, if someone gets their password, then they can cause havoc. I do appreciate IPS leaving this off by default because this is and will be an admin function for me.
March 9, 201510 yr Author Another option might be to only allow Prune from the ACP and Mass Move from both ACP and Front End.
March 9, 201510 yr I think the best solution is by default the prune/mass move comes turned off. If the Admin wants, he can turn it on for the groups he chooses. If he gives permissions to the mods and a mod prune his whole forum, to bad for him... It was him that gave the permissions.
August 19, 20159 yr Another often used feature removed from IPB4. Not happy with this "upgrade" thusfar
August 19, 20159 yr Another often used feature removed from IPB4. Not happy with this "upgrade" thusfarI can see why it was removed though. I think it is safer in the ACP or at least (as I made the suggestion) a re-authentication option before pruning as its as you know quite destructive, and 'accidents' are known to happen.
August 19, 20159 yr So the only option right now is the manually delete threads? I thought this was supposed to be an upgrade.
April 3, 20178 yr Management Moving/deleting forum content by filters (starter, last reply date, reply count, lock status, pinned, featured) will be in 4.2.
December 21, 20204 yr Moving/deleting forum content by filters (starter, last reply date, reply count, lock status, pinned, featured) will be in 4.2. Where do I find this?
December 22, 20204 yr Go to the forum management area in the AdminCP, click the dropdown arrow next to the forum, and choose to Move/Delete Content.