Skip to content
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 5.x #1542

Closed
mwvolo opened this issue Jan 9, 2024 · 7 comments · Fixed by #1539
Closed

Upgrade to Wagtail 5.x #1542

mwvolo opened this issue Jan 9, 2024 · 7 comments · Fixed by #1539
Assignees
Labels

Comments

@mwvolo
Copy link
Member

mwvolo commented Jan 9, 2024

Andy and Dominique met with me asking about upgrading to Wagtail 5+, seeing some new feature that would be useful to them around image and document management. (probably this)

The following release notes are related:
https://docs.wagtail.org/en/stable/releases/5.0.html
https://docs.wagtail.org/en/stable/releases/5.1.html
https://docs.wagtail.org/en/stable/releases/5.2.html

This will likely encompass moving to 5.2, as it is a LTS release (receives support for at least 12 months).

Not related but barring a better place to put these, notes from the conversation with AM/DS on 12/18)

  • Wagtail upgrade (Michael will attempt but is unable to promise by Q1; will work with Marvin and team on future upgrade plans)
  • Content cleanup (mostly manual - consult with Content team on naming convention)
  • Dynamic page content — work up a plan and talk with Roy
  • Website search (across REX and OSWeb)
  • Possible high-priority request: India-specific sponsorship of pages, possible need to target ads based on user location
  • If user location becomes available, target Amazon ads based on it.
@mwvolo mwvolo self-assigned this Jan 9, 2024
@mwvolo mwvolo added the maint label Jan 9, 2024
@mwvolo mwvolo linked a pull request Jan 9, 2024 that will close this issue
@erikayvonne
Copy link

erikayvonne commented Jan 16, 2024

this can go on qa first w/o January 22 - and then on dev after Roy is done with 1/24 release
aiming for upgrade to be between February 7 and 21 releases (accounts release takes priority over this)
cc @mwvolo @brittanyearly

@erikayvonne
Copy link

@yblock to check this out on QA before it goes on dev

targeting w/o Feb 12, unless accounts release spills over

@yblock
Copy link
Contributor

yblock commented Jan 23, 2024

The only thing I see that isn't working is the "usage count" feature on documents to show where and how often a document is used. Not sure if that's expected to be working but it would be nice.

Screenshot 2024-01-23 at 11 00 26 AM

@mwvolo
Copy link
Member Author

mwvolo commented Jan 23, 2024

@yblock Is this a regression or it never worked?

@yblock
Copy link
Contributor

yblock commented Jan 23, 2024

Regression, it only started working recently and is currently working on prod.

@mwvolo
Copy link
Member Author

mwvolo commented Jan 25, 2024

I changed the A&P book cover on the book, which updated the usage to 1.
I think it might be that the documents you looked at were actually not in use?

Image

If you could try to attach a document to a page and verify this is working, that'd be great!

@yblock
Copy link
Contributor

yblock commented Jan 25, 2024

I checked many, and confirmed in the same way you did that it wasn't working. But, checking now it looks like it is working. Maybe a caching issue on my end or indexing taking time, I don't know. But it looks good now! 👍

@brittanyearly brittanyearly added this to the February 14 '24 milestone Jan 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants