This site has been archived and you can no longer log in or post new messages. For up-to-date community resources please visit

eZ Community » Forums » eZ Publish 5 Platform » Publish Content Signal triggered via...

Publish Content Signal triggered via backend (legacy)

Publish Content Signal triggered via backend (legacy)

Tuesday 15 April 2014 6:54:00 pm - 2 replies

i try to trigger a Signal which is initiated by a publish content event in the backend of eZ (legacy).
Theoratically the ContentService\PublishVersionSignal should be the right one but i suppose it's only executed when working with ContentService via API directly, but the content is published in the backend.
This example does not work on backend event:
I only see that the PersistenceCachePurger methods are executed but not the "Signals", how can i clean trigger the PublishEvent in symfony stack?

Monday 21 April 2014 7:57:18 pm

Hi Artur

Signals are indeed only triggered when using API, and hence won't be used by the legacy backend.

I'm afraid that there is no reliable native solution for what you want to do. I can suggest you to implement a content edit handler that would trigger a Symfony event (see documentation on Confluence to learn how to use Symfony services in legacy code).

Wednesday 23 April 2014 6:11:07 pm

or a legacy workflow event, and submit it to ezworkflowcollection blunk.gif Emoticon


You must be logged in to post messages in this topic!

36 542 Users on board!

Forums menu

Proudly Developed with from