Bug 32856

Summary:	JavaScript error for unmapped UDM syntax types
Product:	UCS	Reporter:	Alexander Kläser <klaeser>
Component:	UMC - Domain management (Generic)	Assignee:	UMC maintainers <umc-maintainers>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	P5	CC:	best, gohmann
Version:	UCS 3.1
Target Milestone:	UCS 3.x
Hardware:	Other
OS:	Linux
See Also:	https://forge.univention.org/bugzilla/show_bug.cgi?id=38743 https://forge.univention.org/bugzilla/show_bug.cgi?id=38762
What kind of report is it?:	---	What type of bug is this?:	---
Who will be affected by this bug?:	---	How will those affected feel about the bug?:	---
User Pain:		Enterprise Customer affected?:
School Customer affected?:		ISV affected?:
Waiting Support:		Flags outvoted (downgraded) after PO Review:
Ticket number:		Bug group (optional):
Max CVSS v3 score:
Bug Depends on:
Bug Blocks:	32857

Description Alexander Kläser

2013-10-14 13:50:28 CEST

Using a syntax which is not mapped to a UMC widget (e.g., Bzip2Base64Upload), one will obtain a JavaScript error and the UDM object cannot be opened:

> "TypeError: Cannot call method 'indexOf' of undefined

This behaviour is due to the mapping logic in udm/DetailPage.js:

> ...
> if ( iprop.id.slice( 0, 1 ) == '$' && iprop.id.slice( -1 ) == '$' ) {
>   properties.push(iprop);
>   return;
> }
> if ( 'LinkList' == iprop.type ) {
>   iprop.multivalue = false;
> } else if ( iprop.type.indexOf('MultiObjectSelect') >= 0 ) {
> ...

In this case, type is undefined.

It would be helpful to handle undefined types and assign a dummy widget type such that the user may see that a property is not rendered properly. Not sure whether this problem occurs in 3rd party extensions.

Comment 1 Stefan Gohmann

2017-06-16 20:38:30 CEST

This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.

Comment 2 Stefan Gohmann

2017-08-08 07:09:52 CEST

This issue has been filed against UCS 3.1.

UCS 3.1 is out of maintenance and many UCS components have vastly changed in later releases. Thus, this issue is now being closed.

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