Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allows working copy of Plone Site #130

Open
wants to merge 5 commits into
base: master
Choose a base branch
from
Open

Conversation

wesleybl
Copy link
Member

@wesleybl wesleybl commented Oct 9, 2024

This is part of: plone/volto#5284

The container for the Plone Site working copy is Plone Site itself.

To avoid permission errors, the Plone Site working copy is created as the Document type. But right after the Document is created, its portal_type is changed to "Plone Site", so that the schema of the working copy is the same as the Plone Site schema.

Prevents Plone Site permissions from being changed on checkin.

The working copy of Plone Site is created in Plone Site itself. So at checkout, we should check if the user has permission to add content in Plone Site, instead of its parent.

The container for the Plone Site working copy is Plone Site itself.

To avoid permission errors, the Plone Site working copy is created as
the Document type. But right after the Document is created, its
portal_type is changed to "Plone Site", so that the schema of the
working copy is the same as the Plone Site schema.

- Prevents Plone Site permissions from being changed on checkin.
The working copy of Plone Site is created in Plone Site itself. So at
checkout, we should check if the user has permission to add content in
Plone Site, instead of its parent.
Plone Site is now versionable in Products.CMFEditions
@mister-roboto
Copy link

@wesleybl thanks for creating this Pull Request and helping to improve Plone!

TL;DR: Finish pushing changes, pass all other checks, then paste a comment:

@jenkins-plone-org please run jobs

To ensure that these changes do not break other parts of Plone, the Plone test suite matrix needs to pass, but it takes 30-60 min. Other CI checks are usually much faster and the Plone Jenkins resources are limited, so when done pushing changes and all other checks pass either start all Jenkins PR jobs yourself, or simply add the comment above in this PR to start all the jobs automatically.

Happy hacking!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants