andylarkum

Good question. Disappointingly, I've tried rolling my site back (git) to the last good version, but I get the same content error. Without rebuilding the site, I can't give you...

No - am using the standard laravel .gitignore - but I have that content because I pushed it (to S3). Rebuild will be quick, but annoying, and I certainly don't...

Full process I've been using: `php please ssg:generate --workers=4 && npm install && npm run production` `cd storage/app/static` `aws s3 sync . s3://my_site_s3_bucket` S3 hosts the static site behind Cloudfront.

OK, so happily simply running: `php please cache:clear` ...brought the pages back (see: https://benfurfie.co.uk/articles/how-to-fix-the-call-to-a-member-function-selectedquerycolumns-on-null-error-in-statamic-3) Having got the content back, I did some tidying up to fix some bits I wanted...

FWIW (and in case anyone else stumbles across this issue), for me, running `php please cache:clear` ...before AND after running `php please ssg:generate` ...solved the problem.

For now, to work around, I've done this (in case it helps others): In layouts.antlers.html: Remove Antlers: `{{ vite src=“resources/js/app.js|resources/css/app.css” }` Add HTML: ` ` `` ``