-
Notifications
You must be signed in to change notification settings - Fork 68
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
Upgrade to Wagtail 6.3 #478
Conversation
We worked on this branch live during Wagtail office hours tonight. @vossisboss tried this branch with a copy of the database but we are seeing some errors with the image block changes. It's likely this has something to do with the django-pattern-library package we are using however. If not, we should get a bug report going... |
@vossisboss @cnk I have raised wagtail/wagtail#12514 for the ImageBlock crash we were seeing yesterday. |
05f4f2f
to
2bac61d
Compare
I've amended my commits to use the 6.3.0 final Wagtail release |
I'll pull and review this some time after lunch @Stormheg |
Hrm. Something's up here @Stormheg. Let me see if I can figure out what's going on... Looks like the NoneType error is still there according to my local build. |
Interesting, that looks similar to wagtail/wagtail#12514 that was fixed in wagtail/wagtail#12517. Maybe there's a different case that's not handled yet? I wonder what the traceback says. |
@laymonage Here's the trace from my local copy. I'm checking Sentry to see if the staging one is any different. I've confirmed that Wagtail 6.3 is definitely installed.
|
Sentry provided some more information. I don't think you have a Sentry account @laymonage? I would send you that trace too otherwise. |
This appears to be an issue specific to the Wagtail.org homepage (at least in my cursory testing). I tried reverting ImageBlocks to ImageChooserBlocks and the problem block appears to be TeaserBlock from core/blocks.py. I didn't get any further but reverting |
We opened wagtail/wagtail#12571 tonight that attempts to fix the |
The `alternative_text` field has been unused for a long while now. We have determined from a production database copy that there is a handful of images that has useful content in that field worth keeping.
6.8 has some pretty cool performance improvements to `collectstatic`!
adc40d2
to
02ce66c
Compare
I have added a commit that copies the content from The commit that migrates our use of ImageChooserBlocks to ImageBlocks has been extracted to #480 and removed from this PR. There isn't currently a gradual way of adopting contextual alt text, forcing editors to add it to existing images before they can successfully edit a page. We determined we are not ready for that. With these changes in place, I think this can be considered ready for review and merge. @vossisboss is there a way to restore a database backup of staging from before we deployed this branch? My removal of the ImageChooserBlock to ImageBlock commit from this branch will cause issues if you try to deploy this branch again, as I have removed the migration files. The removal of those files will make the database very unhappy. |
@@ -13,8 +13,8 @@ build-backend = "poetry.core.masonry.api" | |||
|
|||
[tool.poetry.dependencies] | |||
python = "^3.12" | |||
django = "~5.0.6" | |||
wagtail = "~6.2.2" | |||
django = "~5.0.9" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why not
django = "~5.0.9" | |
django = "~5.1.4" |
as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@zerolab that is blocked waiting on a new release of https://github.com/torchbox/django-pattern-library
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
argh, I keep forgetting about it.
one workaround is to build it locally and bundle the wheel with the repo, but that is not worth it. One for a follow up PR
@Stormheg, I'm not sure what the best way to roll back our staging database would be. That's a new one for me. I think my first inclination would be to check the Heroku dashboard and see if there's a backup restore option there. I need to write the newsletter and do some other stuff before I look into that. |
We tested this on staging and it looks good. There is one minor issue with uploading profile pictures, the uploaded pictures aren't accessible and result in a 403 error from AWS S3. We lodged in ticket with the Torchbox sysadmin team for them to check it out as it is likely a misconfiguration and not an issue with this upgrade. |
collectstatic
!)alternative_text
field, use the newdescription
field from Wagtail 6.3 instead.