Our upgrade journey begins at Wagtail 2.5.
You will want to bookmark this one particular documentation page:
https://docs.wagtail.org/en/stable/releases/upgrading.html
Also note that I am starting with:
Along the way we will upgrade Django and Python, as well.
Kickstarting the Upgrade from Wagtail 2.5
Upgrading your Wagtail setup is more than just stepping up numbers—it's a perfect chance to tidy up your project! As you embark on this journey from Wagtail 2.5, here are a few things you should consider doing first:
When it comes to actually upgrading Wagtail, you've got a couple of options:
I personally lean towards the second option—waiting until all upgrades are complete before diving into unit testing. It feels more efficient as it prevents you from getting stuck on the same issues repeatedly. However, choose the path that best suits your workflow and team dynamics.
Note: This is a GREAT time to reduce package use that Wagtail supports. For instance you can remove the wagtail-livepreview package in favour of Wagtail's built in live-preview feature.
Your first major stop is Wagtail 2.7 LTS. It’s important to note that this version still plays nicely with Django 2.2, keeping things smooth compatibility-wise.
🚀 Launch Check: Before moving beyond Wagtail 2.7 LTS, make sure to do a basic functionality test. Running python manage.py runserver 0.0.0.0:8000
should work without a hitch. Ensuring everything operates correctly at this stage sets a solid foundation for further upgrades.
In the next article, we will install Wagtail 2.7. Thats our first upgrade step.
Wagtail CMS enthusiast; Wagtail core team member; Coding teacher.