[CONTEDIT-510] Inconsistent structure when creating story without blocks Created: 02/Feb/23  Updated: 19/Sep/23  Resolved: 19/Sep/23

Status: Closed
Project: Content Editor
Component/s: None
Affects Version/s: 2.1.3
Fix Version/s: 2.1.4

Type: Bug Priority: Normal
Reporter: Roberto Gaona Assignee: Dai Ha
Resolution: Duplicate Votes: 4
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
causality
relation
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Epic Link: AuthorX Support
Team: AuthorX
Work Started:

 Description   

Steps to reproduce

This can be reproduced easily on our demo website

  1. Create two stories, one defining a simple block of text for example and other empty (just fill the mandatory fields).
  2. Edit the empty story to add a text block
  3. Check in JCR the structure created for each story. The structure of the one created with blocks from the start will have a blocks node while the recently edited won't although content is the same.

When opening the recently edited story, a warning will be displayed stating:

"Since version 2.1-beta of the Content Editor module, the blocks in the Stories app can handle internationalized content. The current block structure is not compatible with the i18n configuration of the 'blocks' field in the app. Please ask your developer to set 'i18n: false' for the field."

Expected results

Editing the story yields the same result as creating the story with blocks all from the start

Actual results

Structure isn't consistent and it throws warnings

Workaround

Development notes



 Comments   
Comment by Remy Scherrer [ 14/Sep/23 ]

Hi there

We have received a question from our customer regarding this ticket. When can we expect this bug to be fixed? This is an important issue for our customer and it would be great if you could fix this bug as soon as possible. 

Many thanks and best regards
Remy Scherrer

Comment by Laura Delnevo [ 19/Sep/23 ]

The issue was fixed with CONTEDIT-516 in version 2.1.4.
Nevertheless, we re-validated the issue and we can confirm that the reported issue is no longer there 

Generated at Mon Feb 12 00:21:07 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.