Issue with Component Order Mismatch in Dynamic Zone After upgrade to v5.4.0

[panupong-chaetan]

Bug report

Required System information

• Node.js version: 18.18.2
• NPM version: 10.9.0
• Strapi version: 5.4.1
• Database: mysql
• Operating system: windows 10
• Is your project Javascript or Typescript: Typescript

Description of the Issue

The order of components displayed in the dynamic zone on localhost does not match the order configured in the Strapi admin panel. This discrepancy makes it difficult to ensure consistent rendering between the admin interface and the local environment.
This problem occured after upgrade from v5.3.0 to v5.4.0.
Previously I used v5.3.0 without any problems.

Steps to reproduce the behavior

1. Log in to the Strapi admin panel.
2. Navigate to a content type that includes a dynamic zone.
3. Add multiple components to the dynamic zone and arrange them in a specific order.
4. Save the changes.
5. Query the content type through the API or render it in the frontend on localhost.
6. Observe that the order of the components displayed does not match the order configured in the admin panel.

Expected behavior

The order of components displayed on localhost should match the order set in the Strapi admin panel for the dynamic zone.

Actual behavior

The order of components displayed on localhost is incorrect and does not align with the order set in the Strapi admin panel.

Screenshots

Code snippets

[strapi-bot]

This issue has been mentioned on Strapi Community Forum. There might be relevant details there:

https://forum.strapi.io/t/issue-with-component-order-mismatch-in-dynamic-zone-on-localhost/48858/1

[simon-roland]

Pretty sure this is related to the issue described in #22228

[panupong-chaetan]

Pretty sure this is related to the issue described in #22228

Yes, before upgrading from 5.3.0 to 5.4.0 it worked fine.

[DSK-QwQ]

Can confirm downgrading again fixes the issue. 5.4.0 is the culprit.