This is not a troubleshooting section where one can find help based on subtle
error messages.
The documentation does not give a direct from error to error resolution.
If there are no objections I will add the related traceback and error
information to the docs here.

-aj


Nathan Van Gheem wrote
> http://plone.org/documentation/manual/upgrade-guide/version/upgrading-plone-4.2-to-4.3/referencemanual-all-pages
> 
> 
> On Sun, May 26, 2013 at 10:32 AM, Andreas Jung <

> lists@

> > wrote:
> 
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Thanks.
>>
>> Do we have troubleshoting section in the documentation related to
>> upgrade problems?
>>
>> Andreas
>>
>> David Glick wrote:
>> > As documented in the upgrade guide and Dexterity release notes you
>> > must install plone.app.dexterity with the [relations] extra if
>> > upgrading to Dexterity 2. This is unfortunate but was necessary since
>> > no one has committed to maintaining the relation support, so it
>> > couldn't be submitted to be in core.
>> >
>> > David Glick (mobile)
>> >
>> > On May 26, 2013, at 6:30 AM, Andreas Jung <

> lists@

> > wrote:
>> >
>> > Plone 4.3:
>> >
>> > calling
>> >
>> > img.target.to_object
>> >
>> > fails for all referenced objects of a Plone site migrated from Plone
>> > 4.2.X to Plone 4.3
>> >
>> >
>> >
>> >
>> /home/plone/.buildout/eggs/z3c.relationfield-0.6.2-py2.7.egg/z3c/relationfield/relation.py(111)_object()
>> >
>> >
>> >
>> > -> try: (Pdb) list 106      def _object(id): 107          if id is
>> > None: 108              return None 109          intids =
>> > component.getUtility(IIntIds) 110          import pdb;
>> > pdb.set_trace() 111  ->        try: 112              return
>> > intids.getObject(id) 113          except KeyError: 114              #
>> > XXX catching this error is not the right thing to do. 115
>> > # instead, breaking a relation by removing an object should 116
>> > # be caught and the relation should be adjusted that way.
>> >
>> > (Pdb) print intids 
> <persistent broken five.intid.intid.IntIds
>>
>  > instance '\x00\x00\x00\x00\x00\x04\x9e\xb8'>
>> >
>> > (Pdb) intids.getObject(id) *** AttributeError: getObject
>> >
>> > Why do we have broken five.intid here?
>> >
>> > -aj
>> >> 
> <lists.vcf>
>  _______________________________________________
>> >> Product-Developers mailing list 

> [email protected]

>> >> https://lists.plone.org/mailman/listinfo/plone-product-developers
>>
>> - --
>> ZOPYX Limited         | Python | Zope | Plone | MongoDB
>> Hundskapfklinge 33    | Consulting & Development
>> D-72074 Tübingen      | Electronic Publishing Solutions
>> www.zopyx.com         | Scalable Web Solutions
>> - --------------------------------------------------
>> Produce & Publish - www.produce-and-publish.com
>>
>>
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.11 (Darwin)
>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>>
>> iQGUBAEBAgAGBQJRoir6AAoJEADcfz7u4AZj9YkLv0Pb1SJxCM4dqztxsphlNdel
>> 3NR4Un5laF1HqdZjPT9/YrGgzNHwJJDZzBXYi3BU2FfA1j/yD4l7mG9/u7I41LiA
>> 1QrEqs2RsCY8Sk5KUcZKK97ewcnqwMmrjEmw4Q23lERbp9j3uYWc1A+1ehLGT3Dy
>> HDG+SKKp104UmY38QpAKBL7IYQfz/MT+ECwr44f1NS+C0CQoYqML4gnyxj9o1WIM
>> 1gByNakTUU89MfCU6VhD7sBmHE37FgPjO1TPbpCVnkjd8bF5noaqapK3ChfarxtU
>> dHZJmJ0B7U90eyyAsjqF5RUB6LPYe6P8wQocGdlGaSc5Q2LjQvZMxhZVfpH+/jZ7
>> 9ph23vMvJZ+6gqps4Pq0rJx+8i3JgbywwhFNAhHKr70QjIuAlxHiN+5kjvNbKPud
>> IgqM9TMMak2eyLxEMBDgPA0/23gYWd33zIWUCgTKT11HN/lOXORXTTb+Nj4T+cTL
>> geHegrEAwTIdwcT984QGmAquW1gxjTI=
>> =1Coc
>> -----END PGP SIGNATURE-----
>>
>> _______________________________________________
>> Product-Developers mailing list
>> 

> [email protected]

>> https://lists.plone.org/mailman/listinfo/plone-product-developers
>>
>>
> 
> _______________________________________________
> Product-Developers mailing list

> [email protected]

> https://lists.plone.org/mailman/listinfo/plone-product-developers





--
View this message in context: 
http://plone.293351.n2.nabble.com/Persistent-broken-five-intid-intid-IntIds-after-Plone-4-2-4-3-migration-tp7565368p7565373.html
Sent from the Product Developers mailing list archive at Nabble.com.
_______________________________________________
Product-Developers mailing list
[email protected]
https://lists.plone.org/mailman/listinfo/plone-product-developers

Reply via email to