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.
Steps to reproduce the behavior
Log in to the Strapi admin panel.
Navigate to a content type that includes a dynamic zone.
Add multiple components to the dynamic zone and arrange them in a specific order.
Save the changes.
Query the content type through the API or render it in the frontend on localhost.
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.
This issue significantly impacts the usability of Strapi for managing dynamic content. Content creators need to rely on the exact order of components in a Dynamic Zone to ensure proper frontend rendering. The current behavior forces workarounds like adding custom order fields or manual sorting, undermining Strapi’s promise of simplicity and flexibility.
