Jan Hackel wrote: >>>> On the comment front, it seems that there is a 'comments' viewlet (and >>>> associated template) at >>>> > <http://dev.plone.org/plone/browser/plone.app.layout/trunk/plone/app/layout/viewlets/comments.py>. >>>> Presumably, we should be able to register our own for appropriate >>>> contexts/interfaces and then tweak the behaviour accordingly. >>>> >>>> Does that sound right? Or am I being overly hopefull by only looking at >>>> the trunk of plone.app.layout? (If so, what version(s) should we be >>>> looking at for Plone 3.x compatibility?) >>> I am pretty sure it can be done for the breadcrumbs, but I haven't had a >>> look at the comments. But this is only the beginning (as so often with >>> symptoms). I think any Plone View(let) will prefer the containment path >>> over the navigation path, e.g. the edit view. I am still experimenting if >>> this can somehow be mended at it's root. Soon more, I hope. >> Ah, I see. Completely off the top of my head, could we provide our own >> adapter to IAbsoluteURL, or something similar? > > I am afraid, no. The relevant operation for the catalog is getPhysicalPath. > It comes from OFS.Traversable (Zope 2, alas), which relies on acquisition > instead of adaption.
Now I'm confused. I thought that the *aim* was to tweak something that the catalog would ignore so that we don't end up with multiple catalog entries for each object. If we just adapt IAbsoluteURL, then it seems like we should be able to ensure that whenever someone asks for the url of the object that we're concerned with, we can give them the (archive-url) answer that we want to. What am I missing? Tim _______________________________________________ quills-dev mailing list [email protected] http://lists.etria.com/cgi-bin/mailman/listinfo/quills-dev
