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

upgrade/migrate for Plone 5 if needed: isaw.policy 1.0.dev0 #523

Open
paregorios opened this issue Jul 12, 2024 · 4 comments
Open

upgrade/migrate for Plone 5 if needed: isaw.policy 1.0.dev0 #523

paregorios opened this issue Jul 12, 2024 · 4 comments

Comments

@paregorios
Copy link
Member

paregorios commented Jul 12, 2024

This currently active addon provides three Dexterity types: location, publication, and library collection. We need it to work properly under Plone 5.1.

isaw.policy.location

The only objects of this type currently in the database are test items in my personal folder, and they are all currently throwing the error:

AttributeError('image',) (Also, the following error occurred while attempting to render the standard error message, please see the event log for full details: image)

I will create a separate ticket for addressing this error.

isaw.policy.publication

This content type is currently used widely across the site and is working fine.

isaw.policy.libcollection

This content type is not currently used anywhere on the site.

@paregorios paregorios changed the title upgrade/migrate for Plone 5: isaw.policy 1.0.dev0 upgrade/migrate for Plone 5 if needed: isaw.policy 1.0.dev0 Jul 12, 2024
@paregorios
Copy link
Member Author

Data will be migrated fine, but the views need to be checked in Plone 5.1.

@sauzher
Copy link

sauzher commented Dec 11, 2024

@paregorios
isaw.policy.location is still needed even if there is no active contents in the portal?

the ticket you refer to has been created?

@paregorios
Copy link
Member Author

@sauzher Thanks. isaw.policy.location is no longer needed and can be eliminated. I have not created a new ticket for the problems, and think we don't need one since we are going to eliminate the type entirely. Does that make sense to you?

@sauzher
Copy link

sauzher commented Dec 13, 2024

Yes, it does. Now I can get rid of that type during migration script run.
Thanks.

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

2 participants