Bug #13342

Problem: Adding Actor relationships via GUI is no longer working

Added by Peter Van Garderen 5 months ago. Updated 4 months ago.

Status:VerifiedStart date:06/03/2020
Priority:HighDue date:
Assignee:Peter Van Garderen% Done:

0%

Category:Actor
Target version:Release 2.6.0
Google Code Legacy ID: Tested version:
Sponsored:No Requires documentation:

Description

You can save the record and no error message appears. However, the newly added relationship does not appear on the Actor record. Note that adding relationships via CSV import is still working.

Screen Shot 2020-06-17 at 12.03.24 PM.png (116 KB) Peter Van Garderen, 06/17/2020 03:13 PM

Screen Shot 2020-06-17 at 12.01.35 PM.png (214 KB) Peter Van Garderen, 06/17/2020 03:15 PM

Screen Shot 2020-06-17 at 12.01.52 PM.png (303 KB) Peter Van Garderen, 06/17/2020 03:15 PM

Screen Shot 2020-06-17 at 12.02.39 PM.png (241 KB) Peter Van Garderen, 06/17/2020 03:15 PM

Screen Shot 2020-06-17 at 12.02.59 PM.png (225 KB) Peter Van Garderen, 06/17/2020 03:15 PM


Related issues

Related to Access to Memory (AtoM) - Feature #13280: Create relationships between existing authority records v... Verified 06/27/2020
Related to Access to Memory (AtoM) - Bug #12709: Error when creating new description or actor with access ... Verified 01/14/2019

History

#1 Updated by Peter Van Garderen 4 months ago

  • Related to Feature #13280: Create relationships between existing authority records via CSV import added

#2 Updated by Peter Van Garderen 4 months ago

  • Assignee changed from Mike Cantelon to David Juhasz

it seems to be related to an update to js/autocomplete.js
If you git check out f1eba0b41dc2fde049324681bc2b92f7958ebd12 then stash the version of that file somewhere you can check out the latest commit and overwrite js/autocomplete.js and it should work

#3 Updated by Peter Van Garderen 4 months ago

  • Related to Bug #12709: Error when creating new description or actor with access point terms added

#4 Updated by David Juhasz 4 months ago

  • Status changed from New to QA/Review
  • Assignee changed from David Juhasz to Peter Van Garderen

I've merged a fix to qa/2.6.x for this bug: https://github.com/artefactual/atom/commit/8f89e0b0f49942bd08f85fbcfe1443e675b81ff9

It's ready for QA/Review

#5 Updated by Peter Van Garderen 4 months ago

I've QA'ed the fix but I'm still experiencing the original bug.

I rebased to qa/2.6.x 8f89e0b0f and ran `php symfony cc`, `php symfony tools:upgrade-sql`, and `php symfony search:populate`

I create a new relationship between two existing Actor records ("Associative", "is a friend of"). The record saves. A notification is given that the actor record has been updated and that the related descriptions are being updated asynchronously. Following the link to the job scheduler page shows that task completed successfully.

However, when returning to the Actor view or edit page, the relationship is not appearing.

See the attached screencaps.

#6 Updated by Peter Van Garderen 4 months ago

  • Status changed from In progress to Verified
  • Assignee changed from David Juhasz to Peter Van Garderen

Turned out to be an issue with cached Javascript. Verified this fix is working on Firefox and Chrome with clean caches.

Also available in: Atom PDF