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

Craft 5 upgrade instruction tweaks #682

Merged
merged 1 commit into from
Jan 23, 2025
Merged

Conversation

brandonkelly
Copy link
Member

  • Adds a step to run utils/fix-field-layout-uids (since Craft 5 will make you go back to v4 and run it, if there are any duplicate UUIDs within field layout configs, so might as well do it up front just in case).
  • Adds a step to deploy project config changes as a result of project-config/rebuild or utils/fix-field-layout-uids (see [5.x]: Craft 5 upgrade error: A field layout element is missing its UUID cms#16411 (comment)).
  • Removes the step about making a local DB backup. Shouldn’t be necessary because the local backup is basically going to be the same as the production backup you already created (plus any automated project config changes).

@brandonkelly brandonkelly requested a review from a team as a code owner January 20, 2025 15:57
Copy link

netlify bot commented Jan 20, 2025

Deploy Preview for craft-docs ready!

Name Link
🔨 Latest commit 1ffaa2f
🔍 Latest deploy log https://app.netlify.com/sites/craft-docs/deploys/678e725aa0e3c700088e1e07
😎 Deploy Preview https://deploy-preview-682--craft-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@AugustMiller AugustMiller merged commit bfdde73 into main Jan 23, 2025
6 checks passed
@AugustMiller AugustMiller deleted the craft-5-upgrade-tweaks branch January 23, 2025 17:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants