Open wezell opened 2 weeks ago
Not reproducible in LTS
No, but the infinity relationships being stored in the block are, unless you backported the fix from last week.
Are you referring to this one? https://github.com/dotCMS/core/issues/28659 If so, then yes, we will need to backport it, as it is currently queued for backporting.
There are some videos in auth that can't be edited and seem related to this:
https://authoring.dotcms.com/dotAdmin/#/c/content/7c2fc123-dd3e-401b-812f-a8adab7b84ca
Pass Internal QA: Works as expeceted
Failed: Tested on trunk_2b6105d, Docker, macOS 14.5, FF v126.0.1
I'm getting this error when reproducing this issue.
Hi @josemejias11 not sure if it is related to block editor or even the issue reported here, may be we can see it in another issue
Hi @jdotcms, lets make @wezell the decider here. If he says the error can be review in another card. there's no problem on my end whatsoever. thanks!
@josemejias11, this is a different issue - we should open a card for it and add the jackson optional mapper to our ObjectMapper code.
Approved: Tested on trunk_2b6105d, Docker, macOS 14.5, FF v126.0.1
The reported issue above will be covered on the card https://github.com/dotCMS/core/issues/29041
Parent Issue
No response
Problem Statement
I think this is happening when a field has been converted to a block from a wysiwyg but the content in the field is still HTML:
Steps to Reproduce
Acceptance Criteria
Important fix - Refresh references should not cause/throw an error. We can log a warning, but it should not prevent the content from rendering or api calls, etc.
Additionally - we should skip the refreshReferences if the block content is not json
dotCMS Version
24.06.x
Proposed Objective
Quality Assurance
Proposed Priority
Priority 1 - Show Stopper
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
No response
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response