Depth param not working with global

jm.sv2 years ago

10

• 

  jarrod_not_jared

  2 years ago

  This tells me that you are making a request and access control is returning false for that collection on those docs

• 

  jm.sv2 years ago

  @281120856527077378

  both my Home global and Projects collection have

  access: { read: () => true }

  . Would there be another config / another area I need to explicitly allow access?
• 

  jarrod_not_jared

  2 years ago

  @722129234474303508

  I just tried to recreate your issue as you described, and was unable to. If you can recreate it inside the

  test/_community

  folder and open an issue on github that would be great!

• 

  notchr2 years ago

  I wonder if this is due to the kind of relationship set?

• 

  jarrod_not_jared

  2 years ago

  Whaddya mean? I set up a relationship just like

  @722129234474303508

  had and then used a global, with a group, with a relationship field inside of it (with the same field config settings)

• 

  notchr2 years ago

  Yeah good point

  @281120856527077378

  - maybe an older payload vers on their end?

  
  
  

  I cant replicate either

• 

  jarrod_not_jared

  2 years ago

  yeah possibly old payload, would like to know what version they are on

• 

  notchr2 years ago

  Probably a coincidence, but someone just made a support post with a similar issue on payload latest, not exact but similar-ish

• 

  jm.sv2 years ago

  @281120856527077378

  @1049775120559898725

  this was a silly mistake, I must have had an old legacy field called

  projects

  on

  Home

  that was populated so it was still returning from the API even though it's no longer part of the schema. I was confusing that for my

  projectsSection.projects

  that I just confirmed is working correctly. Will do some digging to see best practice for handling stale data / fields stuck inside the database. Thank you both for your help!

• 

  jarrod_not_jared

  2 years ago

  Nice! No problem 🙂