Re: [drupal:dries] /modules user.module
Let me try again. What I wanted to send is that we should either a) delete the user and all of his content. b) block the user If you delete the user and leave the content then you have broken attribution rights which is not a good idea. Regards NK
Karoly Negyesi wrote:
Let me try again.
What I wanted to send is that we should either
a) delete the user and all of his content. b) block the user
If you delete the user and leave the content then you have broken attribution rights which is not a good idea.
Regards
NK
- block the user and unpublish the content
Please see this issue: http://drupal.org/node/8 There is *no* 100% correct situation, it needs to be flexible on a per user basis. ted On 1/9/06, Moshe Weitzman <weitzman@tejasa.com> wrote:
Karoly Negyesi wrote:
Let me try again.
What I wanted to send is that we should either
a) delete the user and all of his content. b) block the user
If you delete the user and leave the content then you have broken attribution rights which is not a good idea.
Regards
NK
- block the user and unpublish the content
This is one of those issues that come up like, every three weeks? Last time this was discussed we seemed to agree that : * There is not *one* way to do this. It very much depends on the site. * Some people preferred to change the status of nodes, others to delete nodes, again others to just change the username into something like "deleted user" (and block that user). * Drupal should not go for a default way, but rather present good hooks and APIs and let it be the way it is now: do nothing. Then the contribbuted modules could do it in fancy ways, acc to what the site prefers to do. Am i missing something? Or should we rather pick up the discussion there and get closer to a solution :) ? Bèr -- PGP ber@webschuur.com http://www.webschuur.com/sites/webschuur.com/files/ber_webschuur.asc PGP berkessels@gmx.net http://www.webschuur.com/sites/webschuur.com/files/ber_gmx.asc
On Mon, 09 Jan 2006 21:24:28 +0100, Bèr Kessels <ber@webschuur.com> wrote:
This is one of those issues that come up like, every three weeks?
Last time this was discussed we seemed to agree that : * There is not *one* way to do this. It very much depends on the site. * Some people preferred to change the status of nodes, others to delete nodes, again others to just change the username into something like "deleted user" (and block that user). * Drupal should not go for a default way, but rather present good hooks and APIs and let it be the way it is now: do nothing. Then the contribbuted modules could do it in fancy ways, acc to what the site prefers to do.
Am i missing something? Or should we rather pick up the discussion there and get closer to a solution :) ?
There are lot of good solutions. But there are a lot of _bad_ ones and we shall avoid those.
On Mon, 09 Jan 2006 20:52:02 +0100, Moshe Weitzman <weitzman@tejasa.com> wrote:
Karoly Negyesi wrote:
Let me try again. What I wanted to send is that we should either a) delete the user and all of his content. b) block the user If you delete the user and leave the content then you have broken attribution rights which is not a good idea. Regards NK
- block the user and unpublish the content
I like that...
Karoly Negyesi wrote:
On Mon, 09 Jan 2006 20:52:02 +0100, Moshe Weitzman <weitzman@tejasa.com> wrote:
Karoly Negyesi wrote:
Let me try again. What I wanted to send is that we should either a) delete the user and all of his content. b) block the user If you delete the user and leave the content then you have broken attribution rights which is not a good idea. Regards NK
- block the user and unpublish the content
I like that...
This might not be sufficient under certain circumstances. Under German (and maybe EUropean) privacy law, I can demand that my data be erased completely. Use case: an ecommerce site where you wish to cancel your acount for some reason. Also, it might be required that the user's content be deleted (say from a discussion board). Cheers, Gerhard
Folks, Simon and myself are working on a patch that should make everyone happy, or so we hope. There is not *set* solution, it has to be flexible. Karoly might want to just block his users but leave the content. Gerhard, on the other hand, might want to delete all content. Regardless, Drupal should accomdate both and it should be somehow get broken going either route. Privacy is a big issue and with the rate that Drupal is growing, needs to be adressed soon. Simon and myself are working on a patch and will have something soon. Stay tuned here: http://drupal.org/node/8 (yes trying to beat Gerhards recent patch for issue 176 ;-) ted On 1/9/06, Gerhard Killesreiter <gerhard@killesreiter.de> wrote:
Karoly Negyesi wrote: This might not be sufficient under certain circumstances. Under German (and maybe EUropean) privacy law, I can demand that my data be erased completely.
Use case: an ecommerce site where you wish to cancel your acount for some reason. Also, it might be required that the user's content be deleted (say from a discussion board).
On Mon, 09 Jan 2006 22:58:40 +0100, Theodore Serbinski <tss24@cornell.edu> wrote:
Folks, Simon and myself are working on a patch that should make everyone happy, or so we hope. There is not *set* solution, it has to be flexible.
Karoly might want to just block his users but leave the content.
Gerhard, on the other hand, might want to delete all content.
Folks, understand me: I am OK with both. But if I am not mistaken we currently have a third, erroneus way: delete user and leave content. THIS is what's not good.
On 1/9/06, Karoly Negyesi <karoly@negyesi.net> wrote:
Folks, understand me: I am OK with both. But if I am not mistaken we currently have a third, erroneus way: delete user and leave content. THIS is what's not good.
Agreed. That is why one of the options during the delete will handle this special case: 2 different options as Simon points out (and the admin will be able to choose what to do at time of deletion because it depends on the user account, site, etc...): 1. leave username and delete all personal information and account info and set account status to a new 3rd type, 'deleted' ... by doing this, this account and username can still be permanently deleted if need be 2. delete entire account and username, and set all posts to 'Unknown' or 'Anoymous' At time of deletion, whomever is deleting, can choose one of these options if it fits in the deletion workflow. This should account for all scenarios and everyone should be happy, no? ted
This should account for all scenarios and everyone should be happy, no?
Maybe. If you add too much code accommodating the needs of each scenario, you might run into bloat complaints. I suggest ignoring unlikely combinations or making them available only with contrib modules. -moshe
On 1/9/06, Moshe Weitzman <weitzman@tejasa.com> wrote:
This should account for all scenarios and everyone should be happy, no?
Maybe. If you add too much code accommodating the needs of each scenario, you might run into bloat complaints. I suggest ignoring unlikely combinations or making them available only with contrib modules.
Agreed, but it seems to be only a few likely scenarios that I think we can agree on :-) ted
Op dinsdag 10 januari 2006 02:06, schreef Moshe Weitzman:
Maybe. If you add too much code accommodating the needs of each scenario, you might run into bloat complaints. I suggest ignoring unlikely combinations or making them available only with contrib modules.
Yes +1. What you are trying in node 8 is to provide options for every use case, for every possible combination and for every possible scenario. You /will/ miss a few cases and scenarios. You /will/ offer a lot of hardly ever used options. from my previous mail: * There is not *one* way to do this. It very much depends on the site and wishes ... * Drupal should not go for a default way, but rather present good hooks and APIs and let it be the way it is now [yet possibly better]: do nothing. Then the contributed modules could do it in fancy ways, acc. to what the site developer prefers to do. Some (silly) modules I can thing of: * delete_my_content.module * delete_my_account_and_content.module * advanced_user_blocking.module * unpublish_by_user.module Bèr PS: I beleive most of these modules are already possible, yet no-one made them. Lack of interest? Is core already good enough? Or is drupal core too restricting? -- [ Bèr Kessels | Drupal services www.webschuur.com ]
[..] Some (silly) modules I can thing of: * delete_my_content.module * delete_my_account_and_content.module * advanced_user_blocking.module * unpublish_by_user.module [..] PS: I beleive most of these modules are already possible, yet no-one made them. Lack of interest? Is > core already good enough? Or is drupal core too restricting?
One of those silly ones is this module I uploaded here: http://drupal.org/node/23929 It lists all nodes where the author is missing. (did not bother to properly upload the module to contrib yet) Jadwigo
On a 4.6 system, a client accidentally deleted a user. I was able to recover the data by recreating the users table row for this person. The nodes he authored were still there. Morale of the story: Do not delete the content. Make it anonymous, or unpublish it if you want. If you reall want the space, then there can be an admin option to "purge deleted posts" or something along those lines. On 1/9/06, Karoly Negyesi <karoly@negyesi.net> wrote:
Let me try again.
What I wanted to send is that we should either
a) delete the user and all of his content. b) block the user
If you delete the user and leave the content then you have broken attribution rights which is not a good idea.
Regards
NK
participants (8)
-
Bèr Kessels -
Gerhard Killesreiter -
Karoly Negyesi -
karoly＠negyesi.net
-
Khalid B -
Lodewijk Evers -
Moshe Weitzman -
Theodore Serbinski