Token replacements lead to leaked metadata

Created on 21 March 2019, over 5 years ago
Updated 25 March 2024, 8 months ago

We have a business rule that sends out an email when a node is created. When creating a node using JSONAPI the token replacements cause a HTTP 500 error due to the leaked metadata.

Patch forthcoming.

🐛 Bug report
Status

Needs review

Version

3.0

Component

Code

Created by

🇧🇪Belgium matthijs

Live updates comments and jobs are added and updated live.
  • Performance

    It affects performance. It is often combined with the Needs profiling tag.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024