Cannot find a descendant at path [6,0] in node ... Error

thedunco2 years ago

12

• 

  jmikrut

  2 years ago

  can you open a GitHub issue about this with as much detail as possible?

  
  
  

  the team will get on it

• 

  thedunco2 years ago

  Will do, thanks

  
  
  

  I'm having some trouble reproducing it consistently, but will speak to my team to see if they can get a video of it happening so I can write up the most detailed issue I can.

• 

  notchr2 years ago

  @408784184765710337

  I have an issue that may be related?

  
  
  

  So I have a Pages collection

  
  
  

  Which, I sort of regret creating as a single collection

  
  
  

  Because then each individual page you end up creating Blocks

  
  
  

  But I had the idea of a Slider Block, for a main page Slider (eww I know)

  
  
  

  Then I got smart and decided, this is going to be a CTA instead (yay)

  
  
  

  Well, I went and changed the name of the model in my source

  
  
  

  Then I went to add a new CTA and my admin panel crashes

  
  
  

  It's because there are remnants of an old Block type that weren't deleted

  
  
  

  and I didn't migrate first, but in this case, I shouldn't have had to really manage the migration

  
  
  

  Because it was such a simple change

• 

  thedunco2 years ago

  Oh, interesting. So you're saying it shouldn't be an issue with newly created ones which would be why I'm having a hard time reproducing it?

• 

  notchr2 years ago

  So say I accidentally noticed I wrote

  
  
  

  SilderBlock

  
  
  

  if i created an instance of a SilderBlock

  
  
  

  and then changed the collection name to SliderBlock

  
  
  

  it will crash on adding new data

• 

  thedunco2 years ago

  Mmm, yeah that might be related but I'm not sure that's the exact issue because I was seeing this when I drag/dropped the block, not when adding new data per say

• 

  notchr2 years ago

  I do think this kind of error should be handled by better error messaing

  
  
  

  but yeah, possibly related maybe not

• 

  thedunco2 years ago

  Thanks for your input though, I can check the document and see if there's any old data in there

• 

  notchr2 years ago

  I would like to see better migration documentation on the Payload site too hehe

  
  
  @1032341301619871785
  
  

  Only because I have no idea what to do about resolving this

  
  
  

  Without redefining the old model type

  
  
  
  
  

  :*(
• 

  thedunco2 years ago

  I asked about this in

  #967097582721572937

  yesterday and it sounds like there should be some examples in GitHub discussions (although I didn't have time to find any specific examples yesterday)

• 

  notchr2 years ago

  Hehe I saw that thread

  @408784184765710337

  , but this kind of information NEEDS to be on the Payload site

  
  
  

  It's a crucial time for Payload to appeal to devs

  
  
  

  And detailed documentation is how to appeal to devs

• 

  thedunco2 years ago

  I was able to consistently reproduce this. I'll open an actual github issue with more info after lunch but just for context it's still happening on payload v1.16.17

  
  
  

  I've opened the github issue here

  https://github.com/payloadcms/payload/issues/2272