0007146: Deleting User in the admin interface does not delete related data - OXID eShop bugtrack

ID	Project	Category	View Status	Date Submitted	Last Update

0007146	OXID eShop (all versions)	2.5. Administer users	public	2020-06-03 09:27	2020-06-03 13:25

Reporter	[email protected]	Assigned To
Priority	normal	Severity	minor	Reproducibility	always
Status	closed	Resolution	duplicate
Product Version	6.2.1

Summary	0007146: Deleting User in the admin interface does not delete related data
Description	When a user is deleted in OXID related data (like additional addresses) should also be automatically deleted. This is done in the User-Model when the delete() method is called, which calls additional methods like for example "User->deleteAddresses()". "User->delete()" can receive an ID that should be deleted as an argument. Methods like "User->deleteAddresses()" do NOT use that passed ID, instead they always reference the ID of the currently loaded model. This comes into play when a user is deleted via the admin interface. "AdminListController->deleteEntry()" will call "User->delete()" with the ID as param, without actually loading the user model. This will delete the oxuser record, but not the related data, because the sub-delete-methods like "User->deleteAddresses()" do not respect the passed ID. So the solution would be either to pass the ID to delete to "User->deleteAddresses()", "User->deleteNewsletterSubscriptions()", etc. or to load the ID in to the user model in "AdminListController->deleteEntry()".
Steps To Reproduce	* Create a new user in the OXID admin interface (or in the shop frontend, doesn't matter) * Add an additional delivery address to that user * Note the OXID-ID of that user * Delete that user in the OXID admin interface * Look into the oxaddress table and search for the user OXID-ID in "OXUSERID" -> The database row of the address still remains
Tags	No tags attached.

Theme	Not defined
Browser	Not defined
PHP Version	Not defined
Database Version	Not defined