Remove broken old import step from base profile. #76
Conversation
This file contains 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
Fixes issue #74. Includes an upgrade step for the base profile (plone.app.ldap:default). And an upgrade step for the Plone profile (plone.app.ldap.controlpanel:plone5) that calls that one.
|
Thank you! |
mauritsvanrees
deleted the
maurits-remove-old-persistent-import-step-issue-74
branch
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.
Fixes issue #74.
Includes an upgrade step for the base profile (plone.app.ldap:default).
And an upgrade step for the Plone profile (plone.app.ldap.controlpanel:plone5) that calls that one.
This way it should cleanly upgrade both with and without Plone.
BTW, a manual workaround to the upgrade steps would be to go to the Manage tab of
portal_setupand remove the broken import step there.