Unable to find node on an unmounted component

badjab3262 years ago

13

• 

  paulpopus2 years ago

  @201094837066399744

  whats your collection config? does it happen on all of them or just this one?

• 

  jessrynkar2 years ago

  @201094837066399744

  - could you share the exact field that is causing this issue? I have tried to replicate with a simple select field and a relationship field but not able to reproduce this error.

• 

  badjab3262 years ago

  const Questions = {
    slug: 'questions',
    admin: {
      defaultColumns: [
        'question',
        'label',
        'description',
        'answerType',
        'answerChoices',
        'prevVersion',
        'isDeleted',
        'isUpdated',
      ],
      useAsTitle: 'name',
    },
    access: {
      read: () => true,
    },
    fields: [
      {
        name: 'question',
        type: 'text',
        required: true,
      },
      {
        name: 'label',
        type: 'text',
        required: true,
      },
      {
        name: 'description',
        type: 'text',
        required: true,
      },
      // TODO: SHOW ANSWER CHOICES ONLY FOR MULTIPLE CHOICE ANSWER TYPE
      {
        name: 'answerType',
        type: 'radio',
        options: [
          {
            value: 'multipleChoice',
            label: 'Multiple Choice',
          },
          {
            value: 'simpleText',
            label: 'Simple Text',
          },
          {
            value: 'fileUrl',
            label: 'File URL',
          },
        ],
        defaultValue: 'simpleText',
      },
      {
        name: 'answerChoices',
        type: 'array',
        fields: [
          {
            name: 'answerChoices',
            type: 'text',
          },
        ],
      },
      {
        name: 'regulations',
        type: 'relationship',
        relationTo: 'regulations',
      },
      {
        name: 'prevVersion',
        type: 'array',
        fields: [
          {
            name: 'prevVersion',
            type: 'relationship',
            relationTo: 'questions',
          },
        ],
      },
      {
        name: 'isDeleted',
        type: 'checkbox',
        defaultValue: false,
      },
      {
        name: 'isUpdated',
        type: 'checkbox',
        defaultValue: false,
      },
    ],
    timestamps: true,
  }
  
  export default Questions

  
  
  

  It happens in all collections, whether there's data already in the database or we start completely fresh.

  
  
  

  here are two examples of fields breaking the UI.

  
  
  

  {
        name: 'regulations',
        type: 'relationship',
        relationTo: 'regulations',
      },

  
  

  I've modified the next item from the full collection above. Using radio was the workaround fix for this item, but relationship seems to require the same assets for the dropdown menu.

  
  

  {
        name: 'answerType',
        type: 'select',
        options: [
          {
            value: 'multipleChoice',
            label: 'Multiple Choice',
          },
          {
            value: 'simpleText',
            label: 'Simple Text',
          },
          {
            value: 'fileUrl',
            label: 'File URL',
          },
        ],

• 

  jessrynkar2 years ago

  @201094837066399744

  thank you for the examples - I've used the exact same fields but am not getting your error. I definitely want to figure out why this is happening for you. What version of payload are you on?

• 

  badjab3262 years ago

  @854377910689202256

  Thanks! We are using 1.6.15 currently. I also haven't had this issue with any of my other Payload projects (I have around 3 others to date) but this one is the only in which I'm adding Payload to an existing backend, rather than starting from the template.

• 

  paulpopus2 years ago

  you are a bit out of date, try

  yarn upgrade

  ?

• 

  jarrod_not_jared

  2 years ago

  @201094837066399744

  This happens on the

  create

  view? or the

  edit

  view?

• 

  badjab3262 years ago

  Just gave that a shot, no dice unfortunately.

  
  
  

  Tested both and received the same result.

• 

  paulpopus2 years ago

  Definitely not reproducible 😅

  
  
  

  I'm adding Payload to an existing backend
  

  do you think you could recreate this in a repo you can share?

  
  
  

  or share this one without any private info

• 

  badjab3262 years ago

  Actually we figured it out! We needed to add 'react-select' to the overrides, thanks for all the help!

• 

  markhor.2 years ago

  @854377910689202256

  We tried to override react-select's version with the latest v5.7 in our package.json and that fixed the crash. Any particular reason why that might be happening?

• 

  jessrynkar2 years ago

  @201094837066399744

  @182597927133249536

  nice! What version of react-select did it show previously?

• 

  markhor.2 years ago

  I didn't check inside payload's package json what version was installed currently but on your github it says v3