craftcms / craftcms/cms

[4.x]: CRaft 4 upgrade

Open
#17,965 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug craft4
Dominant language
PHP
Stars
3.6k
Forks
705
Avg merge
1d 5h
Merged PRs (30d)
134

Description

What happened?
Description

I’ve tried and some other devs ~10 times to upgrade a large Craft 4 multi-site to Craft 5.
During the upgrade Craft triggers a resave of all entries. Our install reports ~30M entries across sites, and the process keeps dying (connection gets dropped). The longest run made it ~16 hours before failing.

Is there a supported way to defer the upgrade-triggered resave to the queue instead of doing it inline or other you have advice ?

Craft CMS version

4.x

PHP version

No response

Operating system and version

No response

Database type and version

No response

Image driver and version

No response

Installed plugins and versions

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by investigating the Craft 4-to-5 upgrade path and how the upgrade-triggered resave handles large multi-site installations, then determine whether queue-based deferral is supported. Done means a documented, supported approach or a clearly scoped implementation plan for avoiding the failing inline resave.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.