search

collective / wildcard.fixpersistentutilities

A package that can help you remove local persistent utilies
http://pypi.python.org/pypi/wildcard.fixpersistentutilities
5 stars 7 forks source link

Please add Plone 3 support #1

Open alfrenovsky opened 12 years ago

alfrenovsky commented 12 years ago

The original bug report was:

Can't remove: object has no attribute 'isDoomed'

2012-07-05T12:49:30 ERROR Zope.SiteErrorLog http://ploneclone:8080/Plone/delete-persistent-utility/delete_utility Traceback (innermost last): Module ZPublisher.Publish, line 119, in publish Module ZPublisher.mapply, line 88, in mapply Module ZPublisher.Publish, line 42, in call_object Module wildcard.fixpersistentutilities.views, line 149, in delete_utility Module wildcard.fixpersistentutilities.views, line 34, in undoom_transaction AttributeError: 'module' object has no attribute 'isDoomed'

do3cc commented 12 years ago

Which version of Plone and which version of transaction are you using?

alfrenovsky commented 12 years ago

Plone 3.3.1 Don't know how to figure out what transaction version.

do3cc commented 12 years ago

isDoomed only exists in ZODB 3.8 and higher. Plone 3.3 user Zope 2.10 which uses ZODB 3.7. I am not sure if support for older versions will get added. Are you really wanting to use fixpersistentutilities to upgrade to 3.3? Or do you want to upgrade from 3.3 to 4.x? Principally you can use wildcard.fixpersistentutilities after an upgrade to 4.x. wildcard.fixpersistentutilities provides some patches that will make plone not to fail if there is missing code. But before you try this, make a backup.

alfrenovsky commented 12 years ago

Also tried to install a fresh 4.latest and copy the Datafs. Can't migrate because of the missing interfaces. And fixpersistentutilities just doesn't remove them. Monday I`ll send you some logs.

do3cc commented 12 years ago

This is becoming more of a regular support question, which should go to the plone-users list: https://lists.sourceforge.net/lists/listinfo/plone-users/ or to the plone chat. Also, if you are doing a migration, you should have a look at the migration guides: http://plone.org/documentation/manual/upgrade-guide/

As for the errors you mention, I cannot give any hint yet. If you write to the ML, together with the logs, also tell us if the problems happen on startup or after opening the site, if you use addon products etc.etc.

As for the bug report itself, I'll modify the title now, since it basically is the question to add plone 3.3 support. I am not sure how likely this is going to happen. I have no plans to implement this feature.

I hope this helps!

moorepants commented 10 years ago

Can you suggest a patch to get this to work? I'm also trying to migrate a Plone 3.3.6 site to Plone 4 which unfortunately had a Plone4Artists add-on installed that does not exist for Plone 4. So it seems that I have to completely remove the p4a references while it is a Plone 3 site, before migration.

This seems to have worked: http://www.eng.ox.ac.uk/Plone/running-plone/upgrading-from-plone-3.3.5-to-plone-4.1.2 for someone else, but I'm not sure how (I've messaged them to see if they have a suggestion).

moorepants commented 10 years ago

I just tried 1.1b2 which doesn't have the isDoomed check and the p4a instances seem to be able to be removed. I'll report more later once I see if upgrade is successful.