-
-
Notifications
You must be signed in to change notification settings - Fork 9.2k
Closed
Labels
flag: EEIssues correlates to internal EE ticketIssues correlates to internal EE ticketissue: bugIssue reporting a bugIssue reporting a bugseverity: criticalIf the issue has a security impact or breaks core usage of the productIf the issue has a security impact or breaks core usage of the productsource: core:content-managerSource is core/content-manager packageSource is core/content-manager packagestatus: confirmedConfirmed by a Strapi Team member or multiple community membersConfirmed by a Strapi Team member or multiple community membersversion: 5Issue is present in Strapi 5Issue is present in Strapi 5
Description
Bug report
Required System information
- Node.js version: v18.20.4
- Yarn version: 1.22.22
- Strapi version: 5.4.0
- Database: MySQL
- Operating system: MacOS (darwin-arm64)
- Is your project Javascript or Typescript: TypeScript
Describe the bug
Strapi Not Saving Order of Components in Dynamic Zone When Published
Steps to reproduce the behavior
- Go to Article edit page
- Drag and Drop components in dynamic zone
- Click on Save
- Switch to Published tab
- See error: Component order is not save like expect
(in DB, columnarticle_cmps.orderis not saved for Published document, only saved for Draft document)
Expected Behavior:
The order of components in the dynamic zone should be preserved after publishing the content.
Actual Behavior:
The order of components is not preserved, and they appear in a different order after publishing.
Additional Information:
I have ensured that the dynamic zone is correctly configured in the Content-Type Builder.
I am using the latest version of Strapi.
I have not implemented any custom save logic for the dynamic zone.
Screen.Recording.2.2024-11-15.at.11.59.19.mov
millsoft and monolithedkjfranke, alexander-aleman, dimitrisganotis and maikelvanhaaren
Metadata
Metadata
Assignees
Labels
flag: EEIssues correlates to internal EE ticketIssues correlates to internal EE ticketissue: bugIssue reporting a bugIssue reporting a bugseverity: criticalIf the issue has a security impact or breaks core usage of the productIf the issue has a security impact or breaks core usage of the productsource: core:content-managerSource is core/content-manager packageSource is core/content-manager packagestatus: confirmedConfirmed by a Strapi Team member or multiple community membersConfirmed by a Strapi Team member or multiple community membersversion: 5Issue is present in Strapi 5Issue is present in Strapi 5
Type
Projects
Status
Fixed/Shipped
Status
Done