I don't see my previous collections after adding in versions

nh02.2 years ago

6

access: {
    read: () => {
      if (isLoggedIn) {
        return true;
      }

      return {
        or: [
          {
            _status: {
              equals: 'published',
            },
          },
          {
            _status: {
              exists: false,
            },
          },
        ],
      };
    },
  },
  versions: {
    drafts: true,
  },

• 

  dribbens

  2 years ago

  What happens is the list is populated from querying from _collectionname_versions, a separate collection from the main when versions are enabled. To fix it, every document that existed before versions was enabled needs to be resaved.

  
  

  There is a script in the changelog that resaves all documents in a collection. It could also be done using a PATCH request for the entire collection.

  
  
  

  PATCH

  
  

  /api/pageType?where[id][exists]=true

  
  

  body: {_status: 'draft'}

  
  

  headers: {

  
  

  content-type: application/json

  
  

  authorization: JWT TOKENFROMCOOKIE

  
  

  }

  
  
  

  Sorry for the psuedocode, I'm on mobile. I hope this gives you an idea on what to do.

  
  

  This is something we need to document better.

• 

  nh02.2 years ago

  Cool! Thanks for the quick response!

• 

  xgzeptolast year

  Hey, just asking if adding _status solves your issue; I tried adding this directly to the database and the problem persists 😢

• 

  yageeelast year

  Can you share the script for resave all documents in a collection, please?

  
  
  

  btw, thanks for the PATCH example, works well!

• 

  nh02.last year

  Apologies for the late response. If it's still relevavant to you, adding _status wasn't the way to go, but instead running the migrateVersions script available on payloads github repo.

• 

  xgzeptolast year

  thx for the reply 🫡 problem solved