Objects can no longer adapt to IPrimaryFieldInfo

fulv · August 15, 2016, 7:53pm

I have three custom cover tiles, and the client has no budget for upgrading, so I found a solution here:

plone/plone.rfc822/blob/master/plone/rfc822/supermodel.rst

Supermodel handler
==================

This package contains a handler for the ``marshal`` ``plone.supermodel``
namespace, which can be used to mark the primary field of a schema.

This handler is installed so long as ``plone.supermodel`` is installed.

First, let's load this package's ZCML so that we can run the tests:

    >>> configuration = b"""\
    ... <configure xmlns="http://namespaces.zope.org/zope">
    ...
    ...     <include package="zope.component" file="meta.zcml" />
    ...     <include package="plone.supermodel" />
    ...     <include package="plone.rfc822" />
    ...
    ... </configure>
    ... """
    >>> from io import BytesIO

This file has been truncated. show original

So I fixed it by doing this in one of my __init__.py files:

from plone.app.contenttypes.behaviors.leadimage import ILeadImage
from zope.interface import alsoProvides
from plone.rfc822.interfaces import IPrimaryField

alsoProvides(ILeadImage['image'], IPrimaryField)

Not sure if this could be done in zcml. By the way, the link to plone.rfc822 above also explains how a field is marked as primary in schema, using marshal:primary="true". That's how the File and Image schemas do it in their schema in plone.app.contenttypes.

I'd still love to understand why this broke at some point on my client's site, but I may never know.