-
-
Notifications
You must be signed in to change notification settings - Fork 203
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
Error: Error: Validation (isSlug) failed for slug #75
Comments
@simhol Sorry to hear you are running into issues. This error is coming from your Ghost CMS (there is no
I also notice that you are building on Windows which is not officially supported (it means you are a bit on your own when it comes to debugging). I recommend using WSL 2 with Ubuntu when building on Windows. However, I don't think this is the issue here. |
I will try to unpublish posts or import/export them to identify the malicious content! |
Can you please open a new issue for this error as it looks unrelated? |
Before doing that, please make sure your Ghost instance is running on a recent version. Please also publish your software versions for OS, Ghost and npm/yarn here. You are getting many errors I have never seen before, so something is fundamentally wrong here. |
Closing as not reproducable. If you disagree, please link to a repository with a reproducable example and add some instructions to it. |
I've received this error on a fresh new project. Just cloned the starter and provided a .env.local file with the API_URL and _KEY to my Ghost instance.
I get the following error in my terminal when running this in my dev environment:
Error: Error: Validation (isSlug) failed for slug
at getPostBySlug (F:\Projects\tsc-blog.next\server\pages\index.js:4018:134)
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async getStaticProps (F:\Projects\tsc-blog.next\server\pages[...slug].js:10310:10)
at async renderToHTML (F:\Projects\tsc-blog\node_modules\next\dist\next-server\server\render.js:28:1737)
at async F:\Projects\tsc-blog\node_modules\next\dist\next-server\server\next-server.js:112:97
at async __wrapper (F:\Projects\tsc-blog\node_modules\next\dist\lib\coalesced-function.js:1:330)
at async DevServer.renderToHTMLWithComponents (F:\Projects\tsc-blog\node_modules\next\dist\next-server\server\next-server.js:137:387)
at async DevServer.renderToHTML (F:\Projects\tsc-blog\node_modules\next\dist\next-server\server\next-server.js:138:923)
at async DevServer.renderToHTML (F:\Projects\tsc-blog\node_modules\next\dist\server\next-dev-server.js:35:578)
at async DevServer.render (F:\Projects\tsc-blog\node_modules\next\dist\next-server\server\next-server.js:75:236)
at async Object.fn (F:\Projects\tsc-blog\node_modules\next\dist\next-server\server\next-server.js:59:580)
at async Router.execute (F:\Projects\tsc-blog\node_modules\next\dist\next-server\server\router.js:25:67)
at async DevServer.run (F:\Projects\tsc-blog\node_modules\next\dist\next-server\server\next-server.js:69:1042)
at async DevServer.handleRequest (F:\Projects\tsc-blog\node_modules\next\dist\next-server\server\next-server.js:34:504)
I've changed nothing in the original repo.
The text was updated successfully, but these errors were encountered: