Bug 32856 - JavaScript error for unmapped UDM syntax types
JavaScript error for unmapped UDM syntax types
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: UMC - Domain management (Generic)
UCS 3.1
Other Linux
: P5 normal (vote)
: UCS 3.x
Assigned To: UMC maintainers
:
Depends on:
Blocks: 32857
  Show dependency treegraph
 
Reported: 2013-10-14 13:50 CEST by Alexander Kläser
Modified: 2017-08-08 07:09 CEST (History)
2 users (show)

See Also:
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:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Kläser univentionstaff 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 univentionstaff 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 univentionstaff 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.