Remove Products.CMFFormController / portal_form_controller. #696
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.
Remove the package from the buildout files.
Use branches of
CMFPlone
(plone/Products.CMFPlone#3226) andplone.app.upgrade
(plone/plone.app.upgrade#251).We could also remove a
CMFFormController
line fromplone.app.testing
, but it's not in the way.Could be done once we make a
plone.app.testing
branch for Plone 6 only.In
plone.app.upgrade
I remove theportal_form_controller
tool.We could also conditionally remove it: check if the tool is an instance of
ZODB.broken.Broken
.This is to support the theoretical case that someone explicitly adds the
CMFFormController
package, because it is still needed in a specific site.But same could be done for
portal_quickinstaller
, and we don't do it there either.Once green and approved, I can do the merges. The two PRs should be merged, and then on coredev we can keep using the master branches, and only merge the part of this PR that removes
CMFFormController
from thetest-eggs
and sources/versions.