-
Notifications
You must be signed in to change notification settings - Fork 329
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
RQ-Dashboard can no longer be integrated with Flask 2.3+ as a blueprint #417
Comments
Our team has run into the same issue. |
Any workarounds or alternatives someone have for this issue? |
+1 |
@mbhagdev I saw that you seem to have a fork of RQ Dashboard – does your fork fix this issue? |
My fork is also published on pypi as rq-dashboard-compatible |
Thanks @mbhagdev, confirmed that your fork works with flask==2.3.2! Our team has created a separate fork internally that branches off of the 0.6.1 tag with the same changes, since your fork is based on master which has a completely different and new (?) UI. |
+1 |
Traceback (most recent call last): |
This should now be fixed with the latest merge, please confirm |
I'm still getting the same error.
|
@AriefBadal23 did you compile it from the source or did you use the releases? we did not update the releases, just the source |
Oh I checked the released version, I will try the source then. |
@AriefBadal23 yes, the version has not been updated yet. we are working on automating this, will let you know once that automation if finalized, for now please use the source code |
This worked for me
|
@AriefBadal23 we have now the PyPi package updated, so you should be all fine. Update to the latest 0.6.6 |
Hello,
app.before_first_request
andblueprint.before_first_request
have been deprecated in Flask2.2.0
(pallets/flask#4605) and completely removed in version2.3.0
.Therefore it is no longer possible for projects using Flask
2.3.0
to integrate rq-dashboard directly as an application blueprint. An attempt to do so will produce anAttributeError: 'Blueprint' object has no attribute 'before_app_first_request'
.The text was updated successfully, but these errors were encountered: