Bug #13511

Regression causing data on related tables to be dropped on save

Added by Dan Gillean 2 months ago. Updated 21 days ago.

Status:NewStart date:05/27/2021
Priority:CriticalDue date:
Assignee:-% Done:


Target version:Release 2.7.0
Google Code Legacy ID: Tested version:
Sponsored:No Requires documentation:No


Some recent commit has caused a regression that is impacting multiple entities, and causing some data to be dropped on save. So far confirmed examples include:

  • event dates added to new or edited descriptions
  • Note data (any custom rad note type; general notes, etc)
  • actor-actor relationships

This was first found via Vagrant testing on 2021-05-25 when testing in Vagrant. The behavior has been confirmed by a forum user on 05-27, here:

To reproduce, create a new description, add a date of creation and a general note, and save.


First theory was the recent large community PR (here ) might have broken it. However, my VM did not include the commits from the PR when first reproduced - see my attached tig output

Next theory was that the STRICT_TRANS_TABLES sql_mode might be causing it. I checked and this was enabled in the vagrant box (so we can find more incompatibilities, per issue # ). However, when I changed sql modes, restarted MySQL, cleared the application cache/PHP-FPM, and reindexed, I was still unable to add event dates to descriptions. It's possible that this is still the culprit somehow but I did double-check that my setting changes were in effect.

There are no relevant error messages I can see in the webserver logs.

The forum user also added:

I enabled general_log in MySQL so I could trace the SQL being generated by attempts to change those values, to see if the INSERT/UPDATE queries were being generated, but failing silently on the DB side. As far as I can tell, no SQL call is being made for the activities that fail.

tig-2021-05-27.png (215 KB) Dan Gillean, 05/27/2021 04:29 PM


#1 Updated by Steve Breker 2 months ago

Replicated in latest Vagrant VM.
- created new VM
- pulled all latest commits into atom qa/2.x
- did a tools:purge --demo
- set default template to RAD
- created new description with event date
- save
- dates not recorded on description

- set default template to ISADG
- created new description with event date and note
- save
- dates and notes not saved with description.

#2 Updated by Dan Gillean 21 days ago

  • Priority changed from High to Critical

This issue is blocking the QA of other issues, and must be fixed before we can prepare a 2.7 release. Bumping up priority.

Also available in: Atom PDF