Hi all,
Pure looking at things structurally when deleting a user the following
should happen:
1. Unlink all his objects
2. Delete all his objects (perhaps take a CPO export of his entire
repository beforehand as a final backup?)
3. Contact all applications / packages with a request to delete all
references to user x (which isn't all that unsimilar from the
object unlink)
If and when all that has been implemented everywhere, the user itself
could be deleted and there shouldn't be any problems.
Practically speaking it's a loooooooooot of checks that need to be
executed and even more statements that need to be executed to actually
make it all happen. Te easy way out is to not actually delete the user
but deactivate him. That might work in some cases, depending on your
company's policy, but it does not remove the need for an actual delete
in those cases where it is explicitly needed and/or requested.
Best regards,
Hans
On 01/04/2011 08:56, Sven Vanpoucke wrote:
Hello All
I would like to discuss the deletion of a users in chamilo 2.0. At
this point the user his content objects are NOT removed because they
would cause a lot of issues where the content objects are published or
used in other content objects. It's important that we define some kind
of procedure that should happen when a user gets deleted. What happens
with his content objects, what happens with the references to the user
id's in all the other tables (tracking, subscriptions etc...).?
At this point i'm pretty sure that when you delete a user, the system
will break on some places because of the display for the username
without the check if the user still exists. I implemented a new
function in the userdatamanager which gets the user's fullname by user
id which returns the fullname if the user exists and User unknown if
the user doesn't exist anymore but i didn't have the time / resources
yet to change this feature on the entire platform. If you are
developing new features i would ask you to now use this function, or
at least check if the user still exists in the platform to avoid
breakage.
--
*Hans De Bisschop*
Hoofddeskundige ICTO | Lead Developer Chamilo 2.0
Software Coordinator Chamilo Association
Erasmushogeschool Brussel
Nijverheidskaai 170 | B-1070 Brussel
T 02 559 02 54 | i 254
hans.de.bissc...@ehb.be <mailto:hans.de.bissc...@ehb.be> |
www.erasmushogeschool.be <http://www.erasmushogeschool.be/>
Kom eens langs: www.erasmushogeschool.be/infodagen
<http://www.erasmushogeschool.be/infodagen>
of lees onze elektronische nieuwsbrief: ehbrief.ehb.be
<http://ehbrief.ehb.be/>
P Before printing, think about the environment
_______________________________________________
Dev mailing list
Dev@lists.chamilo.org
http://lists.chamilo.org/listinfo/dev
