p4a.ploneimage dependencies

0 views
Skip to first unread message

Patrick Gerken

unread,
Oct 26, 2009, 7:00:37 PM10/26/09
to p4a-...@googlegroups.com
Hi,

last week I had this issue with the registerIndexableAttribute.
Instead of doing
the right thing and upgrade to a stable plone I removed that method that is
deprecated anyway and register the attribute with the help of plone.indexer
and an adapter declaration. From my understand this works only for
Plone <=3.2.
Do we want to maintain backward compatibility with older versions,
or is this something I can commit on trunk without stepping on anybodies toes?

Best regards,

Patrick

p.s. I would have committed it to branch already, but seems the svn
server disk is full

Ross Patterson

unread,
Oct 27, 2009, 12:25:25 AM10/27/09
to p4a-...@googlegroups.com
Patrick Gerken <do3c...@googlemail.com> writes:

> Hi,
>
> last week I had this issue with the registerIndexableAttribute.
> Instead of doing
> the right thing and upgrade to a stable plone I removed that method that is
> deprecated anyway and register the attribute with the help of plone.indexer
> and an adapter declaration. From my understand this works only for
> Plone <=3.2.
> Do we want to maintain backward compatibility with older versions,
> or is this something I can commit on trunk without stepping on anybodies toes?

Plone 3.3 has a BBB wrapper that preserves compatibility with
registerIndexableAttribute. Since there's nothing to be gained from
breaking compatibility with Plone <3.3, I'm -1 for this change.

> p.s. I would have committed it to branch already, but seems the svn
> server disk is full

I think that's being worked on. But I don't think branch vs trunk makes
any difference if the server is out of disk space.

Thanks again for contributing,
Ross

Reply all
Reply to author
Forward
0 new messages