Monday 01 November 2010 3:08:54 pm

I fear it's one of those areas of eZP that despite being very powerful is severely undocumented (along with eg. workflow events).

Imho any change to content should be coded within an "operation", and views should be little but wrappers around them. The advantage is that it would make it much easier to interact with the system using php code, webservices or anything else that bypasses views.

Operations are

• available for invocation from php code via ezOperationHandler::execute()
• tied to triggers

Principal Consultant International Business
Member of the Community Project Board