-
-
Notifications
You must be signed in to change notification settings - Fork 483
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
<asgiref.local.Local object at 0xffff8cab4f90> object has no attribute 'request' #1279
Comments
We encountered the same error this week. We use Wagtail 5.2 and django-simple-history in a project. After upgrading to django-simple-history 3.4.0 we encountered this error when attempting to preview a Wagtail page while editing the page. We do not encounter this error if we revert to django-simple-history 3.3.0. |
I'm seeing the same issue here. Works fine with 3.3.* but fails as described with 3.4.0. |
Previously the middleware made this check before deleting the request property from context, but with the refactor done in 3.4.0 it's gone
|
Hi, I'm the maintainer of Django Check SEO. I tried to re-add the |
Closed by #1256 |
I'm not sure if this is a django-check-seo issue or a django-simple-history issue. But if I enable the middleware of django-simple-history, it breaks django-check-seo (so I'm posting it in both) . Either work fine independently but not together so there seems to be a conflict somewhere.
To reproduce the bug, install both apps, and then use django-check-seo. Here's the traceback:
The text was updated successfully, but these errors were encountered: