You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have checked that the bug exists in the dev-development branch
Yes
I have checked that there are no already open issues or recently closed issues about this bug
Yes
Describe the bug
When editing a workspace record in a translation page, the changes of the workspace record are not reflected in the frontend. Non-translated pages don't show that issue.
To Reproduce
Steps to reproduce the behavior:
Create a page and a translation with one Flux-powered content element with at least one defined field.
In a workspace edit the translation of the content element.
Preview workspace version of record and see changes not reflected.
Expected behavior
Changes on the workspace record are reflected in frontend.
Screenshots
Additional context
The problem originates in Classes/Controller/AbstractFluxController->getRecord(), where the record data from the ContentObjectRenderer, which at this point is fully overlayed, is being overwritten with the data of the language record.
The text was updated successfully, but these errors were encountered:
I have checked that the bug exists in the
dev-development
branchYes
I have checked that there are no already open issues or recently closed issues about this bug
Yes
Describe the bug
When editing a workspace record in a translation page, the changes of the workspace record are not reflected in the frontend. Non-translated pages don't show that issue.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Changes on the workspace record are reflected in frontend.
Screenshots
Additional context
The problem originates in
Classes/Controller/AbstractFluxController->getRecord()
, where the record data from theContentObjectRenderer
, which at this point is fully overlayed, is being overwritten with the data of the language record.The text was updated successfully, but these errors were encountered: