You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On tutorial pages, clicking "Solve" button on bottom left updates the code to display the "solution" to the tutorial problem. In addition, it appends the ?solved query string to the URL: e.g. https://www.solidjs.com/tutorial/introduction_basics?solved.
When users try to reach the solution directly using the URL, however, the server returns 500 response with the following payload:
"could not find tutorial/introduction_basics/index.html in your content namespace"
After trying with multiple browsers, I noticed that the problem goes away once the solid site is cached. This, however, can still be an issue when the URL with ?solved is shared to someone who has never visited the site before or uses a browser that automatically clears all cached files. E.g. I use Firefox on the "Always use private browsing mode" as my main browser, and see the 500 response every time I try a tutorial page URL with ?solved.
The text was updated successfully, but these errors were encountered:
On tutorial pages, clicking "Solve" button on bottom left updates the code to display the "solution" to the tutorial problem. In addition, it appends the
?solved
query string to the URL: e.g.https://www.solidjs.com/tutorial/introduction_basics?solved
.When users try to reach the solution directly using the URL, however, the server returns 500 response with the following payload:
After trying with multiple browsers, I noticed that the problem goes away once the solid site is cached. This, however, can still be an issue when the URL with
?solved
is shared to someone who has never visited the site before or uses a browser that automatically clears all cached files. E.g. I use Firefox on the "Always use private browsing mode" as my main browser, and see the 500 response every time I try a tutorial page URL with?solved
.The text was updated successfully, but these errors were encountered: