Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

404 on team page #40

Open
Happy-Ferret opened this issue Mar 14, 2017 · 1 comment
Open

404 on team page #40

Happy-Ferret opened this issue Mar 14, 2017 · 1 comment
Labels
bug Something isn't working hacktoberfest Hacktoberfest help wanted Extra attention is needed

Comments

@Happy-Ferret
Copy link

Happy-Ferret commented Mar 14, 2017

On the initial load, the team page returns the following error (tested with Chrome and its default JS console).

GET https://liri.io/team/%7B%7B%20member.image%20%7D%7D 404 ()

%7B%7B%20member.image%20%7D%7D Failed to load resource: the server responded with a status of 404 ()

The error itself apparently relates to one deferred JS function in the generated HTML.

It doesn't break the site but it appears to slow it down ever so slightly.

PS: Any way to get the team page working in a development environment?
I'm still a Jekyll newbie and have yet to figure out what the "API" bit in team.js is referring to (and why there's a reference to port 8080 in there). However, it's the only page that doesn't appear to even load on localhost.

@plfiorini plfiorini added the bug Something isn't working label Apr 25, 2017
@plfiorini
Copy link
Member

Since the web site is static (with all its advantages) we made the server-side bits with Go: https://github.com/lirios/
The website executable listen to port 8080

@plfiorini plfiorini added hacktoberfest Hacktoberfest help wanted Extra attention is needed labels Sep 28, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working hacktoberfest Hacktoberfest help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants