Best Of

And I thought to myself: "That shouldn't be too hard..."

I will upload the plugin some time later, but you can already get it from here.

@phreak That plugin replaces every name with "[Deleted User]" but keeps the content.

I would never allow a user to remove content by himself. That should be done by a board admin. Removing content is quite difficult if the user already has deleted himself. Maybe some hint on that should be added to the delete section of my plugin "If you also want to remove the content (discussions & comments), please do not delete your user by yourself but ask a moderator to help you instead" - something like that...

@jasongeek: Totally understand you from a community managers perspective. We also have frequent requests and handle these manually.

@Kaspar: There are several cases where users request that. People who sign up and don‘t find the community to fit their needs like to remove their data or at least e-mail. On the other hand we have users who are angry because of ongoings in the community or too personal involvement so they want to get their account removed. Often it‘s of emotional value for the user but also GDPR rules are set to give users the ability to get their account data removed on request (and people seem to know that).

Community managers of large forums run into those requests several times a week and there is no „routine“ in place currently how to do that.

We remove images and replace the e-mail with our own trashmail adding [email protected] to clean the users data from our database. We do not remove discussions or posts unless there is sensitive information in them as this would crush the context of many discussions.

But we are about to create an addon to let users handle account removal that doesn‘t hurt the forums readability.

@charrondev

When I had a look at the API I came across a question that hasn't been answered then. I would still be interested in the question, though.

Let's assume I would like to create a fancy catalogue page for tags (whatever that might be), I would start by writing a public function tagsController_catalogue_create() { which would show my page. But what would I have to do to make that info available as /api/v2/tags/catalogue?

By the way: it took me quite some time to set up a simple ApiController for testing. A full blown example in the docs would be helpful.