Skip to content

Commit 11d6d6c

Browse files
Update docs/backend/upgrading/version-specific-migration/upgrade-to-61.md
Co-authored-by: David Glick <david@glicksoftware.com>
1 parent 7f78901 commit 11d6d6c

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/backend/upgrading/version-specific-migration/upgrade-to-61.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -145,7 +145,7 @@ There are a few things you should consider when upgrading a project to, or makin
145145
- Do you want to use the `Products.CMFPlone` package (no distributions), either `plone.volto` or `plone.classicui` (one distribution), or `Plone` (two distributions)?
146146
- If your site uses Volto for the frontend, you will already have `plone.volto` as a dependency.
147147
This can stay the same.
148-
- If your site uses only the `Products.CMFPlone` package, the frontend is Classic UI.
148+
- If your site depends on the `Products.CMFPlone` package without the `Plone` or `plone.volto` packages, then the frontend is Classic UI.
149149
This can stay the same, but you may want to depend on `plone.classicui`.
150150
With that package you can still create a new site and have the same content as before.
151151
- If your site uses the `Plone` package, you will have the two new distributions available.

0 commit comments

Comments
 (0)