What are operations in eZ Publish context?

Next topic

Author	Message
Eirik Alfstad Johansen	Monday 01 November 2010 10:11:35 am Can anyone point me to a page in the docs or elsewhere where operations are explained. I've seen them lying around (among other places, in relation to the shop module), and while playing around with the ggsysinfo extension, I noticed it had a separate view listing all the installation operations. However, as I've never had the need for them yet, I'm uncertain as to their purpose. Sincerely, Eirik Alfstad Johansen http://www.netmaking.no/
Gaetano Giunta	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

Author

Message

Monday 01 November 2010 10:11:35 am

Can anyone point me to a page in the docs or elsewhere where operations are explained. I've seen them lying around (among other places, in relation to the shop module), and while playing around with the ggsysinfo extension, I noticed it had a separate view listing all the installation operations. However, as I've never had the need for them yet, I'm uncertain as to their purpose.

Sincerely,

Eirik Alfstad Johansen
http://www.netmaking.no/

Gaetano Giunta

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