[UIIN-323] "Please refresh page" errors of type "cannot read <xyz> of undefined" Created: 12/Jul/18  Updated: 03/Nov/23  Resolved: 27/Sep/18

Status: Closed
Project: ui-inventory
Components: None
Affects versions: None
Fix versions: None

Type: Bug Priority: P2
Reporter: Niels Erik Nielsen Assignee: Jakub Skoczen
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: File PublisherBug.mp4     PNG File Screenshot from 2018-07-17 13-43-19.png     PNG File image-2018-07-12-10-02-04-641.png    
Issue links:
Relates
relates to FOLIO-1165 Requests 3rd pane not showing details Closed
Sprint:
Development Team: Other dev

 Description   

Placeholder issue for testers to report errors of this type until we find out if it's one or more generic problems or rather similarly looking problems of individual UI modules :

Occurrence 2. Ann-Marie added a video showing a similar bug appears when creating an Inventory Instance.

    • Create the instance with Title, Resource Type, Format.
    • Click on the "Publication" accordion to open it, but don't add any info to those fields.
    • Then try to save.
    • The "Publisher Bug" illustrated in the video appears.
    • I can't refresh it away. It's also showing in demo.folio.org, so not just snapshot-stable.


 Comments   
Comment by Ann-Marie Breaux (Inactive) [ 12/Jul/18 ]

Alexander Soto Anya Charlotte Whitt See Occurrence 2 and the video above. We discovered this when the ICs were testing in Inventory earlier today. Thanks.

Comment by Niels Erik Nielsen [ 17/Jul/18 ]

Ann-Marie Breaux - What this test is doing is adding a publisher element with no data in it. Since this doesn't make sense, the UI should prevent it. Or rather:

1) The Instance form should prevent an empty publisher element from being submitted
2) The back-end should probably either refuse to persist such an instance or silently remove the obsolete object
3) The UI should defend itself from this data scenario, should it occur anyway (that is, the UI should not error out)

Parts of these fixes are on their way, see UIIN-207 Closed

Comment by Niels Erik Nielsen [ 17/Jul/18 ]

test-exercise, test-loan-renewals and /users test currently fail due to this error in ui-users:

Comment by Ann-Marie Breaux (Inactive) [ 17/Jul/18 ]

Thanks, Niels Erik Nielsen That makes sense. Glad to hear that some fixes are on the way.

Comment by Cate Boerema (Inactive) [ 19/Jul/18 ]

Niels Erik Nielsen, this is unassigned but it looks like you are working on it. Should we assign it to you and to this sprint? Just trying to clean up the Core team unassigned backlog.

Comment by Ann-Marie Breaux (Inactive) [ 07/Aug/18 ]

Alexander Soto Holly Mistlebauer See this bug and the comments on it

Comment by Niels Erik Nielsen [ 27/Sep/18 ]

I don't think this issue serves any purpose now.

Generated at Thu Feb 08 23:12:37 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.