Fatal Error Occurs due to Incorrect Order of Bulk Delete Event Action

Created on 14 May 2024, 7 months ago

Problem/Motivation

The Bulk delete event that is triggered from (for example entity track) admin/config/entity-track/batch-update will result in a fatal error.
When deleteTrackingInformation is called it wil result in a fatal error.

Steps to reproduce

1. Perform a bulk delete operation using the admin/config/entity-track/batch-update page.
2. Observe the fatal error that occurs.

Proposed resolution

Review and add the following patch / MR

Remaining tasks

Test and review bij community

User interface changes

None

API changes

None

Data model changes

None

🐛 Bug report

Status

Needs review

Version

4.0

Component

Code

Created by

🇳🇱Netherlands Remco Hoeneveld

Live updates comments and jobs are added and updated live.

Merge Requests

!83Fatal Error Occurs due to Incorrect Order of Bulk Delete Event Action
Open
🇳🇱Netherlands Remco Hoeneveld
updated 7 months ago

Comments & Activities

Issue created by @Remco Hoeneveld
Merge request !83Issue #3175056 by marcoscano, seanB: Split module in generic tracking API and... → (Open) created by Remco Hoeneveld
Status changed to Needs review 7 months ago12:35pm 14 May 2024
Comment 7 months ago →
🇮🇳India Akram Khan Cuttack, Odisha
Verified #2 error is resolved. Added both before and after patch snap for the reference.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024

Fatal Error Occurs due to Incorrect Order of Bulk Delete Event Action

Problem/Motivation

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Merge Requests

!83Fatal Error Occurs due to Incorrect Order of Bulk Delete Event ActionOpen

Comments & Activities

!83Fatal Error Occurs due to Incorrect Order of Bulk Delete Event Action
Open