Upgrade to Plone 6.2.0#125
Merged
Merged
Conversation
Contributor
|
Let me look at it, as we need also to replace the Migration Tool here. |
Member
Author
|
@ericof I made the machine take a look. I think these are the only ones that are worth it, but check it out. |
Adapt kitconcept.core to Products.CMFPlone 6.2.0: - Drop the local MigrationTool override of addon_list/initializeTool; the addon registry now lives in plone.base - Import IAddonList from plone.base.interfaces and deprecate the local IAddonList alias - Remove initialize_migration_tool from the base setup handler - Renumber the 6.2-alpha upgrade step (fix_history_action_permission + IClassicUISchema) to 20260620001 so it runs after the formblock step
Drive site creation in the test layer through the distribution answers/handlers instead of the bespoke setUpDefaultContent path: - Add a CoreFixture (answers-driven) and DEFAULT_ANSWERS, dropping the manual add_site call in the fixture - Add session-scoped distribution/answers fixtures and a create_site helper so tests can build sites with arbitrary answers - Un-skip the LRF content-type test and build a multilingual site for it This is the test groundwork required to exercise the new multilingual support.
Provide an optional "multilingual" Generic Setup profile that pulls in plone.app.multilingual and ships the LRF (Language Root Folder) type, moving it out of the dependencies profile. Downstream projects can now rely on this profile instead of shipping the configuration themselves.
Provide pre_handler/handler/post_handler on the distribution plus a creation utilities module (content, registry, permissions, site logo, multilingual support) so the site-creation logic lives in the core distribution instead of being duplicated by downstream projects. - Wire the handlers onto the testing distribution - Add an available_languages argument to add_site, defaulting to the default language when not provided
- Correct a typo in the move_rename_object script docstring - Regenerate the de/en/pt_BR locale catalogs and the POT template
Contributor
|
Updated this branch — merged latest Commits
Notes
|
Contributor
|
@sneridagh After merging, but before releasing, I want to make sure |
sneridagh
commented
Jun 22, 2026
sneridagh
left a comment
sneridagh
left a comment
Member
Author
There was a problem hiding this comment.
LGTM!!! Flawless, lovely work!
Contributor
|
@sneridagh Before merging it I will test on kitconcept-website just to be sure it is working as expected, (And probably make some additional fixes) |
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
2 participants
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.
@ericof @davisagli could you please check if there is some upgrade in the 6.2.0 upgrade steps that have to be backported? I guess you have more background on which ones are needed and which don't. Thanks!!