Triggering changes on documents after Custom Type change

Prismic for Content Creators
1

Hey @Phil, I am continuing to experience this problem.

image
image951×443 14.7 KB

image
image797×120 3.82 KB

image

Is there any way of forcing boolean fields to take their default value across a repository?

3

Hi @ben7,

Is this a field you've just added or modified? Changes won't appear across your repository on their own. You'd need to do a republish the documents with that field for it to "update".

5

Thanks Ezekiel.

Is there any way to republish all published pages in a repository?

6

Hi Ben.

Thanks for raising this! At the moment, making a change to a Custom Type (like updating a Slice or field config) doesn’t automatically revalidate or update existing documents that use that Custom Type, they’ll remain as they were until individually edited and saved.

A couple of things you can try:

  • Manual trigger: Open and re-save each document to apply the changes.
  • Migration API: Use the Migration API to script updates across documents, even a no-op change (like setting a field to its current value) can trigger revalidation and apply the updated schema.