Reloading a language or topic page results in 404 about verto HOT 15 CLOSED

@thebarshablog I rechecked the language-specific and topic-specific pages and they are responding 404 on page refresh.

from verto.

Sorry for taking so long to answer. It worked, thank you :)

from verto.

Hey, not sure if anyone was still working on this, but I've put up a PR with a (hopefully) working solution to this issue :)

from verto.

Hey @lucavallin I tried loading several language-specific and topic-specific pages, as of present moment, it doesn't lead to a 404 error page but successful directs to the respective github repositories. Should this issue still be open?

from verto.

Hey @thebarshablog, it does lead to 404. Try [https://firstissue.dev/language/javascript/]

from verto.

In such a case, @romeshkosme, the issue should be renamed/specifics must be added. It's a happenstance under JavaScript whereas when I'm selecting based on other mentioned languages, its working just as fine. Please recheck again and confirm.

from verto.

Hey @lucavallin If nobody has picked it up, I would like to pick this one.

from verto.

@romeshkosme Yep, feel free to work on this!

from verto.

Hello, is this bug still existing?

from verto.

@JeniferConstantino It is! There has been an attempt, see #68. Unfortunately the fix there won't work for us.

from verto.

Hello, thank you for answering :).

I would like to work on this issue but the problem is that I'm not being able to simulate the bug. I launched on development mode (npm run dev). When I launched, it took me to the website:

As said in the issue description, I went to a language-specific page and chose to browse by the language of "JavaScript", for example. Then I reload the page by clicking on F5 (or refreshing the link). By doing this I was expecting the error to show up, instead, everything happens as I think it should:

Am I doing something wrong?

from verto.

@JeniferConstantino Yes, that works in dev. The problem is that in production the app is exported as a static site, and that's where it breaks. You can try and reproduce it locally by building the website and then running npm run export. If you open the exported site (which is static) you should be able to reproduce it. Googling for next js static site reload 404 brought me here: https://nextjs.org/docs/basic-features/data-fetching/get-static-props. Maybe a possible solution.

from verto.

Thank you, I'm seeing if I can solve the bug :)

from verto.

Hello.

Problem: I'm having authorization issues on the Octokit API. After doing "npm build run" it returns 403 because of credentials.

Explanation:

I've been trying to make "npm run export", but before doing this I have to make "npm run build". When executing this command I get the following:

And after waiting some time it retrieves me this:

The code that is being executed is the following:

With this being said, I conclude that the error occurs because I excited the number of requests to the API being used (60 requests as pointed out on the curl in the second image). I've read in here: https://docs.github.com/en/rest/overview/resources-in-the-rest-api?apiVersion=2022-11-28#rate-limiting that the number of requests can increase if I'm logged in GitHub. I've created a token, but now I'm not sure how can I log in to GitHub so that the API detects it.

Thank you in advance.

from verto.

Hello! Ah yes, that's expected when running npm run build locally. We had a flag in place to avoid this but it seems it has been removed. Anyway, that happens because when you build the app, we get the data from GitHub to display it on the website. It's 1300 repositories and it goes through the API call quota quickly. What you can do for now is to remove the prebuild script from package.json so it is not called before a build runs. In this way, the app will use the generated.json data example that comes with the repo. Let me know if this works!

from verto.