Site in constant loading screen

[abbensch]

Hi all,
I've finally finished (I think) all the steps for my repository, devkit, and csv, but my site is stuck loading my objects. I've tried editing where its fetching the metadata from, both from the live google sheets and via a .csv in github. I've also gone through my metadata to make sure it fits the layout, though I guess I could still be missing an error. I'm not sure where I've gone wrong and haven't found any other info on this issue.

Any help would be great! I'm not a coder just a historian :,( ty!!
site link: [https://abbensch.github.io/bellevue-boro-collection/]

[mohammadrezwankhan]

Good news: your metadata itself is not what is keeping the site on the loading screen. The configured URL is.

Your deployed page is currently trying to download:

https://abbensch.github.io/bellevue-boro-collection/_data/bellevue_boro_collection.csv

That URL returns 404. In this Pages build, _data is input to Jekyll, not a published browser-accessible directory. CollectionBuilder adds the “Loading...” spinner before Papa Parse fetches the CSV, and its error callback only logs to the console, so a 404 leaves the spinner visible forever.

Your current CSV is healthy: I loaded it with the same papaparse.min.js shipped in your repository and got:

12 items
12 unique, non-empty objectid values
0 parse errors

The smallest permanent fix is to edit _config.yml and replace:

metadata-csv: "/_data/bellevue_boro_collection.csv"

with the raw GitHub URL:

metadata-csv: "https://raw.githubusercontent.com/abbensch/bellevue-boro-collection/main/_data/bellevue_boro_collection.csv"

I verified that exact raw URL currently returns HTTP 200 and allows browser access.

Alternatively, if you prefer a local site asset:

1. move _data/bellevue_boro_collection.csv to assets/bellevue_boro_collection.csv; and
2. set:

metadata-csv: "/assets/bellevue_boro_collection.csv"

Use one approach, not both. Your own CollectionBuilder copy documents these same two supported patterns: a raw GitHub URL, or a CSV inside assets/.

You can test the raw URL before changing anything by opening this in a new/private browser tab:

Test Bellevue metadata through CollectionBuilder

The private/fresh tab matters because your site has development-mode: true. Change Metadata stores its last URL in sessionStorage, and parsed items are cached there too; both take precedence over the newly built _config.yml value in the existing tab.

After committing the _config.yml change:

1. wait for the GitHub Pages deployment to finish;
2. close the existing site tab and reopen the site in a fresh/private tab;
3. confirm the metadata request is 200 rather than 404.

If you want to clear the current tab instead, open its developer console and run:

sessionStorage.removeItem("cb_metadata_set");
sessionStorage.removeItem("cb_items_store");
location.reload();

So you do not need to rebuild the CSV or change its columns. Fix the metadata-csv URL, let Pages redeploy, and clear the tab's old session metadata; that directly removes the request failure causing the endless loader.

[abbensch]

OMGGGG thank you so much. Much appreciated 👍