404 Not Found after upgrade to 2.3

[danielcwj16]

Just upgraded to 2.3. Then cannot open graphql site anymore. It shows graphiql.js file not found.

#683 looks similar to my issue, but I can't pull up the site with what @brandonmbanks did.

[phalt]

Have you ran python manage.py collectstatic ?

[shoof1072]

Could this be related to #508?

Our project pulled in 2.3.0 and we observed the same 404, both FF and Chrome render a blank page at the /graphql/ path, and observed the following printed to our service log:

WARNING:django.request:Not Found: /static/graphene_django/graphiql.js

We've rolled back and pinned to 2.2.0 for now.

[danielcwj16]

Have you ran python manage.py collectstatic ?

I tried this and it created a static folder with that graphene_django/graphiql.js in it. But still can not open the page, console gave the same error message.

[phalt]

We've just pushed out 2.3.2, can you check this is still occurring in that version? I am running 2.3 locally on my machine and I'm having no issues.

[danielcwj16]

We've just pushed out 2.3.2, can you check this is still occurring in that version? I am running 2.3 locally on my machine and I'm having no issues.

Still not works

[jkimbo]

@danielcwj16 have you added graphene_django to your INSTALLED_APPS list in settings.py? django.contrib.staticfiles also needs to be in that list.

[evanheckert]

@jkimbo I have both of those in place, and have run collectstatic and am experiencing the same issue. Rollback to 2.2 solves it for now.

[jkimbo]

@evanheckert can you share your static file settings in settings.py? Or even better if you could create a reproduction of the issue that would be very helpful.

[dacevedo12]

@jkimbo We're experiencing the same problem. Here's what our static settings look like

It works in the local development server but then fails after the app is deployed and served through wsgi

[jkimbo]

@dacevedo12 can you create a full reproduction of the issue (as a github repo)? I can't reproduce the problem.

[jkimbo]

Actually @dacevedo12 I think you need os.path.join(PROJECT_ROOT, "static"), in your STATICFILES_DIRS setting and you need to make sure you run manage.py collectstatic as part of your deployment process.

[Ouradze]

This is still present in 2.5 :) You can reproduce it with https://gitlab.com/eclar/django_deploy but only with the production image.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[evanheckert]

This is still present in 2.5 :) You can reproduce it with https://gitlab.com/eclar/django_deploy but only with the production image.

Still an issue.

[mmitsui]

Has anyone tried updating urls.py as per the Django docs on static files (Serving static files during development)? This seemed to resolve the issue for me.

[evanheckert]

@mmitsui Yes, of course.

# urls.py
from django.conf import settings
from django.conf.urls.static import static
from django.contrib import admin
from django.urls import path
from django.views.decorators.csrf import csrf_exempt

from graphene_django.views import GraphQLView

urlpatterns = [
    path("__admin/", admin.site.urls), 
    path("gqlendpoint/", csrf_exempt(GraphQLView.as_view(graphiql=True)))
] + static(settings.STATIC_URL, document_root=settings.STATIC_ROOT)

And..

# settings.py
import os
...
...
STATIC_URL = "/static/"
BASE_DIR = os.path.dirname(os.path.dirname(os.path.abspath(__file__)))
STATIC_ROOT = os.path.join(BASE_DIR, "static/")

[jkimbo]

@evanheckert @Ouradze @dacevedo12 when running Django with DEBUG=False it will not host static files for you (ref). You will need to run a server to host the static assets or use something like whitenoise to get the python process to host them. Once you have that setup it should work fine.

The reason this changed in v2.3 is that we moved the graphiql javascript bundle into a separate file: #508