I fixed issue #152. The way in which I solved it involved adding a
browser view that may be useful in other places as well. So I will
advertise is here. :)
You can now call some-context/@@payable-content and get back True if
that context is payable (buyable, donatable) and False otherwise. Can
be handy for spots where you cannot import and check against an
interface, like in actions.xml.
Also, instead of edit-buyable, edit-donatable, etcetera, there is now
the edit-payable view. It is of course still handled by a different
browser view class, based on the interface (IBuyableMarker,
IDonatableMarker) of the context. This meant I could have just one
action in actions.xml as the edit tab for any content that is payable.
So in case you have any references to @@edit-buyable/donatable/etc in
any custom client product, you need to change that to @@edit-payable.
Getting close to a release candidate. :)
Bye,
--
Maurits van Rees | http://maurits.vanrees.org/ [NL]
Work | http://zestsoftware.nl/
"I am trapped in a Klein Bottle and can't get in."
www.ifpeople.net
t: 678-608-3408
130 Boulevard NE, #6
Atlanta, GA 30312