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

The installation of an add-on including its dependencies is no longer transactional #2872

Open
zopyx opened this issue May 23, 2019 · 0 comments

Comments

@zopyx
Copy link
Member

zopyx commented May 23, 2019

The fix for

#2228

introduced a new undesired installation behavior.

The installation of an add-on (and its dependencies) in Plone in all versions has been transactional until Plone 5.1.

Plone 5.2 introduces a workaround for the bug mentioned above which gives up this principle.

As clearly documented in

#2228 (comment)

the new behavior can bring a site into an unwanted and undefined state. An installation issue with a package must never ever install any further dependencies. A rollback of the transaction for the add-on itself and its dependencies is the only valid option in this case.
Full success or full rollback. Nothing inbetween.

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

No branches or pull requests

1 participant