Matt Hamilton's presentation at the European Plone Symposium 2010 discusses event-driven programming in Plone, focusing on how to extend existing functionality without modifying the core code. He illustrates this by sharing a real-life scenario involving the addition of spam checking to comments in the plone.app.discussion product, leveraging Plone's event system to circumvent the lack of extension points. The methodology allows for minimal boilerplate code while maintaining existing functionality and providing a pathway for further automation and customized actions within Plone.

1. Event Driven Programming in
Plone
Matt Hamilton
...or how to extend Plone the lazy way
Matt Hamilton
Technical Director, Netsight

2. Who am I?
- Matt Hamilton
- Technical Director of
Netsight Internet Solutions
- A Plone ‘integrator’
matth@netsight.co.uk
@hammertoe
Matt Hamilton European Plone Symposium 2010, Sorrento 2

3. Who is this talk for?
- Integrators
- Those newish to Plone, they can
assemble together a site from a
number of products, but don't really
want to alter them
- I consider myself 'experienced' but this
was a bit of an epiphany for me
Matt Hamilton European Plone Symposium 2010, Sorrento 3

4. What is the problem?
?
Matt Hamilton European Plone Symposium 2010, Sorrento 4

5. What is the problem?
I want to change the functionality of an
existing product, but don't want to
change the guts of it.
Matt Hamilton European Plone Symposium 2010, Sorrento 5

6. What is the problem?
Came from a real life problem.
Developing Netsight's new website.
Wanted to use plone.app.discussion, but
needed to add spam checking on
comments
Matt Hamilton European Plone Symposium 2010, Sorrento 6

7. What is the problem?
Matt Hamilton European Plone Symposium 2010, Sorrento 7

8. What is the problem?
plone.app.discussion has captcha
support already, but I wanted to add
Akismet support, but no easy extension
point
Matt Hamilton European Plone Symposium 2010, Sorrento 8

9. Admittedly, I could have offered to
refactor the whole p.a.discussion code ;)
Matt Hamilton European Plone Symposium 2010, Sorrento 9

10. Considered Approaches
- I could subclass the product and
override it
➡ A lot of boiler-plate for small change
- I could use an adapter and adapt the
behaviour
➡ No adapter lookup where I needed it
- I could 'just hack it in the original code'
➡ Yuck! Maintainability nightmare
Matt Hamilton European Plone Symposium 2010, Sorrento 10

11. Eureka!
Matt Hamilton European Plone Symposium 2010, Sorrento 11

12. Eureka!
Use Events!
Matt Hamilton European Plone Symposium 2010, Sorrento 12

13. Eureka!
- I realised I could leave p.a.discussion
alone, and just listen for an event for
when a comment is added and then
check it for spam
- I can listen for an event from Plone and
then do the behaviour afterwards
Matt Hamilton European Plone Symposium 2010, Sorrento 13

14. Advantages
- Leave the existing code alone
- Work around lack of suitable extension
point
- Very little boilerplate code
- All happens in same transaction still
Matt Hamilton European Plone Symposium 2010, Sorrento 14

15. Zope's Event System
- Events
- Subscribers
Matt Hamilton European Plone Symposium 2010, Sorrento 15

16. A Simple Event
in configure.zcml:
<subscriber
for=".interfaces.IMyObject
.interfaces.IMyEvent"
handler=".events.myEventHandler"
/>
in events.py:
def myEventHandler( object, event):
object.doSomeThing()
Matt Hamilton European Plone Symposium 2010, Sorrento 16

17. Event Simpler Event
in events.py:
from five import grok
from interfaces import IMyObject, IMyEvent
@@grok.subscribe(IMyObject, IMyEvent)
def myEventHandler( object, event):
object.doSomeThing()
Matt Hamilton European Plone Symposium 2010, Sorrento 17

18. Example - Spam Checking
in events.py:
from five import grok
from plone.app.discussion.interfaces
import IComment
from zope.lifecycleevent.interfaces
import IObjectAddedEvent
@@grok.subscribe(IComment,
IObjectAddedEvent)
def checkForSpam( comment, event):
wf = getToolByName(comment,
'portal_workflow')
if is_spam(comment.text):
wf.doActionFor(comment, ‘spam’)
Matt Hamilton European Plone Symposium 2010, Sorrento 18

19. Next Example - GetPaid
GetPaid is an eCommerce add-on to
Plone
➡ Allows you to mark any piece of
content as ‘buyable’
Matt Hamilton European Plone Symposium 2010, Sorrento 19

20. PloneConf 2010 Registration
User clicks ‘register’
User fills in ‘add attendee’ form, and hits submit
Event fired indicating object added to container
Event subscriber marks item as buyable, adds to
shopping cart, and then redirects to cart view
Matt Hamilton European Plone Symposium 2010, Sorrento 20

21. GetPaid Example
from Products.CMFCore.utils import getToolByName
from getpaid.core.interfaces import workflow_states
import interfaces
def handlePaymentReceived( order, event ):
if event.destination !=workflow_states.order.finance.CHARGED:
return
for item in order.shopping_cart.values():
ob = item.resolve()
workflow = getToolByName( ob, 'portal_workflow')
state = workflow.getInfoFor( ob, 'review_state' )
if state == 'published':
return
workflow.doActionFor( ob, 'publish')
Matt Hamilton European Plone Symposium 2010, Sorrento 21

22. Other Ideas
- Whenever a Folder is created, add
some default content to it
- When a Page is added, set some
metadata fields
- When an Event is added, check that an
expiry date has been set no more than
12 months in the future
Matt Hamilton European Plone Symposium 2010, Sorrento 22

23. Questions?
Matt Hamilton
matth@netsight.co.uk