and Failed Migrations

Another fun-and-games style problem I’ve come across when using sometimes migrations won’t work when converting a standard site’s files over to blobs.

That’s a pretty ambiguious description, but essentially, the error you might see will have a semi-normal traceback to start, and then garbage (contents of a file, presumably) - which, depending on the file size might hurt your browser.  The last part of the (normal) traceback reads thus:

File "/home/buildout/instance/eggs/ plone/app/linkintegrity/", line 158, in referencedObjectRemoved raise LinkIntegrityNotificationException, obj LinkIntegrityNotificationException

Thankfully, this gives us an excellent pointer to a solution: disable link integrity checking on your site prior to migrating.

The fix/workaround

Head to the Plone Control Panel, and click onto Site.  Uncheck Enable link integrity checksand then run your blob migration.  When you’re done, you can return your site to normal.Or not.  Your choice.  Doens’t seem like there’s any harm with turning it back on once everything’s happy; just something to watch out when migrating content.

Go Top
comments powered by Disqus