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

Remove old calendar and events portlets #154

Open
mauritsvanrees opened this issue Sep 15, 2021 · 0 comments
Open

Remove old calendar and events portlets #154

mauritsvanrees opened this issue Sep 15, 2021 · 0 comments

Comments

@mauritsvanrees
Copy link
Member

We have plone/app/portlets/portlets/calendar.py and events.py, but these are only here for backwards compatibility. The real portlets are in plone.app.event now:

$ cat calendar.py 
# avoid broken persistent object
from plone.app.event.portlets.portlet_calendar import Assignment
$ cat events.py 
# avoid broken persistent object
from plone.app.event.portlets.portlet_events import Assignment

I think if you still have such a persistent object in your database and you run bin/zodbupdate, the script recognises that the class is at a different place now, and rewrites the object. I did not test it in this case, but that is what I expect. When going from Python 2 to 3 in 5.2, everyone will have run this script.

So when was this change done? In 2011, first in commit 6a2c8c6 and a small change in 9adde7d. Both commits are in plone.app.portlets version 2.5a1. This was included since Plone 4.3.4.

So I think we can safely remove these two files on master, which is for Plone 6 only.

Can someone confirm that my conclusion is correct?

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