On 22.02.10 16:54, Patrick Gerken wrote: > we ran into trouble on a plone site using both collective.indexing and > Products.CMFEditions, both > latest versions. The changes done by collective.indexing falsify some > assumptions > done by Products.CMFEditions.
`collective.indexing` now has a workaround for this, see http://dev.plone.org/collective/changeset/112307 > My changes are in the do3cc_collective.indexing branch. i think this should no longer be needed now, even though it remains to be discussed if it wouldn't be the safer option for for `CMFEditions` to indeed consider `_p_changed`. andi -- zeidler it consulting - http://zitc.de/ - [email protected] friedelstraße 31 - 12047 berlin - telefon +49 30 25563779 pgp key at http://zitc.de/pgp - http://wwwkeys.de.pgp.net/ plone 4.0 alpha released! -- http://plone.org/products/plone/ _______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
