search

Charcoal-SE / charcoal-se.github.io

Website for Charcoal
https://charcoal-se.org/
8 stars 27 forks source link

Search is broken #56

Closed tripleee closed 4 years ago

tripleee commented 5 years ago

Since at least this weekend, I am unable to obtain any search results on https://charcoal-se.org/

If I type in a search term in the magnifying glass in the upper right corner, I see the following messages in my JavaScript console:

(index):1 Unchecked runtime.lastError: The message port closed before a response was received.
box-90f3a29ef7448451db5af955688970d7.html:1 Unchecked runtime.lastError: The message port closed before a response was received.
search-by-algolia.svg:1 Failed to load resource: the server responded with a status of 404 ()
j-f1 commented 5 years ago

Confirmed fixed ✅

tripleee commented 5 years ago

@j-f1 Thanks for the quick fix, but I still don't see search results other than sporadically.

For example, right now, typing "blacklist" into the search box behind the magnifying glass in the top-right corner at https://charcoal-se.org/ gets me nothing, just silence. (Typing "ping" into the search box does get me something, though it seems constrained to a single post, where there should be more than one.)

The JavaScript console still gets the first two of the original three errors (where I guess the one which disappeared, about access to the SVG image, was the least crucial anyway).

tripleee commented 5 years ago

I am again unable to obtain any search results on the site.

Edit: Actually "ping" still works, but no other terms I tried bring meaningful results, including "charcoal", "blacklist", "request", "smokedetector", and "autoflagging". Incredibly, "spam" only gets me a single result.

tripleee commented 4 years ago

Again, or still? Not able to get any results as of right now.

I don't see anything useful at all in the JavaScript console.

j-f1 commented 4 years ago

It seems like the Algolia access token doesn’t have enough permissions. I’m currently re-running the latest build to see if the new permission I added helps.

j-f1 commented 4 years ago

cc @iBug why is the site build run twice (once on Actions, once on Travis)?

j-f1 commented 4 years ago

This should be fixed.

iBug commented 4 years ago

cc @iBug why is the site build run twice (once on Actions, once on Travis)?

I originally wanted to migrate our site build from Travis to GH Actions and its in a partial state now. I suspended work on it after discovering that manually triggered Action builds can't use existing caches.