Bug 31391 - empty room after switching to the same room
empty room after switching to the same room
Status: CLOSED WORKSFORME
Product: UCS@school
Classification: Unclassified
Component: UMC - Computer room
UCS@school 3.1
Other Linux
: P5 normal (vote)
: UCS@school 3.1 R2
Assigned To: Sönke Schwardt-Krummrich
Alexander Kläser
: interim-2
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-05-17 13:40 CEST by Florian Best
Modified: 2013-06-07 21:38 CEST (History)
1 user (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 Florian Best univentionstaff 2013-05-17 13:40:13 CEST
When switching to the same room as the current selected room i am getting the following error which results in an empty room list.

646 | if (item.DemoServer[0] === true) {
→ Uncaught TypeError: Cannot read property '0' of undefined 

item
Object
_0: 14
_RI: true
_S: Object
connection: Array[1]
id: Array[1]
ip: Array[1]
mac: Array[1]
name: Array[1]
teacher: Array[1]
__proto__: Object
Comment 1 Sönke Schwardt-Krummrich univentionstaff 2013-05-17 13:48:30 CEST
I cannot reproduce this error in two instances.
Comment 2 Alexander Kläser univentionstaff 2013-05-28 19:00:26 CEST
I cannot reproduce this behaviour, either. Looking at the code, DemoServer is always set initially in the query command, therefore its value should always be accessible. Unless there are more specific information on how to reproduce the problem → VERIFIED
Comment 3 Sönke Schwardt-Krummrich univentionstaff 2013-06-07 21:38:36 CEST
UCS@school 3.1 R2 has been released:
http://download.univention.de/doc/release-notes-ucsschool-3.1-rev2.pdf

If this error occurs again, please use "Clone This Bug".