Bug 42400 – move python hook code from ImportUser class to User class

Bug 42400 - move python hook code from ImportUser class to User class


Summary:	move python hook code from ImportUser class to User class

Status:	CLOSED WONTFIX

Product:	UCS@school
Classification:	Unclassified
Component:	Ucsschool-lib
Version:	UCS@school 4.1 R2
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	UCS@school 4.1.x
Assigned To:	UCS@school maintainers
QA Contact:

URL:
Keywords:

Depends on:	41572
Blocks:	42541
	Show dependency tree / graph

Reported:	2016-09-15 11:30 CEST by Daniel Tröder
Modified:	2023-06-12 15:39 CEST (History)
CC List:	2 users (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	2: Improvement: Would be a product improvement
Who will be affected by this bug?:	5: Will affect all installed domains
How will those affected feel about the bug?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.114
Enterprise Customer affected?:
School Customer affected?:	Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Daniel Tröder

2016-09-15 11:30:07 CEST

+++ This bug was initially created as a clone of Bug #41572 +++

If PyHooks are run from User, they are also executed by UMC-modules (like the original hooks).

Comment 1 Daniel Tröder

2016-09-30 09:28:22 CEST

IMHO this should be moved further up the chain into UCSSchoolHelperAbstractClass, where are also the legacy hooks.

This will allow to use PyHooks also when creating OUs, printers, computers, groups etc.

Comment 2 Sönke Schwardt-Krummrich

2019-02-05 21:16:31 CET

This issue has been filled against UCS@school 4.1 (R2). The maintenance with bug 
and security fixes for UCS@school 4.1 (R2) has ended on 5th of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3 (or later). 
Please contact your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug"
or simply reopen the issue. In this case please provide detailed information on
how this issue is affecting you.