Dynamic zone breaks after upgrading from 4.9.2 to 4.11.0

[jastrand]

Bug report

Required System information

• Node.js version: 16
• NPM version: 6
• Strapi version: 4.11.0
• Database: postgres
• Operating system: ios

Describe the bug

After upgrading from 4.9.2 to 4.11.0 strapi admin breaks with "Woops! Something went wrong. Please, try again" after trying to use a component in the dynamic zone.

Steps to reproduce the behavior

1. In the strapi admin ui, go to any collection type using dynamic zone.
2. Click on any of the components in the dynamic zone to add it
3. See error "Woops! Something went wrong. Please, try again" and the console logs:

TypeError: Cannot read properties of undefined (reading 'attributes')
    at Object.entries.reduce (content-manager.4e46c41a.chunk.js:6660:67)
    at Array.reduce (<anonymous>)
    at findAllAndReplace (content-manager.4e46c41a.chunk.js:6651:39)
    at content-manager.4e46c41a.chunk.js:6782:40
    at produce (main.e40cee3e.js:45810:15892)
    at reducer (content-manager.4e46c41a.chunk.js:6728:32)
    at Object.fi [as useReducer] (main.e40cee3e.js:75945:451)
    at exports.useReducer (main.e40cee3e.js:86305:274)
    at EditViewDataManagerProvider (content-manager.4e46c41a.chunk.js:7052:56)
    at Xh (main.e40cee3e.js:75942:137)

Expected behavior

Expected to be able to use components in the zone :)

Screenshots

How the UI looks like before click:

How the ui looks when click on any of the components:

Code snippets

This is one example of the schema for one of the components:

{
  "collectionName": "components_landing_pages_big_numbers",
  "info": {
    "displayName": "Big Numbers",
    "description": "",
    "icon": "bold"
  },
  "options": {},
  "attributes": {
    "header": {
      "type": "text",
      "required": false
    },
    "items": {
      "type": "component",
      "repeatable": true,
      "max": 4,
      "min": 2,
      "component": "landing-pages.big-number-item"
    },
    "disclaimer": {
      "type": "text"
    },
    "backgroundColor": {
      "type": "enumeration",
      "enum": [
        "None",
        "Yellow",
        "Alpha"
      ],
      "default": "None"
    }
  }
}

My package json:

"dependencies": {
    "@strapi-community/strapi-provider-upload-google-cloud-storage": "^4.5.6",
    "@strapi/plugin-graphql": "4.11.0",
    "@strapi/plugin-i18n": "4.11.0",
    "@strapi/plugin-seo": "^1.9.1",
    "@strapi/plugin-users-permissions": "4.11.0",
    "@strapi/strapi": "4.11.0",
    "knex": "2.4.0",
    "pg": "8.5.1",
    "slugify": "^1.5.3",
    "strapi-plugin-duplicate-button": "^1.1.7",
    "styled-components": "^5.3.3"
  },

Let me know if I can provide any more context, thanks

[BorisKamp]

I have the same while I'm close to a deadline. Now I cannot enter my content, this is really urgent to fix guys!

Context from my side:

1. In only get the error when I try to select a component from the dynamic zone which has a nested component in it. Meaning I can select a component which only has a text field in it, but I cannot select a component which has a nested other component in it.
2. Downgrading does not fix the problem.
3. I have this locally and on my production server

[strapi-bot]

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

https://forum.strapi.io/t/breaking-new-error-ive-never-seen-did-the-last-version-cause-this/29148/3

[jastrand]

I have tested again and can also confirm that this is only happening for components with nested components.

[joshuaellis]

Thanks for the report everyone – this was an oversight, there's a PR to resolve this open now

[BorisKamp]

Okay, any ETA on the release that should fix this? Because I really need the fix asap (-:

[joshuaellis]

Okay, any ETA on the release that should fix this? Because I really need the fix asap (-:

The PR is open and the aim is 4.11.1 which we're hoping to release on Monday. That's all I can say for now. You could, if it's blocking you over the weekend use patch-package temporarily until the patch is released.