Replies: 1 comment
|
That screen is Next.js's production fallback, so it unfortunately hides the real exception; it does not by itself mean the GitHub connection failed. The quickest split is: can Pages CMS still open a different repository?
For the one-repository case, malformed YAML/front matter is the leading suspect. The same exact screen was reported in issue #378; the maintainer found invalid multiline YAML, and noted that Pages CMS 2.0's parsing had become stricter. Current Pages CMS parses collection content through In particular, this is invalid YAML: description: first line
second lineUse a block scalar instead: description: >-
first line
second lineI would check the last commit made before this started, then validate:
A fast way to isolate it is to temporarily restore the last known-good commit (or remove half of the newly added/edited entries), reload Pages CMS, and bisect the changed files. Reinstalling the app will not fix malformed repository content. If other repos work and all YAML validates, add the repository URL, branch, the exact page/path that triggers it, the last known-good commit, and the error's |
Uh oh!
There was an error while loading. Please reload this page.
never had this happen before. know what the issue is?

All reactions