Bug #13585

Additional language of materials values don't get saved

Added by Redmine Admin 6 months ago. Updated 3 months ago.

Status:InvalidStart date:11/23/2021
Priority:MediumDue date:
Assignee:-% Done:

0%

Category:Information object
Target version:Release 2.7.0
Google Code Legacy ID: Tested version:2.7
Sponsored:No Requires documentation:

Description

To reproduce

Log in as a user with edit privileges
Navigate to an information object that has a language of materials value
Open the edit screen and add one or more additional languages to the language of materials field
Save the record

Resulting error

Additional languages do not appear in the language of materials field. This is happening on AtoM 2.6.0 - 192.

Expected result

A bulleted list showing all languages added in the edit screen


Related issues

Related to Access to Memory (AtoM) - Task #13530: Create new versions of existing themes with Bootstrap 5 In progress 06/17/2021

History

#1 Updated by Redmine Admin 6 months ago

  • Subject changed from Additional langue of materials values don't get saved to Additional language of materials values don't get saved

#2 Updated by David Juhasz 6 months ago

  • Tested version 2.7 added

This bug is affecting qa/2.x, even though the version number shown in AtoM is "2.6.0 - 192"

#3 Updated by David Juhasz 6 months ago

  • Category set to Information object
  • Target version set to Release 2.7.0

#4 Updated by Tessa Walsh 6 months ago

I am able to recreate this issue on the affected client test server intermittently, but not in a local development environment. Sometimes the language just isn't added, other times it is, even for the same description. Once it works it seems to work a few times in a row. From what I can tell, other fields don't seem to be affected. In fact, changes made in other fields will be applied even when the language changes are not on the same request. I don't think it's a caching issue because when the change doesn't work, the database reflects the same state as the UI (i.e. the new language isn't added in the `property_i18n` table either).

It's possible there's an issue with validating just this one field (validator is set here: https://github.com/artefactual/atom/blob/qa/2.x/apps/qubit/modules/default/actions/editAction.class.php#L80-L86) but I haven't yet been able to successfully reproduce it in a dev environment to determine if that's actually the issue.

#5 Updated by José Raddaoui Marín 3 months ago

  • Status changed from New to Invalid

I believe this was an issue with the Bootstrap 5 upgrade that was already solved on the development branch.

#6 Updated by José Raddaoui Marín 3 months ago

  • Related to Task #13530: Create new versions of existing themes with Bootstrap 5 added

Also available in: Atom PDF