Default content blocks give fatal error on new nodes

Created on 24 October 2023, about 1 year ago

Problem was introduced in on of the latest beta releases.
Cause is handling block_revision_id/block_id setting before block_serialized.
Serialized data will always contain more up to date info if it is available and should indicate we need a new id.

🐛 Bug report
Status

Fixed

Version

1.0

Component

Code

Created by

🇧🇪Belgium weseze

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024