Add documentation for sulu 2->3 update#916
Open
Prokyonn wants to merge 4 commits into
Open
Conversation
Prokyonn
force-pushed
the
enhancement/sulu-2-3-upgrade
branch
from
05029e8 to
4955087
Compare
Prokyonn
force-pushed
the
enhancement/sulu-2-3-upgrade
branch
from
022e573 to
6330393
Compare
Prokyonn
force-pushed
the
enhancement/sulu-2-3-upgrade
branch
from
6330393 to
cc9f090
Compare
Comment on lines
+49
to
+50
| php bin/console doctrine:migrations:migrate | ||
| php bin/adminconsole phpcr:migrations:migrate |
Member
There was a problem hiding this comment.
Does the same, and running in website console is not required:
Suggested change
| php bin/console doctrine:migrations:migrate | |
| php bin/adminconsole phpcr:migrations:migrate | |
| php bin/console doctrine:migrations:migrate |
Member
Author
There was a problem hiding this comment.
phpcr migrations are not automatically executed via the doctrine:migrations command 🤔
but yes the adminconsole was not intentional
Member
There was a problem hiding this comment.
oh this is 2.6 ? is migration bundle already there in 2.6 latest version? Else i think this is only should include the phpcr migrations
alexander-schranz
requested changes
May 20, 2026
Prokyonn
force-pushed
the
enhancement/sulu-2-3-upgrade
branch
from
d0f3a8b to
68c8882
Compare
Prokyonn
requested review from
alexander-schranz and
Copilot
and removed request for
alexander-schranz
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a dedicated upgrade guide for moving from Sulu 2.6 to Sulu 3.0 (including the two-phase prep/migrate approach), and updates the existing upgrade index/generic upgrade guide to point to it and reflect Sulu 3.x upgrade steps.
Changes:
- Add a new
upgrade-2.6-3.0guide covering preparation on 2.6, switching to 3.0, and PHPCR → Doctrine migration steps. - Update the generic “upgrade within major” guide to reference the new 2.6 → 3.0 guide and include a Sulu 3.x database migrations step.
- Link the new guide from the upgrades index.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
upgrades/upgrade-2.x.rst |
Expands scope wording to include 3.x, links to the new 2.6→3.0 guide, and adds a Doctrine migrations step for Sulu 3.x. |
upgrades/upgrade-2.6-3.0.rst |
New end-to-end upgrade guide outlining recommended upgrade phases and common post-upgrade issues. |
upgrades/index.rst |
Adds the new 2.6→3.0 guide to the upgrades toctree. |
Comments suppressed due to low confidence (1)
upgrades/upgrade-2.x.rst:104
- This section points readers to the
UPGRADE.mdfile for BC breaks, but the referenced link target in this document is pinned to the3.0branch. Since this guide is now positioned as the generic “within-major” upgrade guide for both 2.x and 3.x, a fixed 3.0 link is likely to be outdated/misleading for other 2.x/3.x upgrades. Consider linking to a version-appropriate branch/tag (or explaining how to pick the correct UPGRADE.md for the target version).
4. Check the UPGRADE.md file for BC breaks
------------------------------------------
The `UPGRADE.md file`_ in the ``sulu/sulu`` repository contains all changes breaking backwards compatibility
between different versions. These changes might break your application if you have used the changed part of Sulu
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+1
to
+2
| Upgrading Sulu 2.x and 3.x | ||
| ========================== |
| @@ -83,7 +97,7 @@ not fit your project. | |||
| For a convenient view of all changes in the skeleton repository, open https://github.com/sulu/skeleton/compare/ | |||
| and the select your current version as ``base`` and the target version as ``compare``. | |||
Comment on lines
+175
to
+182
| **10. Reindex the search** | ||
|
|
||
| Populate the new search index (admin and website) with the migrated Sulu 3.0 data: | ||
|
|
||
| .. code-block:: bash | ||
|
|
||
| php bin/console cmsig:seal:reindex --drop | ||
|
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What's in this PR?
This PR adds a new upgrade guide for moving a project from Sulu 2.6 to Sulu 3.0. The guide explains the
preparation steps on Sulu 2.6. It also covers the switch to Sulu 3.0 and the PHPCR content migration.
The upgrade index now links to the new guide.
Why?
Sulu 3.0 changes the content storage architecture from PHPCR to Doctrine. Projects need a clear
migration path before running the final content migration. The guide describes the recommended order so
teams can prepare, migrate and verify their projects.